About OpsCenter upgrade failure scenarios
In the versions prior to OpsCenter 7.6, the upgrade process first upgrades the OpsCenter software and then the database. If the upgrade fails, the database can become inconsistent and you cannot get it back to the original state.
Starting from OpsCenter 7.6, the database is upgraded in the beginning that is during the pre-installation process. In case of upgrade failure, the older OpsCenter setup is still available for use.
By default, the OpsCenter database is upgraded in the beginning. If you want the OpsCenter software to be upgraded first, you need to do the following:
To change the default upgrade sequence to upgrade database in the end
- Make the following ENABLEPREDBUPGRADE registry entry on the OpsCenter Server host:
Windows
Create a registry value ENABLEPREDBUPGRADE=FALSE at the following location:
HKLM\\SOFTWARE\\Symantec\\OpsCenter\\Server
UNIX
Before starting the upgrade, run the following command: EXPORT ENABLEPREDBUPGRADE=FALSE
Note:
In case of Windows silent installation, you need to add the following in the response file: <InstallProperty Name="ENABLEPREDBUPGRADE" Value="FALSE" />
Table: Upgrade failure scenarios describes the possible upgrade failure scenarios and how you can recover the database in OpsCenter even though the upgrade has failed.
Table: Upgrade failure scenarios
Database upgrade | OpsCenter software upgrade | Required action |
|---|---|---|
|
Successful |
Failed |
To use the upgraded database
To revert to the previous OpsCenter setup after the software upgrade failure
|
|
Failed |
Failed because the database upgrade was failed |
|