GENERAL ERROR: After upgrading to Veritas NetBackup (tm) Vault 6.x, the Vault interface may not reflect the contents of vault.xml

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


Environment

Issue



GENERAL ERROR: After upgrading to Veritas NetBackup (tm) Vault 6.x, the Vault interface may not reflect the contents of vault.xml

Solution



Overview:
After upgrading from an older NetBackup Vault release to version 6.0 or 6.5, the Vault interface may not reflect the same robotic volume groups that are configured in the vault.xml file.

The default format for robotic volume groups has changed, starting with NetBackup 6.0, to allow for a larger number of robots.  For example, what used to be 00_000_TLD and 01_000_TLD (old format) could become 001_00000_TLD and 000_00000_TLD (new format).  During the upgrade, the old format volume group names are retained as long as volumes/media that belong to these volume groups exist.  They will continue to exist and be used until such time as all volumes belonging to them are moved (whether it be to another robotic volume group or to an offsite volume group), at which time the old volume group names will be deleted.  Once the names are deleted, any media that are reinventoried or injected back into the robot will take on the new robotic volume group format.

During the upgrade, the robotic volume groups in the vault.xml remain unchanged.  Furthermore, a discrepancy in the robotic volume group names can arise if none of the old format robotic volume group exists, and this will mean that the vault.xml file is not updated accordingly.

Troubleshooting:
The following post upgrade snippet of a vault.xml file illustrates the discrepancy that can occur.
Note: The robotic volume group is unchanged and still takes the old format 00_000_TL4.

<VAULT CustomerID="454253" Id="1" LastMod="11291260685064530" Name="MyVault" OffsiteVolumeGroup="My_offsite_volumes"
RobotVolumeGroup="00_000_TL4" VaultContainers="NO" VaultSeed="1" Vendor="Iron Mountain">

Running vmquery on the volume database shows that all tapes in the system have been changed to the new format 000_00000_TL4.  It also shows that the old robotic volume group names no longer exist.

VOLUME5.0 BACK00 - 4MM - davetest TL4 0 1 - 000_00000_TL4 backups 42 0 - 1132822284 1133367640 1132822675 1133513632 0 0 - 0 0 - 1 50 - Added by Media Manager
VOLUME5.0 BACK01 - 4MM - davetest TL4 0 2 - 000_00000_TL4 SCRATCH 4 0 - 1132822284 0 1132824597 1133294461 0 0 - 0 0 - - 50 - Added by Media Manager
VOLUME5.0 BACK02 - 4MM - davetest TL4 0 3 - 000_00000_TL4 backups 3 0 - 1132822284 1133381401 1132824862 1133467262 0 0 - 0 0 - - 50 - Added by Media Manager
VOLUME5.0 BACK03 - 4MM - davetest TL4 0 4 - 000_00000_TL4 backups 8 0 - 1132822284 1133342441 1132833958 1133364104 0 0 - 0 0 - - 50 - Added by Media Manager
VOLUME5.0 CATAL0 - 4MM - davetest TL4 0 5 - 000_00000_TL4 CatalogBackup 2 0 - 1133344662 1133395233 1133395313 1133395575 0 0 - 0 0 - - 50 - Added by Media Manager

In this scenario, if the Vault interface is now used to view the vault.xml file, the interface will display the new robotic volume group format (000_00000_TL4), which is inconsistent with the one defined in the vault.xml (00_000_TL4).  See Figure 1

Figure 1. Vault interface showing new robotic volume group format
 

This occurs because the interface fills the drop down list with the existing robotic volume groups in the system, and then makes a call to select the volume group that it obtained from the vault.xml.   If the volume group it is trying to select does not exist in the list, it selects the first entry in the drop down list, which results in an incorrect display.

Log Files:
The /usr/openv/netbackup/db/vault/vault.xml on the master server will need to be edited to capture the new robotic group format.

Resolution:
This TechNote is written to create an awareness that the Vault interface may not display the vault.xml file correctly.  In such circumstances, the resolution is to synchronize the two by editing the vault.xml file to capture the new robotic volume group format.  This can be easily achieved by pressing "OK" on the dialog of the interface when viewing the Vault profiles.



Legacy ID



280696


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


Terms of use for this information are found in Legal Notices