The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following procedure provides a quick, high-level reference to the major steps, in chronological order, that you must perform to do a restore procedure by using the Disaster Recovery System.
To restore Cisco Unified Communications Manager or IM and Presence Service, choose one of the following restore scenarios:
Restore node or cluster to last known good configuration—Use this procedure only if you are restoring this node to a last known good configuration. Do not use this after a hard drive failure or other hardware failure.
Restore entire cluster—Use this procedure to restore an entire cluster. If a major hard drive failure or upgrade occurs, or in the event of a hard drive migration, you may need to rebuild all nodes in the cluster.
Restore the first node only—Use this procedure only to restore the first publisher node in the cluster.
Restore subsequent cluster nodes—Use this procedure to restore the subscriber nodes in a cluster.
Restore cluster in one step after publisher rebuilds—Follow this procedure to restore the entire cluster in one step if the publisher has already been rebuilt.
Note | For publisher rebuild, you can restore only the publisher node or the entire cluster. Select 'Restore the first node only' to restore the publisher node. Select 'Restore the cluster in one-step' to restore the entire cluster. |
Review the following cautions, notes, and tips for general information on restoring backups:
Caution | Be aware that DRS encryption depends on the cluster security password. If you have changed the security password between the backup and this restore, DRS will ask for the old security password. Therefore, to use such old backups, you must remember the old security password or take a backup immediately after the security password change/reset. |
Caution | Do not make any configuration changes to Cisco Unified Communications Manager during a restore until after you have verified that database replication is functioning. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and the User Option windows. |
Note | If you are running a DRS restore on a SAML SSO enabled cluster with an OpenAM SSO backed up configuration, or on an OpenAM SSO enabled cluster with a SAML SSO backed up configuration, you will be logged out from the DRS GUI during restore. You can check the DRS restore status from the DRS GUI or from the CLI. To check the status from the DRS GUI, log into the DRS GUI and navigate to . To check the status from CLI, execute the utils disaster_recovery status command. |
Note | If you are restoring Cisco Unified Communications Manager, ensure that the Cisco Unified Communications Manager version that is installed on the server matches the version of the backup file that you want to restore. If you are restoring Cisco IM and Presence Service, ensure that the version that is installed on the server matches the version from the backup file that you want to restore. |
Note | For Cisco Unified Communications Manager restores, make sure that all cluster nodes are running the same version of Cisco Unified Communications Manager. For Cisco IM and Presence restores, make sure that all cluster nodes are running the same version of Cisco IM and Presence Service. If different nodes are running different versions, your backup or restore could fail. |
Note | The Disaster Recovery System does not migrate data from Windows to Linux or from Linux to Linux. A restore must run on the same product version as the backup. For information on data migration from a Windows-based platform to a Linux-based platform, see the Data Migration Assistant User Guide before following the steps in this procedure. |
Note | When you perform a DRS restore to migrate data to a new server, you must assign the new server the identical IP address and hostname that the old server used. Additionally, if DNS was configured when the backup was taken, then the same DNS configuration must be present prior to performing a restore. For more information about replacing a server, refer to the Replacing a Single Server or Cluster for Cisco Unified Communications Manager guide. |
Tip | Beginning with Cisco Unified Communications Manager Release 8.0(1), there is only one upgrade scenario in which you must run the Certificate Trust List (CTL) client after a hardware replacement. You must run the CTL client if you do not restore the subsequent node (subscriber) servers. In other cases, DRS backs up the certificates that you need. For more information, see the “Installing the CTL Client” and “Configuring the CTL Client” procedures in the Cisco Unified Communications Manager Security Guide. |
Use this procedure only if you are restoring a node to a last known good configuration. Do not use this after a hard drive failure or other hardware failure. If you intend to rebuild the publisher server, read the Restore the First Node Only. If you intend to rebuild the entire cluster, read the Restore Entire Cluster.
Caution | Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, DNS configuration, domain name, version, and deployment type of the restore matches the hostname, IP address, DNS configuration, domain name, version, and deployment type of the backup file that you want to restore. DRS does not restore across different hostnames, IP addresses, DNS configurations and deployment types. |
Note | Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore. |
Step 1 | Choose . The Restore Wizard Step 1 window displays. | ||||||
Step 2 | Choose the
backup device from which to restore in the Select Backup Device area. Then,
click
Next.
The Restore Wizard Step 2 window displays. | ||||||
Step 3 | Choose the
backup file that you want to restore.
| ||||||
Step 4 | Click Next. The Restore Wizard Step 3 window displays. | ||||||
Step 5 | Choose the
features that you want to restore.
| ||||||
Step 6 | Click Next. The Restore Wizard Step 4 window displays. | ||||||
Step 7 | Select the
Perform file integrity check using SHA1 Message Digest checkbox if you want to
run a file integrity check.
| ||||||
Step 8 | When you get prompted to choose the node to restore, choose the appropriate node. | ||||||
Step 9 | (Optional) If
the node that you chose to restore is a publisher node, from the Select Server
Name drop-down list box, choose the Cisco Unified Communications Manager
subscriber node from which you want to restore the publisher database. The
Disaster Recovery System restores all nondatabase information from the backup
file and pulls the latest database from the chosen subscriber node.
| ||||||
Step 10 | To start
restoring the data, click Restore.
| ||||||
Step 11 | Your data gets
restored on the node that you chose. To view the status of the restore, see the
Check Current Restore Job Status.
| ||||||
Step 12 | After the
restoration completes and the Percentage Complete field on the Restore Status
window in the Disaster Recovery System shows 100 percent, restart the server.
For more information on restarting, see the
Cisco
Unified Communications Operating System Administration Guide.
| ||||||
Step 13 | Replication
will setup automatically after a cluster reboot. Check the Replication Status
value on all nodes by using the "utils dbreplication runtimestate" CLI command
as described in the
Command
Line Interface Reference Guide for Cisco Unified Communications
Solutions. The value on each node should equal 2.
|
If a major hard drive failure or upgrade occurs, or in the event of a hard drive migration, you may need to rebuild all nodes in the cluster. Follow these steps to restore an entire cluster.
If you are doing most other types of hardware upgrades, such as replacing a network card or adding memory, you do not need to perform this procedure.
Note | You can restore the whole cluster as a single operation after you rebuild the publisher server and the subscriber servers, or to revert to a known good configuration. You do not need to restore the first node and the subsequent nodes in two separate operations. |
Note | Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore. |
Note | Before you restore a cluster, make sure that all nodes in the cluster are up and communicating with the first node. You must perform a fresh install for the nodes that are down or not communicating with first node at the time of the restore. |
Follow this procedure to restore the first node (publisher) server in the cluster.
Caution | Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, DNS configuration, and deployment type of the restore matches the hostname, IP address, DNS configuration, and deployment type of the backup file that you want to restore. DRS does not restore across different hostnames, IP addresses, DNS configurations, and deployment types. |
Note | Cisco recommends that you perform a fresh installation of Cisco Unified Communications Manager on the first node. For more information on installing Cisco Unified Communications Manager, see Installing Cisco Unified Communications Manager. |
Note | Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore. |
Note | Before you restore Cisco Unified Communications Manager, ensure that the Cisco Unified Communications Manager version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions of Cisco Unified Communications Manager for restore. For example, the Disaster Recovery System does not allow a restore from version 8.6.1.20000-1 to version 8.6.2.20000-2, or from version 8.6.2.20000-2 to 8.6.2.21900-5. |
Step 1 | Choose Restore > Restore Wizard. The Restore Wizard Step 1 window displays. | ||||||
Step 2 | In the Select Backup Device area, choose the appropriate backup device to restore. | ||||||
Step 3 | Click Next. The Restore Wizard Step 2 window displays. | ||||||
Step 4 | Choose the
backup file that you want to restore.
| ||||||
Step 5 | Click Next. The Restore Wizard Step 3 window displays. | ||||||
Step 6 | Choose the
features that you want to restore.
| ||||||
Step 7 | Click Next. The Restore Wizard Step 4 window displays. | ||||||
Step 8 | When you get
prompted to choose the nodes to restore, choose only the first node (the
publisher).
| ||||||
Step 9 | (Optional) From
the Select Server Name drop-down list box, choose the subscriber node from
which you want to restore the publisher database. The Disaster Recovery System
restores all nondatabase information from the backup file and pulls the latest
database from the chosen subscriber node.
| ||||||
Step 10 | To start restoring the data, click Restore. | ||||||
Step 11 | Your data gets
restored on the publisher node.
| ||||||
Step 12 | When the
restoration completes and the Percentage Complete field on the Restore Status
window in the Disaster Recovery System shows 100 percent, restart the server.
For more information on restarting, see the Cisco Unified Communications
Operating System Administration Guide.
| ||||||
Step 13 | When the first node has restarted and is running the restored version of Cisco Unified Communications Manager, restart the subsequent nodes. | ||||||
Step 14 | Replication
will be setup automatically after cluster reboot. Check the Replication Status
value on all nodes by using the "utils dbreplication runtimestate" CLI command
as described in the Command Line Interface Reference Guide for Cisco Unified
Communications Solutions. The value on each node should equal 2.
|
Follow this procedure to restore one or more subsequent nodes in the cluster.
Before you perform a restore operation, ensure that the hostname, IP address, DNS configuration, and deployment type of the restore matches the hostname, IP address, DNS configuration, and deployment type of the backup file that you want to restore. DRS does not restore across different hostnames, IP addresses, DNS configurations and deployment types.
Ensure that the software version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching software versions for restore operations.
If you are restoring the subsequent nodes after a rebuild, you must configure the backup device.
Step 1 | Click . The Restore Wizard Step 1window displays. | ||
Step 2 | In theSelect Backup Device area choose the backup device from which to restore. | ||
Step 3 | Click Next. The Restore Wizard Step 2 window displays. | ||
Step 4 | Choose the backup file that you want to restore. | ||
Step 5 | Click Next. The Restore Wizard Step 3 window displays. | ||
Step 6 | Choose the
features that you want to restore.
| ||
Step 7 | Click Next. The Restore Wizard Step 4 window displays. | ||
Step 8 | When you get prompted to choose the nodes to restore, choose only the subsequent nodes. | ||
Step 9 | Click Restore. | ||
Step 10 | Your data is
restored on the subsequent nodes.
| ||
Step 11 | After the restoration completes and the Percentage Complete field on the Restore Status window in the Disaster Recovery System shows 100 percent, restart the server. For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide. |
Follow this procedure to restore the entire cluster in one step if the Publisher has already been rebuilt or fresh installed.
Cisco recommends that you perform a fresh installation of Cisco Unified Communications Manager on the first node. For more information on installing Cisco Unified Communications Manager, see Installing Cisco Unified Communications Manager
Caution | Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, and deployment type of the restore matches the hostname, IP address and deployment type of the backup file that you want to restore. DRS does not restore across different hostnames, IP addresses and deployment types. |
Note | Extension Mobility Cross Cluster users who logged in to a remote cluster at backup shall remain logged in after restore. |
Note | Before you restore Cisco Unified Communications Manager, ensure that the Cisco Unified Communications Manager or Cisco IM and Presence version that is installed on the server matches the version of the backup file that you want to restore. The Disaster Recovery System supports only matching versions for restore. |
Step 1 | Navigate to the
Disaster Recovery System. Log in to Cisco Unified Communications Manager
Administration, choose
Disaster
Recovery System from the Navigation drop-down list box in the
upper, right corner of the Cisco Unified Communications Manager Administration
window, and click
Go.
The Disaster Recovery System Logon window displays. | ||||||||
Step 2 | Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration. | ||||||||
Step 3 | Configure the backup device. For more information, see Managing Backup Devices, page 7. | ||||||||
Step 4 | Navigate to . The Restore Wizard Step 1 window displays. | ||||||||
Step 5 | In the Select Backup Device area, choose the backup device from which to restore. | ||||||||
Step 6 | Click Next. The Restore Wizard Step 2 window displays. | ||||||||
Step 7 | Choose the
backup file that you want to restore.
| ||||||||
Step 8 | Click Next. The Restore Wizard Step 3 window displays. | ||||||||
Step 9 | Choose the
features that you want to restore.
| ||||||||
Step 10 | Click Next. The Restore Wizard Step 4 window displays. | ||||||||
Step 11 | Click
One-Step
Restore.
| ||||||||
Step 12 | When you get
prompted to choose the nodes to restore, choose all the nodes in the cluster.
| ||||||||
Step 13 | To start restoring the data, click Restore. | ||||||||
Step 14 | Your data gets
restored on all the nodes of the cluster. To view the status of the restore,
see Viewing the Restore Status, page 24.
| ||||||||
Step 15 | When the
restoration completes and the Percentage Complete field on the Restore Status
window in the Disaster Recovery System shows 100 percent, restart the servers.
For more information on restarting, see the
Cisco Unified
Communications Operating System Administration Guide.
| ||||||||
Step 16 | Replication will
be setup automatically after cluster reboot. Use the “utils dbreplication
runtimestate” CLI command as described in the
Command Line
Reference Guide for Cisco Unified Communications Solutions to check the
replication status value on all nodes. The value on each node should equal 2.
|
To check the status of the current restore job, perform the following steps:
Step 1 | Navigate to the Disaster Recovery System. Log in to Cisco Unified
Communications Manager Administration, choose Disaster Recovery System from the
Navigation menu in the upper, right corner of the Cisco Unified Communications
Manager Administration window, and click Go.
If you are checking the current restore job status for IM and Presence nodes, select
from the menu in the upper, right corner of Cisco Unified CM IM and Presence Administration window and click Go. The Disaster Recovery System Logon window displays. |
Step 2 | Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified Communications Operating System Administration. For Cisco Unified CM IM and Presence, log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified CM IM and Presence OS Administration. |
Step 3 | Navigate to
.
The Restore Status window displays.
The Status column in the Restore Status window shows the status of the restoration in progress, including the percentage of completion of the restore procedure. |
Step 4 | To view the restore log file, click the log filename link. |
A database restore may fail if you restore an IM and Presence Service node to a VM with smaller disks.
This failure occurs when you migrate from a larger disk size to a smaller disk size.
Deploy a VM for the restore from an OVA template that has 2 virtual disks.