Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Device host entry missing in netbackup datacenter 4.5 1

Status
Not open for further replies.

dinoteo

Technical User
Oct 2, 2003
51
SG
Hi guys,

I have a global device database error in which it indicated Device host entry missing and the tape drive path and status is missing from Devices.

I know I have to reconfigure the drives..but I do not know how and where to find the command to perform the action. Can anyone please advise?

Thanks.
 
DOCUMENTATION: How to rebuild the globDB (global device database file) on the master server


Details:
Manual: NetBackup (tm) Shared Storage Option System Administrator's Guide for UNIX and Windows
Page:
Modification Type: Addition

Modification:
Note: The globDB came about because of device discovery, specifically to coordinate and compare discovery of NetBackup DataCenter (tm) devices that involve multiple media servers. The globDB still has some value without device discovery. For one, it ensures that robot numbers are not re-used across device hosts. Also, it can prevent configuration problems like duplicated drive names for multi-hosted drives, even when manual-based device configuration changes are made.

The globDB is valid on non-device discovery platforms. It can exist on any kind of media server.

The first step is to verify if the globDB needs rebuild.

Open a command prompt.
In Windows NT/2000:
Click Start | Run. Type cmd and click OK.

Run install_path\veritas\volmgr\bin\vmglob -listall.

This will produce an output to screen indicating:
device type:
device name:
serial number:
hostname:
volume database hostname:
robot number:
robot drive number:
robot type:
drive type:
flags:
worldwide name:

If the list contains errors or inconsistencies, rebuilding the globalDB is an option to synchronize device discovery.

Note: The procedure listed below will work on most installations, but due to the complexity of NetBackup, may not be suitable for all configurations and environments. This procedure also takes into account that the current device configuration is up to date and all devices have been set up and added in the Media and Device Manager. Please contact VERITAS Technical Services for any technical matter related to NetBackup device configuration changes not related to this TechNote.

On the master server:
From a command prompt:

1. Run \install_path\veritas\volmgr\bin\vmglob -delete
This will delete all the global database entries.

2. Run \install_path\veritas\volmgr\bin\vmglob -set_gdbhost <global DB hostname> -h volume_database_host
This will ensure that the master server is set as the global and volume database host.
Note: The global DB host name and the volume_database_host under most circumstances will be the host name of the master server.

3. Run \install_path\veritas\volmgr\bin\tpautoconf -upgrade
This will auto detect all previously configured devices on the master server and populate the globalDB.

4. Run \install_path\veritas\volmgr\bin\vmglob -listall
The list should reflect all the devices configured on the master server and list the master as host name and volume database host name for each device.

On each media server, from a command prompt:
Repeat Steps 2 through 4.

Note: After each update, the vmglob -listall command should reflect the additional devices configured on the media servers. The volume database host name will be the master server host name. The host name will be the media server where the device is configured.


Bob Stump
Just because the VERITAS documentation states a certain thing does not make it a fact and thats the truth
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top