We are going to upgrade Netbackup 7.1 to 7.5 and then to 220.127.116.11 but which is correct order to perform upgrade and migration in clustered enviroment as manuals instructions differs from other
We have two node, hot and cold...
* Cluster guide:
Before cluster is starded:
On each inactive node to which NetBackup may failover, install the NetBackup server software.
Note the following: Follow the instructions for how to upgrade NetBackup as described in the Symantec NetBackup Installation Guide
* Installation guide:
Do not start the NetBackup job-related processes until all nodes are upgraded
* But Upgrade guide:
This step applies only to cluster installations.
After all image metadata migration processes have completed on this master server,
for other master servers in the cluster, you can update the remaining nodes to
NetBackup 7.5 by using the normal cluster upgrade process. For complete details,
see the NetBackup 7.5 Installation Guide.
So, is migration done before or after all nodes are upgraded, because it reguire netbackup service be up and running ?
And how about rollback if everything goes terribly wrong....We are planning to do for rollback purpose Veritas cluster split after system is down for db mounts and tar /usr/openv/*
Thats why wondering could we do upgrade with rollbackup plan as follow:
- shutdown services (cluster offline, freeze)
- split db disk and tar binaries to "backup"
- upgrade hot node
- start services on hotnode and migrate
- verify its working
- upgrade cold node
- rollback if system is not working
- restore binaries for tar "backup"
- attach old veritas db mount points back.