Table Of Contents
Disaster Recovery System Administration
About the Disaster Recovery System
Supported Features and Components
System Requirements
Accessing the Disaster Recovery System
Migrating from a Physical Server to a Virtual Server
How to Back Up Data in the Disaster Recovery System
Adding Backup Devices
Creating and Editing Backup Schedules
Enabling, Disabling, and Deleting Schedules
Starting a Manual Backup
Checking the Status of the Current Backup Job
How to Restore Data in the Disaster Recovery System
Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)
Restoring the First Node Only (Rebuilding the Publisher Alone)
Restoring Subsequent Cluster Nodes (With or Without Rebuild)
Restoring the Entire Cluster
How to View the Status and History of BackUp and Restore Jobs
Viewing the Restore Status
Viewing the Backup History
Viewing the Restore History
About Troubleshooting and Security for BackUp and Restore Operations
Trace File Locations
Command Line Interface Access to Backup and Restore Functions
Known Issues
DRS Restore to a Smaller Virtual Machine Fails
License MAC Value May Change During VMware Restoration
Error Messages During BackUp and Restore Operations
Related Documentation
Disaster Recovery System Administration
March 25, 2013
•
About the Disaster Recovery System
•Accessing the Disaster Recovery System
•Migrating from a Physical Server to a Virtual Server
•How to Back Up Data in the Disaster Recovery System
•How to Restore Data in the Disaster Recovery System
•How to View the Status and History of BackUp and Restore Jobs
•About Troubleshooting and Security for BackUp and Restore Operations
•Related Documentation
About the Disaster Recovery System
The Disaster Recovery System, which can be invoked from Cisco Unified Presence Administration, provides full data backup and restoration capabilities for all servers in a Cisco Unified Presence cluster. The Disaster Recovery System allows you to perform regularly scheduled automatic or user-invoked data backups.
•Supported Features and Components
•System Requirements
Supported Features and Components
The Disaster Recovery System includes the following capabilities:
•A user interface for performing backup and restore tasks. You can schedule back ups of the Cisco Unified Presence database and can choose which nodes in the cluster you want to restore.
•A distributed system architecture for performing backup and restore functions. The Disaster Recovery System contains two key functions, Master Agent (MA) and Local Agent (LA). The Master Agent coordinates backup and restore activity with all the Local Agents, which run backup and restore scripts on the server.
•Archive backups to a physical tape drive or remote SFTP server.
The Disaster Recovery System can back up and restore the following components. The system backs up all of its components automatically.
•Trace Collection Tool (TCT)
•Cisco Unified Presence Preference Files (PREFS)
•Cisco Unified Presence Database (DB)
•XMPP Configuration Files (XCP)
•Syslog Component (SYSLOGAGT)
•Platform
•Reporter
•Cluster Manager (CLM)
•Cisco Unified Presence Configuration Files (CUP)
System Requirements
To back up data to a remote device on the network, you must have configured an SFTP server. Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco through the Cisco Technology Developer Partner program (CTDP).
Accessing the Disaster Recovery System
Before You Begin
•If you are already signed into Cisco Unified Presence Administration, you must sign out of the application before you use the Disaster Recovery System.
•Make sure that Cisco Unified Presence is running on all servers in the cluster.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of the Cisco Unified Presence main window.
Step 2 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Troubleshooting Tip
You set the Administrator username and password during Cisco Unified Presence installation, and you can change the Administrator password or set up a new Administrator account using the Command Line Interface (CLI).
Related Topic
Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
Migrating from a Physical Server to a Virtual Server
You can perform a normal migration from a physical server with less than 80GB of storage space (accounting for RAID) to a virtual server without any modifications to the virtual machine. Normal migration is also possible when migrating from a physical machine with more than 80GB of storage space (accounting for RAID) to a virtual machine with a 5000 user deployment size. Special consideration is required, however, when the physical server has more than 80GB of storage space and the virtual machine has a user deployment size of 1000 or 2500. In this latter scenario, you must perform the following migration procedure.
Procedure
Step 1 Perform a backup of the Disaster Recovery System (DRS) on the physical machine as required in a normal migration.
Step 2 Deploy a new 5000 user OVA based virtual machine.
Step 3 Before installing the base Cisco Unified Presence OS image, change the following settings on the virtual machine:
If...
|
Then...
|
You are migrating to the 1000 user OVA specification
|
Perform the following steps in the specified order:
•Reduce the memory to 2GB (4GB for Cisco Unified Presence Release 8.6.2 or above.
•Reduce the CPU count to 1.
•Go to the Resources tab and set the CPU Reservation to 800MHz and the Memory Reservation to 2048MB.
|
You are migrating to the 2500 user OVA specification
|
Perform the following steps in the specified order:
•Reduce the memory to 4GB.
•Reduce the CPU count to 2.
•Go to the Resources tab and set the CPU Reservation to 2000MHz and the Memory Reservation to 4096MB.
|
Step 4 Install the Cisco Unified Presence OS as normal.
Step 5 Perform the DRS restore on the new virtual machine.
How to Back Up Data in the Disaster Recovery System
The Disaster Recovery System performs a cluster-level backup, which means that it collects backups for all servers in a Cisco Unified Presence cluster to a central location and archives the backup data to a physical storage device.
•Adding Backup Devices
•Creating and Editing Backup Schedules
•Enabling, Disabling, and Deleting Schedules
•Starting a Manual Backup
•Checking the Status of the Current Backup Job
Caution Always run the Post Install Setup wizard immediately
after a fresh installation of Cisco Unified Presence, and
before you back up or restore your data in the Disaster Recovery System. The operation fails if you install Cisco Unified Presence and attempt to back up or restore data in the Disaster Recovery System before you run the Post Install wizard. For more information, see the
Installation Guide for Cisco Unified Presence.
Adding Backup Devices
Before you use the Disaster Recover System, you must create backup devices on which to back up data and configure the locations where you want the backup files to be stored. You can configure up to 10 backup devices.
Before You Begin
Make sure that you have access to an SFTP server to configure a network storage location.The Disaster Recovery System only supports SFTP servers that are configured with an IPv4 address or hostname/Fully Qualified Domain Name (FQDN). The account that you use to access the SFTP server must have write permission for the selected path.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Backup > Backup Device.
Step 5 Select Add New to configure a new backup device.
Step 6 Enter the backup device name in the Backup device name field.
Step 7 Select one of the following backup devices and enter the appropriate field values in the Select Destination areas:
If you want to:
|
Action
|
Store the backup file on a locally attached tape drive
|
a. Select Tape Device.
b. Select the appropriate tape device from the Device name list box. You cannot span tapes or store more than one backup per tape.
|
Store the backup file on a networked drive that is accessed through an SFTP connection
|
a. Select Network Directory.
b. Enter the following required information:
–Server name: Name or IP address of the network server
–Path name: Path name for the directory where you want to store the backup file
–User name: Valid username for an account on the remote system
–Password: Valid password for the account on the remote system
–Number of backups to store on Network Directory: The number of backups to store on this network directory.
|
Step 8 Select Save to allow the Disaster Recovery System Master Agent to validate the selected SFTP server.
Troubleshooting Tips
•Be aware that if you sign in on a VMWare virtual machine, you cannot back up on a tape because the system disables the tape device option for VMWare users.
•The Disaster Recovery System restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. The Disaster Recovery System backs up and restores drfDevice.xml and drfSchedule.xml files. When the server restores these files, you do not need to reconfigure the Disaster Recovery System backup device and schedule.
•You can add, delete, and list devices through the Command Line Interface (CLI).
Related Topics
•Command Line Interface Access to Backup and Restore Functions
•Starting a Manual Backup
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Creating and Editing Backup Schedules
Creating and Editing Backup Schedules
You can create up to 10 backup schedules to back up the whole cluster. Each backup schedule has its own set of properties, including a schedule for automatic backups, the set of features to back up, and a storage location.
Before You Begin
•Configure your backup devices.
•Schedule backups during off-peak hours to avoid processing interruptions and impact to service.
•Make sure that all servers in the cluster are running the same version of Cisco Unified Presence and can be reached through the network. Servers that are not running at the time of the scheduled backup will not be backed up.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Backup > Scheduler.
Step 5 Do one of the following steps to add a new schedule or edit an existing schedule:
a. Select Add New to create a new schedule.
b. Select a name in the Schedule List column to configure an existing schedule.
Step 6 Enter a schedule name in the Schedule Name field. You cannot change the name of the default schedule.
Step 7 Select the backup device in the Select Backup Device area.
Step 8 Select the features to back up in the Select Features area. You must select at least one feature, for example, CUP.
Step 9 Select the date and time when you want the backup to begin in the Start Backup at area.
Step 10 Select the frequency at which you want the backup to occur in the Frequency area: Once, Daily, Weekly, or Monthly.
Troubleshooting Tips
•Be aware that your backup .tar files are encrypted by a randomly generated password. Cisco Unified Presence uses the cluster security password to encrypt this password and save it along with the backup .tar files. If you change this security password through the Command Line Interface or a fresh install, the Disaster Recovery System will prompt you for the old security password. Therefore, to use old backups, we recommend that you remember the old security password or perform a fresh backup immediately after you reset or change the password.
•The Disaster Recovery System restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. The Disaster Recovery System backs up and restores drfDevice.xml and drfSchedule.xml files. When the server restores these files, you do not need to reconfigure the Disaster Recovery System backup device and schedule
•While a backup is running, you cannot perform any tasks in Cisco Unified Operating System Administration because Disaster Recovery System locks the platform API to block all requests to Cisco Unified Operating System Administration. However, this does not block most CLI commands because only the CLI-based upgrade commands use the Platform API locking package.
•If you choose to back up on a weekly basis, you can also select the days of the week when the backup will occur. To set the backup frequency to Weekly, occurring Tuesday through Saturday, select Set Default.
•You can add, delete, and list devices through the Command Line Interface (CLI).
Related Topics
•Command Line Interface Access to Backup and Restore Functions
•Adding Backup Devices
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Enabling, Disabling, and Deleting Schedules
Enabling, Disabling, and Deleting Schedules
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Backup > Scheduler.
Step 5 Select the check boxes next to the schedules that you want to modify.
•Select Select All to select all schedules.
•Select Clear All to clear all check boxes.
Step 6 Select Enable Selected Schedules to enable the selected schedules.
Step 7 Select Disable Selected Schedules to disable the selected schedules,.
Step 8 Select Delete Selected to delete the selected schedules.
Troubleshooting Tips
•You cannot delete a backup device if you configured it as the backup device in a backup schedule.
•You can enable, disable, and delete backup schedules through the Command Line Interface (CLI).
Related Topics
•Starting a Manual Backup
•Command Line Interface Access to Backup and Restore Functions
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Checking the Status of the Current Backup Job
Starting a Manual Backup
Optionally, you can run a manual backup to back up the whole cluster.
Before You Begin
•Configure your backup devices.
•Schedule backups during off-peak hours to avoid processing interruptions and impact to service.
•Make sure that all servers in the cluster are running the same version of Cisco Unified Presence and can be reached through the network. Servers that are not running at the time of the scheduled backup will not be backed up.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Backup > Manual Backup.
Step 5 Select a backup device in the Select Backup Device area.
Step 6 Select the features to back up in the Select Features area, for example, CUP.
Step 7 Select Start Backup to start the manual backup.
Troubleshooting Tips
•Be aware that your backup .tar files are encrypted by a randomly generated password. Cisco Unified Presence uses the cluster security password to encrypt this password and save it along with the backup .tar files. If you change this security password through the Command Line Interface or a fresh install, the Disaster Recovery System will prompt you for the old security password. Therefore, to use old backups, we recommend that you remember the old security password or perform a fresh backup immediately after you reset or change the password.
•The Disaster Recovery System restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. The Disaster Recovery System backs up and restores drfDevice.xml and drfSchedule.xml files. When the server restores these files, you do not need to reconfigure the Disaster Recovery System backup device and schedule
•While a backup is running, you cannot perform any tasks in Cisco Unified Operating System Administration because Disaster Recovery System locks the platform API to block all requests to Cisco Unified Operating System Administration. However, this does not block most CLI commands as only the CLI-based upgrade commands use the Platform API locking package.
Related Topics
Adding Backup Devices
What To Do Next
Checking the Status of the Current Backup Job
Checking the Status of the Current Backup Job
While a backup is running, you can check the status of the current backup job.
Before You Begin
Configure and schedule the back up job. Be aware that if the backup to the remote server is not completed within 20 hours, the backup session will time out. You will then need to begin a fresh backup.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Backup > Current Status.
Step 5 Select the log filename hyperlink to view the backup log file.
Step 6 Perform one of the following actions if required:
a. Select Cancel Backup to cancel the current backup. The backup cancels after the current component completes its backup operation.
b. Select Refresh.
Troubleshooting Tips
The Result column indicates the staging results of individual components. The Status column indicates the status of the entire backup.
Related Topics
•Starting a Manual Backup
•Creating and Editing Backup Schedules.
•How to Restore Data in the Disaster Recovery System
How to Restore Data in the Disaster Recovery System
The Restore Wizard walks you through the steps that are required to restore a backup file:
•Select Storage Location—You must first select the storage location from which you want to restore a backup file.
•Select the Backup File—From a list of available files, you must select the backup file that you want to restore.
•Select Features—From the list of available features, you must select the features that you want to restore.
•Select Nodes—If the feature was backed up from multiple nodes, you must select the nodes that you want to restore.
•Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)
•Restoring the First Node Only (Rebuilding the Publisher Alone)
•Restoring Subsequent Cluster Nodes (With or Without Rebuild)
•Restoring the Entire Cluster
Caution Always run
the Post Install Setup wizard immediately
after a fresh installation of Cisco Unified Presence, and
before you back up or restore your data in the Disaster Recovery System. The operation fails if you install Cisco Unified Presence and attempt to back up or restore data in the Disaster Recovery System before you run the Post Install wizard. For more information, see the
Installation Guide for Cisco Unified Presence.
Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)
Use this procedure only if you are restoring the 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, go to Restoring the First Node Only (Rebuilding the Publisher Alone). If you intend to rebuild the entire cluster, go to Restoring the Entire Cluster.
Before You Begin
•Make sure that the Cisco Unified 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 of Cisco Unified Presence for restore. For example, the Disaster Recovery System does not allow a restore from version 7.0(1).1000-1 to version 7.1(2).1000-1, or from version 7.1(2).1000-1 to version 7.1(2).1000-2. (The last parts of the version number change when you install a service release or an engineering special.) In essence, the product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Cisco Unified Presence database restore. Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Presence.
•Make sure 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.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Restore > Restore Wizard.
Step 5 Complete the Restore Wizard as follows:
Window
|
Configuration Steps
|
Restore Wizard
Page 1 of 4
|
a. Select the backup device from which to restore.
b. Select Next.
|
Restore Wizard
Page 2 of 4
|
a. Select the backup file that you want to restore. The backup filename indicates the date and time that the system created the backup file.
b. Select Next.
|
Restore Wizard
Page 3 of 4
|
a. Select the features that you want to restore. Only the features that were backed up to the file that you select display.
b. Select Next.
|
Restore Wizard
Page 4 of 4
|
a. [Optional] Check Perform file integrity check using SHA1 Message Digest to run a File Integrity Check. A file integrity check is optional and required only in the case of SFTP backups. You need not run an integrity check when restoring from Tape and Local device backups.
b. When you are prompted to choose the node to restore, choose the appropriate node.
c. Select Restore to start restoring the data.
–If you choose the first node to restore the data, the Disaster Recovery System automatically restores the Cisco Unified Presence database on the subsequent nodes.
–If you selected the Perform file integrity check using SHA1 Message Digest check box, the Disaster Recovery System runs the File Integrity Check on each file when you select Restore. If the system finds discrepancies in any .tar file during the check, it aborts the restore process immediately.
Caution After you select the node to which you want the data restored, the system overwrites any existing data on that server.
|
Step 6 Restart the server.
Troubleshooting Tips
•Even if you are restoring only to the first node, you must restart all nodes in the cluster. We recommend that you restart the subsequent nodes before you restart the first node.
•Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore. Also, be aware that the File Integrity Check process consumes a lot of CPU and network bandwidth, which will considerably slow down the restore process.
•If replication does not set up properly, use the utils dbreplication status CLI command to check the Replication Status value on all nodes. The value on each node should equal 2.
•If a subsequent node is down or not connected to the cluster during the cluster restore, the database component restore will skip that node and proceed with the next one. You must carry out a fresh install of Cisco Unified Presence on these subsequent nodes.
•During the restore process, do not perform any tasks with Cisco Unified Presence Administration or Cisco Unified Presence User Pages.
•The Disaster Recovery System does not migrate data from Windows to Linux. A restore must run on the same product version as the backup.
Related Topics
•Known Issues
•Restoring the First Node Only (Rebuilding the Publisher Alone)
•Restoring the Entire Cluster
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
•Viewing the Restore Status
Restoring the First Node Only (Rebuilding the Publisher Alone)
Before You Begin
•Perform a fresh installation of Cisco Unified Presence on the first node or publisher server. For more information on installing Cisco Unified Presence, see the Installation Guide for Cisco Unified Presence.
•Make sure that the Cisco Unified Presence version that you 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 Presence for restore. For example, the Disaster Recovery System does not allow a restore from version 7.0(1).1000-1 to version 7.1(2).1000-1, or from version 7.1(2).1000-1 to version 7.1(2).1000-2. (The last parts of the version number change when you install a service release or an engineering special.) In essence, the product version needs to match, end-to-end, for the Disaster Recovery System to run a successful Cisco Unified Presence database restore. Disaster Recovery System adheres to strict version checking and allows restore only between matching versions of Cisco Unified Presence.
•Make sure 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.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Restore > Restore Wizard.
Step 5 Complete the Restore Wizard as follows:
Window
|
Configuration Steps
|
Restore Wizard
Page 1 of 4
|
a. Select the backup device from which to restore.
b. Select Next.
|
Restore Wizard
Page 2 of 4
|
a. Select the backup file that you want to restore. The backup filename indicates the date and time that the system created the backup file.
b. Select Next.
|
Restore Wizard
Page 3 of 4
|
a. Select the features that you want to restore. Only the features that were backed up to the file that you select display.
b. Select Next.
|
Restore Wizard
Page 4 of 4
|
a. Select Restore to start restoring the data.
b. Select to restore your data to the first node only (the publisher). Do not select the subsequent (subscriber) nodes; it will cause the restore to fail.
Caution After you select the node to which you want the data restored, the system overwrites any existing data on that server.
|
Step 6 Restart the server.
Troubleshooting Tips
•Restoring the first node restores the whole Cisco Unified Presence database to the cluster. This may take up to several hours based on number of nodes and size of database that you are restoring.
•During the restore process, do not perform any tasks with Cisco Unified Presence Administration or Cisco Unified Presence User Pages.
•Be aware that your backup .tar files are encrypted by a randomly generated password. Cisco Unified Presence uses the cluster security password to encrypt this password and save it along with the backup .tar files. If you change this security password between the backup and restore, the Disaster Recovery System will prompt you for the old security password. Therefore, to use old backups, we recommend that you remember the old security password or perform a fresh backup immediately after you reset or change the password.
•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.
Related Topics
•Known Issues
•Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)
•Restoring the Entire Cluster
•How to View the Status and History of BackUp and Restore Jobs
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Restoring Subsequent Cluster Nodes (With or Without Rebuild)
Restoring Subsequent Cluster Nodes (With or Without Rebuild)
Before You Begin
•Restore the publisher node, or first node, in the cluster.
•If you are restoring the subsequent nodes after a rebuild, you must configure the backup device.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Restore > Restore Wizard.
Step 5 Complete the Restore Wizard as follows:
Window
|
Configuration Steps
|
Restore Wizard
Page 1 of 4
|
a. Select the backup device from which to restore.
b. Select Next.
|
Restore Wizard
Page 2 of 4
|
a. Select the backup file that you want to restore.
Caution To restore subsequent nodes in the cluster, you must select the same backup file that you used to restore the first node.
b. Select Next.
|
Restore Wizard
Page 3 of 4
|
a. Select the features that you want to restore. Only the features that were backed up to the file that you select display.
b. Select Next.
|
Restore Wizard
Page 4 of 4
|
a. Select Restore to start restoring the data.
b. Select to restore only the subsequent nodes.
Caution After you select the node to which you want the data restored, the system overwrites any existing data on that server.
|
Step 6 Restart the server.
Step 7 Use the utils dbreplication status CLI command to check the Replication Status value on all nodes. The value on each node should equal 2.
Troubleshooting Tips
•During the restore process, do not perform any tasks with Cisco Unified Presence Administration or Cisco Unified Presence User Pages
•Depending on the size of your database and the components that you select to restore, the system can require one hour or more to restore.
•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.
Related Topics
•Known Issues
•Adding Backup Devices
•Restoring the First Node Only (Rebuilding the Publisher Alone)
•Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)
•Restoring the Entire Cluster
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Viewing the Restore Status
Restoring the 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. 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.
Before You Begin
•Before you restore a cluster, make sure that all nodes in the cluster are up and communicating with the first node. You must carry out a fresh install for the nodes that are down or not communicating with first node at the time of the restore.
•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 the following procedure.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Restore > Restore Wizard.
Step 5 Complete the Restore Wizard as follows:
Window
|
Configuration Steps
|
Restore Wizard
Page 1 of 4
|
a. Select the backup device from which to restore.
b. Select Next.
|
Restore Wizard
Page 2 of 4
|
a. Select the backup file that you want to restore. The backup filename indicates the date and time that the system created the backup file.
b. Select Next.
|
Restore Wizard
Page 3 of 4
|
a. Select the features that you want to restore. Only the features that were backed up to the file that you select display.
b. Select Next.
|
Restore Wizard
Page 4 of 4
|
a. Select Restore to start restoring the data.
b. Select to restore all the nodes in the cluster.
Caution After you select the node to which you want the data restored, the system overwrites any existing data on that server.
|
Step 6 Use the utils dbreplication status CLI command to check the Replication Status value on all nodes. The value on each node should equal 2.
Troubleshooting Tips
•The Disaster Recovery System restores the Cisco Unified Presence database on subsequent nodes automatically when you restore a first node. This may take up to several hours based on number of nodes and size of that database that you are restoring.
•If a subsequent node is down or not connected to the cluster during the cluster restore, the database component restore will skip that node and proceed with the next one. You must carry out a fresh install of Cisco Unified Presence on these subsequent nodes.
•During the restore process, do not perform any tasks with Cisco Unified Presence Administration or Cisco Unified Presence User Pages.
•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.
Related Topics
•Known Issues
•Restoring the First Node Only (Rebuilding the Publisher Alone)
•Restoring a Node or Cluster to a Last Known Good Configuration (No Rebuild)
•Cisco Unified Operating System Maintenance Guide for Cisco Unified Presence
What To Do Next
Viewing the Restore Status
How to View the Status and History of BackUp and Restore Jobs
Use these procedure to review the last 20 backup and restore jobs that have you have performed:
•Viewing the Restore Status
•Viewing the Backup History
•Viewing the Restore History
Viewing the Restore Status
While the restore process is running, you can check the status of the current restore job.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Restore > Status.
Step 5 Select the log filename hyperlink to view the restore log file.
Step 6 Select Refresh if required.
Related Topics
•How to Restore Data in the Disaster Recovery System
•Viewing the Restore History
Viewing the Backup History
From the Backup History window, you can view the backups that you have performed, including filename, storage location, completion date, result, and features that are backed up.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Backup > History to view the last 20 backup jobs.
Step 5 Select Refresh if required.
Related Topics
How to Back Up Data in the Disaster Recovery System
Viewing the Restore History
You can check the status of the current backup job and cancel the current backup job.From the Restore History window, you can view the restore operations that you have performed, including filename, storage location, completion date, result, and the features that you restored.
Procedure
Step 1 Select Navigation > Disaster Recovery System from the menu in the upper, right corner of Cisco Unified Presence main window.
Step 2 Select Go.
Step 3 Enter the same Administrator username and password that you use for the Cisco Unified Operating System.
Step 4 Select Restore > History to view the last 20 restore jobs.
Step 5 Select Refresh if required.
Related Topics
•How to Restore Data in the Disaster Recovery System
•Viewing the Restore Status
About Troubleshooting and Security for BackUp and Restore Operations
The system automatically activates both the Master Agent and the Local Agent on all nodes in the cluster. Each server in the Cisco Unified Presence cluster, including the server that contains the Master Agent, must have its own Local Agent to perform backup and restore functions for its server.
Note The Master Agent is functional only on the publisher node. The Master Agents on the subsequent nodes do not perform any functions.
The Disaster Recovery System uses an SSL-based communication between the Master Agent and the Local Agent for authentication and encryption of data between the Cisco Unified Presence cluster nodes. The Disaster Recovery System makes use of the IPSec certificates for its Public/Private Key encryption. Cisco Unified Presence handles this certificate exchange internally; you do not need to make any configuration changes to accommodate this exchange. However, be aware that if you delete the IPSEC truststore(hostname.pem) file from the Certificate Management pages in Cisco Unified Operating System Administration, the Disaster Recovery System will not work as expected. If you delete the IPSEC-trust file manually, make sure that you upload the IPSEC certificate to the IPSEC-trust. For more details, see the certificate management pages in the Cisco Unified Operating System Administration Guide.
•Trace File Locations
•Command Line Interface Access to Backup and Restore Functions
•Known Issues
•Error Messages During BackUp and Restore Operations
Trace File Locations
Trace files for the Master Agent, the GUI, and each Local Agent are written to the following locations:
•For the Master Agent, platform/drf/trace/drfMA0*
•For each Local Agent, platform/drf/trace/drfLA0*
•For the GUI, platform/drf/trace/drfConfLib0*
You can view trace files by using the Command Line Interface (CLI). See the Command Line Interface (CLI) Reference Guide for Cisco Unified Presence for more information.
Command Line Interface Access to Backup and Restore Functions
The Disaster Recovery System also provides command-line access to a subset of backup and restore functions, as shown in Table 1. For more information on these commands and on using the command line interface, see the Command Line Interface (CLI) Reference Guide for Cisco Unified Presence.
Table 1 Disaster Recovery System Command Line Interface
Command
|
Description
|
utils disaster_recovery backup
|
Starts a manual backup by using the features that are configured in the Disaster Recovery System interface.
|
utils disaster_recovery restore
|
Starts a restore and requires parameters for backup location, filename, features, and nodes to restore.
|
utils disaster_recovery status
|
Displays the status of ongoing backup or restore job.
|
utils disaster_recovery show_backupfiles
|
Displays existing backup files.
|
utils disaster_recovery cancel_backup
|
Cancels an ongoing backup job.
|
utils disaster_recovery show_registration
|
Displays the currently configured registration.
|
utils disaster_recovery show_tapeid
|
Displays the tape identification information.
|
Known Issues
•DRS Restore to a Smaller Virtual Machine Fails
•License MAC Value May Change During VMware Restoration
DRS Restore to a Smaller Virtual Machine Fails
Problem
A database restore may fail if you restore a Cisco Unified Presence server, that was originally installed on an MCS physical server, on a Virtual Machine (VM) disk.
Cause
MCS and VM disks are different in size. This failure occurs when you migrate from a larger disk size (for example, MCS with 146GB) to a smaller disk size (for example, VM with 75GB).
Solution
Reconfigure the VM disk to be the same disk size or larger than the MCS server.
License MAC Value May Change During VMware Restoration
Problem
A license MAC value may change during VMware restorations or physical to VMware restorations. As a result, you will receive a license warning on the Cisco Unified Presence Administration page. The warning will explain that there is an issue with the license and that the server is in a grace period.
Cause
This condition may occur if any of the following values are changed during restoration:
•Primary Node's Time Zone
•NTP Server 1
•NIC Speed
•NIC Duplex
•Host Name
•DHCP
•IP Address
•IP Mask
•Gateway Address
•Primary DNS
•SMTP Location
•Certificate Information
Solution
You need to request a new license with the new license MAC value, upload the new license, and restart the license manager.
Note Cisco highly recommends that you delete the old license before requesting a new one.
Error Messages During BackUp and Restore Operations
The Disaster Recovery System issues alarms for various errors that could occur during a backup or restore procedure. Table 2 provides a list of Cisco Disaster Recovery System alarms.
Table 2 Disaster Recovery System Alarms
Alarm Name
|
Description
|
Explanation
|
CiscoDRFBackupCancelInternalError
|
DRF Backup operation has encountered an error. Backup cancelled internally.
|
DRF Backup operation has encountered an error. Backup cancelled internally.
|
CiscoDRFBackupDeviceError
|
DRF backup process has problems accessing device.
|
DRF backup process encountered errors while accessing device.
|
CiscoDRFBackupFailure
|
Cisco DRF Backup process failed.
|
DRF backup process encountered errors.
|
CiscoDRFFailure
|
DRF Backup or Restore process has failed.
|
DRF Backup or Restore process encountered errors.
|
CiscoDRFInternalProcessFailure
|
DRF internal process has encountered an error.
|
DRF internal process encountered an error.
|
CiscoDRFLA2MAFailure
|
DRF Local Agent is not able to connect to Master Agent.
|
DRF Local Agent cannot connect to Master Agent.
|
CiscoDRFLocalAgentStartFailure
|
DRF Local Agent was not able to start.
|
DRF Local Agent might be down.
|
CiscoDRFMA2LAFailure
|
DRF Master Agent is not able to connect to Local Agent.
|
DRF Master Agent cannot connect to Local Agent.
|
CiscoDRFMABackupComponent
Failure
|
DRF was unable to backup at least one component.
|
DRF requested a component to back up its data; however, an error occurred during the backup process, and the component was not backed up.
|
CiscoDRFMABackupNodeDisconnect
|
The node being backed up disconnected from the Master Agent prior to being fully backed up.
|
The DRF Master Agent was running a backup operation on a Cisco Unified Presence node, and the node disconnected before the backup operation completed.
|
CiscoDRFMARestoreComponent
Failure
|
DRF was unable to restore at least one component.
|
DRF requested a component to restore its data; however, an error occurred during the restore process, and the component was not restored.
|
CiscoDRFMARestoreNodeDisconnect
|
The node being restored disconnected from the Master Agent prior to being fully restored.
|
The DRF Master Agent was running a restore operation on a Cisco Unified Presence node, and the node disconnected before the restore operation completed.
|
CiscoDRFMasterAgentStartFailure
|
DRF Master Agent was not able to start.
|
DRF Master Agent might be down.
|
CiscoDRFNoRegisteredComponent
|
No registered components available, backup failed.
|
DRF backup failed because no registered components are available.
|
CiscoDRFNoRegisteredFeature
|
No feature selected for backup.
|
No feature got selected for backup.
|
CiscoDRFRegistrationFailure
|
DRF Registration operation failed.
|
DRF Registration operation failed for a component due to some internal error.
|
CiscoDRFRestoreFailure
|
DRF restore process failed.
|
DRF restore process encountered errors.
|
CiscoDRFRestoreInternalError
|
DRF Restore operation has encountered an error. Restore cancelled internally.
|
DRF Restore operation has encountered an error. Restore cancelled internally.
|
CiscoDRFSftpFailure
|
DRF sftp operation has errors.
|
DRF SFTP operation has errors.
|
CiscoDRFTapeDeviceError
|
DRF is unable to access tape device.
|
DRF process encountered errors while accessing the tape device.
|
Related Documentation
For the latest Cisco Unified Presence requirements, see the Release Notes for Cisco Unified Presence on cisco.com.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Copyright © 2013 Cisco Systems, Inc. All rights reserved.
Feedback
