Restoring Avaya Common Services in an online deployment environment

Last Updated : Nov 29, 2022 |
Prolog information
Metadata
Keywords:
Use this procedure to recover from a full cluster outage when one or more of the virtual machines in the solution are lost. This procedure restores Cluster Control Manager, infrastructure, and services. It does not restore service application data.
If the CCM and cluster nodes are intact and healthy, you can use your existing Cluster Control Manager and nodes, but if it not intact and healthy you can delete the Cluster Control Manager and nodes and create new.
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
  • Perform a backup and locate your backup file.
  • 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.
  1. Log in to Cluster Control Manager.
  2. On Cluster Control Manager, run the screen command to run the restore process in the background.
    ADDITIONAL INFORMATION:
    When running the restore process in the background, if you need to detach from the SSH session, see Detaching from the restore SSH session.
  3. Run one of the following commands to start the restore process:
    ADDITIONAL INFORMATION:
    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/ccmClusterBackup directory.
    • ccm restore all --remote-server "<FQDN/IP> [-p <port>] -u <username>" <path to backup file>: 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 all --local <path to backup file>: Restores from the local <path to backup file> directory. This command overrides the configured archive destination.
    • ccm restore all <path to backup file>
    ADDITIONAL INFORMATION:
    In 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.
  4. If you used the --remote-server option, enter the remote server password when prompted.
  5. If you did not configure the password for the backup file, enter it when prompted.
  6. To confirm the restore, type y.
  7. When prompted, enter your Avaya SSO credentials.
  8. Wait for the cluster to fully initialize.
  9. Wait approximately 30 minutes, then run ccm smoke-test on Cluster Control Manager and confirm that all tests pass. If ccm smoke-test fails, run it again in 10 minutes. If the test continuously fails for over an hour, contact your technical support representative.
  10. On Cluster Control Manager, run ccm status --pod-details and ensure that the status of all pods is Running or Completed.
    ADDITIONAL INFORMATION:
    When a deployment is complete, the status of all services, except for tools-policy, nfs-provisioner, and utility-service, is Deployed.
Next steps
  • 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.
  • If you imported third-party certificates, the system will not recognize them after the restore. Therefore, you must repeat the import process for the restored cluster to use new third-party certificates.