NetWorker: Oracle backup fail with lockbox error during any failover of NetWorker server
Summary: When NetWorker cluster service failover from one node to another, the Oracle backup failed with lockbox error
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
No Changes but *@* was presented in the Remote Access field of the NetWorker Server client resource
No Oracle backup. Need to delete or modify the client wizard for the RMAN option to get the backup working on the failed over node
During the failover of NetWorker cluster service, the Oracle backup failed with the following error:
Oracle_Client: Unable to obtain the user credentials from the lockbox due to the following error: 'Failed to open lockbox D:\nsr\lockbox\Oracle_Client\clb.lb'.Confirm that the user 'xyz' on the host 'Oracle_Client' is in the Users attribute of the lockbox resource.
No Oracle backup. Need to delete or modify the client wizard for the RMAN option to get the backup working on the failed over node
During the failover of NetWorker cluster service, the Oracle backup failed with the following error:
Oracle_Client: Unable to obtain the user credentials from the lockbox due to the following error: 'Failed to open lockbox D:\nsr\lockbox\Oracle_Client\clb.lb'.Confirm that the user 'xyz' on the host 'Oracle_Client' is in the Users attribute of the lockbox resource.
Cause
The Remote Access Field of the NetWorker Server resource (the NetWorker Cluster name) have *@*.
If *@* presented in the Remote access list, then there is no information in RAP DB that would tell NetWorker what the other node is, and NetWorker don t have an ability to authorize all hosts (even if did, NetWorker wouldn t do that, as that would be a huge security hole). The lockbox on the active node was likely created on the active and the passive node was not added to the allowed list (this is what the error The system hostname key is missing means. This lockbox is likely going to open fine on the other node and will only have active node in the list.
If *@* presented in the Remote access list, then there is no information in RAP DB that would tell NetWorker what the other node is, and NetWorker don t have an ability to authorize all hosts (even if did, NetWorker wouldn t do that, as that would be a huge security hole). The lockbox on the active node was likely created on the active and the passive node was not added to the allowed list (this is what the error The system hostname key is missing means. This lockbox is likely going to open fine on the other node and will only have active node in the list.
Resolution
Applied the following to the "Remote Access" Field of the NetWorker Server Resource (NetWorker cluster name):
*@Physical_Node1
*@Physical_Node2
Run the backup and all OK. The lockbox information updated correctly with both physical node information.
No need to delete the Oracle client or modify
*@Physical_Node1
*@Physical_Node2
Run the backup and all OK. The lockbox information updated correctly with both physical node information.
No need to delete the Oracle client or modify
Affected Products
NetWorkerProducts
NetWorkerArticle Properties
Article Number: 000067776
Article Type: Solution
Last Modified: 03 May 2024
Version: 4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.