GENERAL ERROR: Running "nbpushdata" on Veritas NetBackup (tm) 6.0 Maintenance Pack 2 (MP2) fails to push the globDB.

Article:TECH47638  |  Created: 2010-01-26  |  Updated: 2010-01-26  |  Article URL http://www.symantec.com/docs/TECH47638
Article Type
Technical Solution


Environment

Issue



GENERAL ERROR: Running "nbpushdata" on Veritas NetBackup (tm) 6.0 Maintenance Pack 2 (MP2) fails to push the globDB.

Error



ERROR: globDB_push OUT_[0];
Error from the EMM log: EMMServer generic error = cannot add devices until nbpushdata has been run

Solution



Symptom(s):
When nbpushdata -add is run on NetBackup 6.0 MP2, errors are registered when pushing the globDB.

A change was made in 6.0 MP2 to prevent the configuration of devices, media, pools, and barcode rules until nbpushdata has been run after an upgrade from 5.x.  Enterprise Media Manager (EMM) checks for the flag set by nbpushdata before allowing configuration if this was an upgrade from 5.x.  The configuration of devices from the globDB file is failing because nbpushdata is setting the flag AFTER the globDB records are sent to EMM instead of BEFORE the records are sent to EMM.

The device information in the globDB file is a subset of the information in the ltidevs and robotic_def files.  If all hosts are being upgraded to 6.0 at the same time (not running a mixed 5.x/6.0 environment), the nbpushdata globDB record errors can be ignored.  The devices will be properly configured when the ltidevs and robot_def records are sent to EMM.

If some Media Servers remain at 5.x (running a mixed 5.x/6.0 environment), EMM will not know about the devices on the 5.x hosts because of the globDB record errors.

Log Files:  
Nbpushdata screen output, the error is in bold for clarity:

Processing: C:\Program Files\VERITAS\Volmgr\database\globDB
Estimated time remaining will be displayed every 5 minutes.
ERROR: globDB_push OUT_[0] <COMPAQDLT80000>
Failed to push 1 records to EMM.
Pushed 0 records to EMM.


Nbpushdata.log

13:30:30.500 [988.2368] <4> display_stats: Pushed 1 records to EMM.
13:30:30.500 [988.2368] <4> push_to_EMM: Processing: C:\Program Files\VERITAS\Volmgr\database\globDB
13:30:30.500 [988.2368] <4> globDB_push: Estimated time remaining will be displayed every 5 minutes.
13:30:30.515 [988.2368] <4> globDB_push: OUT_[0] <COMPAQDLT80000> <PXB09P2101> <> 1 <baracuda> <baracuda> -1 -1 0 0 11 |0| |0| |0| |0| |0| |0
13:30:30.515 [988.2368] <4> globDB_push: +++| |0| || 0 <COMPAQ  DLT8000         011A> <> <> <> -1 -1 -1 -1
13:30:30.625 [988.2368] <16> emmlib_AddNewDrive: (0) AddDrive failed, emmError = 2001045, nbError = 0
13:30:30.625 [988.2368] <16> emmlib_DeviceConfigByGlobDb: (0) DeviceConfigByGlobDb failed, retval = < 2001045 >
13:30:30.640 [988.2368] <16> globDB_push: (-) Translating EMM_ERROR_ConfigNotExist(2001045) to 196 in the Media context
13:30:30.640 [988.2368] <16> globDB_push: emmlib_DeviceConfigByGlobDb failed, emmErr=2001045, nbErr=196
13:30:30.640 [988.2368] <4> globDB_push: {-E-} OUT_[0] <COMPAQDLT80000> <PXB09P2101> <> 1 <baracuda> <baracuda> -1 -1 0 0 11 |0| |0| |0| |0|
13:30:30.640 [988.2368] <4> globDB_push: {-E-} +++|0| |0| |0| || 0 <COMPAQ  DLT8000         011A> <> <> <> -1 -1 -1 -113:30:30.640 [988.2368] <16> globDB_push: ERROR: globDB_push OUT_[0] <COMPAQDLT80000> "Configuration is not defined in EMM"


EMM Log
4/21/2006 13:30:30.609 [Diagnostic] NB 51216 nbemm 111 PID:3420 TID:3424 [No context] 1 V-111-1049 [MachineConfigImpl::helperQueryNbpushdataConfig] EMMServer generic error = nbpushdata must be run to complete the upgrade
4/21/2006 13:30:30.625 [Diagnostic] NB 51216 nbemm 111 PID:3420 TID:3424 [No context] 1 V-111-1049 [DeviceConfigImpl::AddDrive] EMMServer generic error = cannot add devices until nbpushdata has been run


Workaround:
Before running "nbpushdata -add" on the first host in a NetBackup environment (the 5.x server that was configured as the Global Device Database Host), do the following on the 5.x Global Device Database Host:

nbpushdata -delete_flag NBPUSHDATA_G_5X_UPGRADE

Then run:

nbpushdata -add

If the issue has already been encountered, it is possible to rollback nbpushdata, delete the flag, and run nbpushdata again.  In order to do this, run the following:

nbpushdata -remove <servername>

Next, delete the flag causing the issue:
nbpushdata -delete_flag NBPUSHDATA_G_5X_UPGRADE

Then run the following again:
nbpushdata -add






Legacy ID



283176


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


Terms of use for this information are found in Legal Notices