GENERAL ERROR: The nbpushdata command can fail if the REQUIRED_INTERFACE entry exists in the vm.conf file on a clustered NetBackup server

Article:TECH48026  |  Created: 2008-01-05  |  Updated: 2008-01-05  |  Article URL http://www.symantec.com/docs/TECH48026
Article Type
Technical Solution


Environment

Issue



GENERAL ERROR: The nbpushdata command can fail if the REQUIRED_INTERFACE entry exists in the vm.conf file on a clustered NetBackup server

Error



<16> get_host_info: get_*_hostinfo failed, stat=163
<16> process_OPTION_add: get_host_info failed, stat=163

Solution



Overview:
When attempting to upgrade a clustered master server the nbpushdata command may fail during the upgrade.  The nbpushdata command is used to populate the new Enterprise Media Manager (EMM) database.   The command will fail with a error code 163, this is not the same as a NetBackup Status code 163.  This failure can occur when a REQUIRED_INTERFACE setting exists in the vm.conf file on a clustered system.

This issue was reported when upgrading a HP-UX clustered master server.  This is not specific to HP-UX and could occur in other environments.

Troubleshooting:
Check the vm.conf file for a REQUIRED_INTERFACE entry.
# cat /usr/openv/volmgr/vm.conf
CLUSTER_NAME = nbmaster
DEVICE_HOST = nbmaster
REQUIRED_INTERFACE = nbmaster

Log Files:
The /usr/openv/netbackup/logs/nbpushdata/log.<date> file on the server will show the following entries when running nbpushdata on an clustered Master/EMM server.
<16> emmlib_UpdateHostEx: (0) UpdateMachine failed, emmError = 4000002, nbError = 0
<16> AddAndVerifyHost: Failed to update this host.  EMM error code = 4000002
<16> AddAndVerifyHost: (-) Translating EMM_ERROR_ArgInvalid(4000002) to 191 in the Media context
<16> get_remote_hostinfo: AddAndVerifyRemoteHost failed, stat=191
<16> get_host_info: get_*_hostinfo failed, stat=163
<16> process_OPTION_add: get_host_info failed, stat=163

Unified logging will show the following message for the nbemm originator id during the time that the nbpushdata command failed.
# vxlogview -p NB -o 111 -b "6/2/06 7:28:02 PM" -d all
05/24/06 19:28:02.546 [Diagnostic] NB 51216 nbemm 111 PID:24402 TID:4 [No context] 1 V-111-1049 [Machine::Update] EMMServer generic error = MachineNbuType can not be changed from CLUSTER to MEDIA

Resolution:
The cause of the problem is the vm.conf file on the clustered master server contains a "REQUIRED_INTERFACE = nbmaster" entry.  This entry causes the nbpushdata command to use the preferred machine name of nbmaster for the name of the node in the cluster.  The cluster name cannot be used as the preferred name for a node in the cluster, so the command fails.

To correct this problem, remove the REQUIRED_INTERFACE lines from the vm.conf file.  Once the lines have been removed then re-run the nbpushdata command and the upgrade should complete successfully.



Legacy ID



283712


Article URL http://www.symantec.com/docs/TECH48026


Terms of use for this information are found in Legal Notices