On this page:
- Upgrade the Controller Using the Enterprise Console
- Controller High Availability
- Controller Data Backup and Restore
You can use the Enterprise Console to onboard and upgrade an HA Controller pair. For HA pairs that are not managed by the Enterprise Console, use the discover and upgrade option; for HA pairs that are managed by the Enterprise Console, you must use the upgrade option.
This topic describes:
- Upgrade method benefits
- Available upgrade methods
- How to shut down the HA Toolkit (HATK) implementation
Upgrade Method Benefits
The upgrade method enables you to:
- Perform a set of pre-upgrade validations. A summary of validation errors is provided to you before you modify the system's state.
- Quickly restore the older Controller version from the preserved secondary version in case of any upgrade issues. As you upgrade the primary server, the secondary server is isolated, thereby providing you a backup from which to quickly restore the service.
Available Upgrade Methods
Use the CLI, or follow a step-by-step Upgrade wizard that guides you through the UI, to perform the upgrade.
Use the CLI Method to Upgrade
You can use the CLI to upgrade the HA Controller pair. For more details, select upgrade using the CLI.
Use the Upgrade Wizard Method to Upgrade
You can use the Upgrade Wizard to follow a step-by-step procedure that guides you through the UI to perform the upgrade. For more details, select upgrade using the Upgrade Wizard.
Shut Down the HA Toolkit (HATK) Implementation
Before you start the Controller HA upgrade from a pre-Enterprise Console deployment, you must first shut down the watchdog and assassin processes. This is only required if you have installed the HA Toolkit previously.
To shut down the HA Toolkit implementation:
If the Controller services are installed with privilege escalation using setups option (-c option in install-init.sh) then running the following command on the secondary will stop the secondary appserver, watchdog, and assassin.
If the Controller services are installed with privilege escalation using sudoers option (-s option in install-init.sh) then running the following command on the secondary will stop the secondary appserver, watchdog, and assassin.
To check if the appserver, watchdog, and assassin stopped on the secondary, you can use the following commands based on the privilege escalation method used to install the Controller services:
For both stopping and checking the statuses, if you do not remember the privilege escalation method used to install services, then you can use both variants, one after the other, in any order.