We plan to upgrade our RHEL 7.7 based netbackup master from 8.1.1 to 8.2, just in case we have issues, is there any simple way to roll back such as "./install --rollback" instead of reinstall catalog? Please share your experience.
thanks
Agree with Tape_Archived
Usually the EMM database is being expanded with new tables for new features. While rolling back files is easy, there is no way of rolling back the added tables.
/Nicolai
Make sure that you have the required software kits and license keys to hand too - for all potentially required old and new versions. Hopefully you won't need them. The very act of writing/developing an plan of action/steps for an upgrade is usually enough to catch most potential problems. As long as you also take your time to read the install/upgrade guide, and review the install/upgrade tech note, and review the LBN, and use Veritas SORT - then you should be reasonably well prepared for your upgrades.
There is no simple rollback as such with NetBackup.
Best option would be to Take the Catalog Backup and Restore it if you have to roll back.
If the master happens to be a VM, take a snapshot/clone copy & ask VM Admin to keep the copy until you are not sure.
Agree with Tape_Archived
Usually the EMM database is being expanded with new tables for new features. While rolling back files is easy, there is no way of rolling back the added tables.
/Nicolai
Pray that you dont have to Roll Back.
There is no RollBack once Database is touched.
The Process is complicated and Better way will be to do a Plain DR Recovery.
Also, Although not stated anywhere. If it were me, I would follow below upgrade path
7.7 -> 8.0 -> 8.2
we always make a backup copy of /usr/openv before any linux master upgrade.
I will advise you take a copy of your production catalog and perform test-upgrade in a test or dev environment. Ensure everything work as expected in test or dev domain prior upgrading production. Best practise to also open a placeholder case with support incase your run into issue while upgrading production. But I can guarrantee if your dev upgrade come up clean, production upgrade should be walk in the park. Also, don't forget to run consistency check prior upgrade. All the best
If you are satisfied with the Answers, please mark the Helpful answer as a Solution so that this Thread Discussion can be Concluded and topic Closed
thanks all.
the upgrade was smoothly. we also upgraded RHEL as well.
after upgade, we encountered a bpjobd crash, activity monitor became empty and generated a few hundred of GB logs. We applied the EEB "eebinstaller_3998268_3_linuxR_x86 ". So far it works just fine.
