02-21-2012 01:38 AM
Hi all,
We want to upgrade NetBackup 6.5.5 to 7.1.0.3 on a clustered Master under AIX 5.3 (HACMP 5.4).
Here is the used methodlogy :
• Freeze Cluster
• Upgrade active node in 7.1
Upgrade passive node in 7.1
• Client and options installation on passive node
• Client and options installation on active node
• Unfreeze cluster / failover test
All these operations are perfomed without any error.
But when we want to start NetBackup services, we can see the following :
• Symbolic Links have been renamed :
« /usr/openv/volmgr/misc/robotic_db » in « /usr/openv/volmgr/misc/robotic_db.orig » => always pointing to /SAN_Disk/usr/openv/volmgr/misc/robotic_db
« /usr/openv/…/var/global » in « /usr/openv/…/var/global.orig » => always pointing to /SAN_Disk/usr/openv/…/var/global
« /usr/openv/netbackup/db » in « /usr/openv/netbackup/db.orig » => always pointing to /SAN_Disk/usr/openv/Netbackup/db
« /usr/openv/…/vault » in « /usr/openv/…/vault.orig » => always pointing to /SAN_Disk/usr/openv/…/vault
«/usr/openv/db » in «/usr/openv/db.orig » => always pointing to /SAN_Disk/usr/openv/db
• Upgrade operation has created all of these directories (rob./global/db/vault/db) on internal disk
o Directories present on internal disks seem to contain upgraded informations but "/netbackup/db" which is empty on the local disk and valid on the original
place.
Upgrade operation is performed correctly and we can have access to Medias / SU when we start NetBackup but images, policies, ... are empty.
To correct this issue, we have to :
• rename :
/SAN_Disk/usr/openv/volmgr/misc/robotic_db in robotic_db.nbu7
/SAN_Disk/usr/openv/…/var/global in global.nbu7
/SAN_Disk/usr/openv/Netbackup/db in db.nbu7
/SAN_Disk/usr/openv/…/vault in vault.nbu7
• rename:
« /usr/openv/netbackup/db.orig » in « /usr/openv/netbackup/db » => pointing to “/SAN_Disk/usr/openv/Netbackup/db” because only the old version seems to be valid
• copy new local directories to SAN place :
« /usr/openv/volmgr/misc/robotic_db » => pointing to /SAN_Disk/usr/openv/volmgr/misc/robotic_db
« /usr/openv/…/var/global » => pointing to /SAN_Disk/usr/openv/…/var/global
« /usr/openv/…/vault » => pointing to /SAN_Disk/usr/openv/…/vault
• rename symbolic links (*.orig):
/usr/openv/volmgr/misc/robotic_db => symbolic link to /SAN_Disk/usr/openv/volmgr/misc/robotic_db
/usr/openv/…/var/global => symbolic lçink to /SAN_Disk/usr/openv/…/var/global
/usr/openv/…/vault => symbolic link to SAN_Disk/usr/openv/…/vault
At this time, we have been qable to start NetBackup on the first node.
The same issue has happened with the passive node.
After that, failover seems to be ok.
• Why « /usr/openv/netbackup/db.orig » is valid and not the new one (which is created on the local disk) ?
• Why new directories « /var/global », « Vault », « robotic_db » are valid and not those which are « .orig »?
Thank you for your help.
Best regards
02-21-2012 03:48 PM
Did you follow the upgrade process in the NBU Clustered Master Server Guide ?
From memory the symbolic links are controlled by the netbackup/bin/cluster/NBU_RSP file have a look there. This file is one of the paramteres for the nbu_server cluster resource.