GENERAL ERROR: Upgrading to NetBackup 6.5 from NetBackup 6.0 fails if multiple SnapVault and NearStore disk storage units use the same volume path

Article:TECH53028  |  Created: 2007-01-07  |  Updated: 2008-01-06  |  Article URL http://www.symantec.com/docs/TECH53028
Article Type
Technical Solution

Product(s)

Environment

Issue



GENERAL ERROR: Upgrading to NetBackup 6.5 from NetBackup 6.0 fails if multiple SnapVault and NearStore disk storage units use the same volume path

Solution



Overview:
An upgrade to NetBackup 6.5 from NetBackup 6.0 fails if multiple SnapVault or NearStore disk store units (DSUs) use the same volume path.  An error occurs when the Enterprise Media Manager (EMM) database schema is being updated.  The upgrade fails and the EMM database remains at the previous NetBackup 6.0 version.  

The problem only affects SnapVault and NearStore DSUs and only occurs under the following conditions:
- A single Media Server is connected to two or more NetApp appliances
- The SnapVault and NearStore DSUs are defined on at least two of the appliances
- The same volume path (ex. /vol) is used for the DSU on two or more of the appliances

If all of these criteria are met then the installer will see these disk storage units as duplicate entries when upgrading.

Troubleshooting:
Verify the volume paths used by the storage units.  On the master server run the bpstulist command to check if any storage units have the same directory listed under the Path: section.

In the following example, the installer will see two media servers with the same path.  It doesn't recognize the unique SnapVault server names.
# bpstulist -U
Label: Stu1
Media Server: HostA
SnapVault Server: FilerABC
Path: /vol1

Label: Stu2
Media Server: HostA
SnapVault Server: FilerXYZ
Path: /vol1

Log Files:
The sql log will show the following errors:
*** ERROR *** Error in file "/usr/openv/db/scripts/NBDB.6.0.sql" at line 3978
*** ERROR *** Index 'AK_DISKVOLUMEMP_EMM_DISK' for table 'EMM_DiskVolumeMountPoint' would not be unique

% // Error: Error in file "/usr/openv/db/scripts/NBDB.6.0.sql" at line 3978
// Index 'AK_DISKVOLUMEMP_EMM_DISK' for table 'EMM_DiskVolumeMountPoint' would not be unique

Resolution:
Because of other issues in the NetBackup 6.5 upgrade, it is necessary to delay deployment of NetBackup 6.5 until NetBackup 6.5.1 is available.  Once NetBackup 6.5.1 is available, the upgrade procedure is as follows:

1. Check for the existence of multiple NearStore or SnapVault storage units that point to the same combination of media server and destination path.
- For any storage units that match this criteria, modify the storage units so that each one uses a unique pathname.  This is a temporary measure that will not impact backup jobs, as it will be undone before any backup jobs are run.
- Please be aware that unless there are other, unused volumes on the system, it will be necessary to create "dummy" volumes with unique names for the purposes of the upgrade.  
2. Immediately upon completion of the 6.5GA installation, apply the 6.5.1 release update.
3. Immediately upon completion of the 6.5.1 installation, restore the original path names for each storage unit as described in step 1.

Failure to apply the 6.5.1 patch can have unintended consequences, and prevent backups from completing successfully.  

If the site has already been upgraded to NetBackup 6.5 and is experiencing the problem described, please contact NetBackup support for assistance resolving this issue.  

To download the NetBackup 6.5.1 release update, once it becomes available, visit the Support Web site at:
 http://www.symantec.com/enterprise/support/overview.jsp?pid=15143



Legacy ID



290486


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


Terms of use for this information are found in Legal Notices