Use this procedure to determine whether to deploy the same version of Cluster Control Manager used when performing the backup or delete any surviving virtual machine remnants before restoring Avaya Common Services.
Before you begin
Determine which course of action is applicable to your situation.
Use one of the following options, depending on whether or not your CCM and nodes are intact and healthy.
Option 1 - CCM and cluster nodes are intact and healthy:
Deploy the same version of Cluster Control Manager you used when performing the backup. Ensure that you also use the same configuration, including the same IP address, number of nodes, Node IP address, Node version, FQDN, enrollment password, disk size, CPU, and memory.
Determine if your backup archive is the same version as your CCM. You can find the Cluster Control Manager version by looking at the backup file name. The format of the backup file name is <ccm hostname or IP>-<common services product version>-<ccm version>-<timestamp>.tgz.
Option 2 - CCM and cluster nodes are not intact and healthy:
Delete any surviving virtual machine remnants, such as virtual machine cluster nodes, from vCenter manually. You can power off and delete these virtual machine remnants in any order.
