Use this procedure to recover Cluster Control Manager from an outage when the Cluster Control Manager virtual machine is lost. This procedure only restores Cluster Control Manager. It does not restore cluster nodes or application data.
Note:
This restore process is supported if the cluster or service version in the backup file is Common Services 1.3.0.x or later.
Before you begin
Locate the backup file.
Use the most recent valid backup file when restoring Cluster Control Manager.
Ensure that you have the password for the backup file.
Assess the node cluster state to determine which option to use for the restoration. For more information about the options, see Assessing cluster state.
Procedure
Log in to Cluster Control Manager.
Ensure that the IP address and version of Cluster Control Manager matches the IP address in the backup file name.
On Cluster Control Manager, run the screen command to run the restore process in the background.
Run one of the following commands to restore the Cluster Control Manager:
Note:
If your backup file is not accessible on a remote server, copy the backup file to Cluster Control Manager using a file transfer utility such as WinSCP.
You can use the /tmp or /var/avaya/artifactCache directory.
ccm restore --remote-server "<FQDN/IP> [-p <port>] -u <username>" <path to backup file> all: Restores from the remote directory path you specify. This command overrides the configured archive destination.
Include the double quotes as shown above for the --remote-server option. If you omit these quotes, the command will fail.
You need to include -p <port> if you are using a port other than the default port 22.
ccm restore --local all <artifact full path>: Restores from the local <path to backup file> directory. This command overrides the configured archive destination.
In all of these command options, replace <path to backup file> with the full path to the backup file. For example, /var/avaya/artifactCache/ccmClusterBackup/<backup-file>.tgz or home/<customer>/<backup-file>.tgz.
Use the same archive destination (local or remote) that you used for the backup.
If you used the --remote-server option, enter the remote server password when prompted.
If you did not configure the password for the backup file, enter it when prompted.
To confirm the restore, type y.
Wait for the restore process to finish.
To verify the restore, run the ccm status and swversion commands.
Next Steps
Power off and delete the non-functional Cluster Control Manager, which was lost during the outage, from vCenter manually.
The restore process disables file integrity validation. If you enabled file integrity validation previously, you can re-enable it by running the clusterFileIntegrity enable command.
