Disaster Recovery System Administration Guide for Cisco Unified Communications Manager, Release 9.1(1)
IM and Presence Disaster Recovery System
Downloads: This chapterpdf (PDF - 459.0KB) The complete bookPDF (PDF - 1.05MB) | Feedback

IM and Presence Disaster Recovery System

IM and Presence Disaster Recovery System

Disaster Recovery System

The IM and Presence Disaster Recovery System, which can be invoked from Cisco Unified CM IM and Presence Administration, provides full data backup and restoration capabilities for all servers in an IM and Presence cluster. The Disaster Recovery System allows you to perform regularly scheduled automatic or user-invoked data backups.

Features and components

The Disaster Recovery System includes the following capabilities:

  • A user interface for performing backup and restore tasks. You can schedule backups of the IM and 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:

  • Trace Collection Tool (TCT)
  • IM and Presence Preference Files (PREFS)
  • IM and Presence Database (DB)
  • XMPP Configuration Files (XCP)
  • Syslog Component (SYSLOGAGT)
  • Platform
  • Reporter
  • Cluster Manager (CLM)
  • IM and Presence Configuration Files (CUP)

The Disaster Recovery System backs up all of its components automatically.

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).

Access the Disaster Recovery System

Before You Begin
  • If you are already signed into Cisco Unified CM IM and Presence Administration, you must sign out of the application before you use the Disaster Recovery System.
  • Make sure that IM and Presence is running on all servers in the cluster.
Procedure
    Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper, right corner of Cisco Unified CM IM and Presence Administration.
    Step 2   Enter the same Administrator username and password that you use to access the Cisco Unified IM and Presence Operating System Administration.

    Troubleshooting Tip

    You set the Administrator username and password during IM and Presence installation, and you can change the Administrator password or set up a new Administrator account using the Command Line Interface (CLI).

    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 an IM and Presence cluster to a central location and archives the backup data to a physical storage device.


    Caution


    Always run the Post Install Setup wizard immediately after a fresh installation of the IM and Presence Service, and before you back up or restore your data in the Disaster Recovery System. The operation fails if you install IM and 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.


    Add backup devices

    Before you use the Disaster Recovery 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. You can add, delete, and list devices through the Command Line Interface (CLI).


    Note


    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.


    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.

    Note


    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.


    Procedure
      Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper, right corner of Cisco Unified CM IM and Presence main window.
      Step 2   Select Go.
      Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration.
      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

      1. Select Tape Device.
      2. 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

      1. Select Network Directory.
      2. 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.

      What to Do Next

      Create and edit backup schedules.

      Create and edit 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.


      Caution


      Be aware that your backup .tar files are encrypted by a randomly generated password. IM and 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.


      Before You Begin
      • Configure your backup devices. You can add, delete, and list devices through the Command Line Interface (CLI).
      • 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 IM and 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.

      Note


      While a backup is running, you cannot perform any tasks in Cisco Unified IM and Presence Operating System Administration because Disaster Recovery System locks the platform API to block all requests to Cisco Unified IM and Presence Operating System Administration. However, this does not block most CLI commands because only the CLI-based upgrade commands use the Platform API locking package.


      Procedure
        Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper, right corner of Cisco Unified CM IM and Presence Administration.
        Step 2   Select Go.
        Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration.
        Step 4   Select Backup > Scheduler.
        Step 5   Do one of the following steps to add a new schedule or edit an existing schedule:
        1. Select Add New to create a new schedule.
        2. 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.

        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.


        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.

        What to Do Next

        Enable, disable and delete schedules

        Related References

        Enable, disable, and delete schedules

        Complete this procedure to enable, disable or delete schedules.

        You can also enable, disable, and delete backup schedules through the Command Line Interface (CLI).


        Note


        You cannot delete a backup device if you configured it as the backup device in a backup schedule.


        Procedure
          Step 1   Select Navigation > IM and Disaster Recovery System from the menu in the upper, right corner of Cisco Unified CM IM and Presence Administration.
          Step 2   Select Go.
          Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration.
          Step 4   Select Backup > Scheduler.
          Step 5   Select the check boxes next to the schedules that you want to modify.
          1. Select Select All to select all schedules.
          2. 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.

          What to Do Next

          Check the status of the current backup job.

          Related References

          Start manual backup

          Complete the following procedure to start a manual backup. Optionally, you can run a manual backup to back up the whole cluster.

          Caution


          Be aware that your backup .tar files are encrypted by a randomly generated password. IM and 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.


          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 IM and 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.
          • While a backup is running, you cannot perform any tasks in Cisco Unified IM and Presence Operating System Administration because Disaster Recovery System locks the platform API to block all requests to Cisco Unified IM and Presence Operating System Administration. However, this does not block most CLI commands as only the CLI-based upgrade commands use the Platform API locking package.
          Procedure
            Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration window.
            Step 2   Select Go.
            Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration.
            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.

            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.

            What to Do Next

            Check the status of the current backup job.

            Check status of 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 backup 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 > IM and Presence Disaster Recovery System from the menu in the upper, right corner of Cisco Unified CM IM and Presence Administration.
              Step 2   Select Go.
              Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration.
              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:
              1. Select Cancel Backup to cancel the current backup. The backup cancels after the current component completes its backup operation.
              2. Select Refresh.

              The Result column indicates the staging results of individual components. The Status column indicates the status of the entire backup.

              Related Information

              Restore scenarios

              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.

              Caution


              Always run the Post Install Setup wizard immediately after a fresh installation of the IM and Presence Service, and before you back up or restore your data in the Disaster Recovery System. The operation fails if you install IM and 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.


              Restore node or cluster to a good configuration

              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, see the topic on restoring the first node on the publisher server. If you intend to rebuild the entire cluster, see the relevant topic.

              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.


              Note


              The Disaster Recovery System does not migrate data from Windows to Linux. A restore must run on the same product version as the backup.


              Before You Begin
              • Make sure that the 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 of IM and Presence for restore. For example, the Disaster Recovery System does not allow a restore from version 8.6.2.10000-44 to version 8.6.3.10000-20, or from version 8.6.3.10000-20 to version 8.6.3.20000-1. (The last parts of the version number change when you install a service release or an engineering special.)
              • Make sure 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.

              Caution


              After you select the node to which you want the data restored, the system overwrites any existing data on that server.


              Procedure
                Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                Step 2   Select Go.
                Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                Step 4   Select Restore > Restore Wizard.
                Step 5   On the first screen of the Restore Wizard, select the backup device from which to restore.
                Step 6   On the second screen of the Restore Wizard, select the backup file that you want to restore.

                The backup filename indicates the date and time that the system created the backup file.

                Step 7   On the third screen of the Restore Wizard, select the features that you want to restore.

                Only the features that were backed up to the file that you select display.

                Step 8   [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.

                Step 9   Select Restore to start restoring the data.
                • If you choose the first node to restore the data, the Disaster Recovery System automatically restores the IM and 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 10   Restart the server.

                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.


                Troubleshooting Tips
                • 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 IM and Presence on these subsequent nodes.
                • During the restore process, do not perform any tasks with Cisco Unified CM IM and Presence Administration or IM and Presence User Pages.

                What to Do Next

                View the restore status.

                Related Information

                Restore publisher node

                Restoring the first node restores the whole IM and 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.


                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.


                Before You Begin
                • Perform a fresh installation of IM and Presence on the first node or publisher server. For more information on installing IM and Presence, see the Installation Guide for IM and Presence.
                • Make sure that the IM and 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 IM and Presence for restore. For example, the Disaster Recovery System does not allow a restore from version 8.6.2.10000-44 to version 8.6.3.10000-20, or from version 8.6.3.10000-20 to version 8.6.3.20000-1. (The last parts of the version number change when you install a service release or an engineering special.)
                • Make sure 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.
                • During the restore process, do not perform any tasks with Cisco Unified CM IM and Presence Administration or IM and Presence User Pages.

                Caution


                Be aware that your backup .tar files are encrypted by a randomly generated password. IM and 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.


                Procedure
                  Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                  Step 2   Select Go.
                  Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                  Step 4   Select Restore > Restore Wizard.
                  Step 5   On the first screen of the Restore Wizard, select the backup device from which to restore.
                  Step 6   On the second screen of the Restore Wizard, select the backup file that you want to restore.

                  The backup filename indicates the date and time that the system created the backup file.

                  Step 7   On the third screen of the Restore Wizard, select the features that you want to restore.

                  Only the features that were backed up to the file that you select display.

                  Step 8   On the final screen of the Restore Wizard, select Restore to start restoring the data

                  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 9   Restart the server.

                  What to Do Next

                  Restore subsequent nodes in the cluster.

                  Restore subsequent cluster nodes

                  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.


                  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.


                  Before You Begin
                  • Restore the publisher node in the cluster.
                  • If you are restoring the subsequent nodes after a rebuild, you must configure the backup device.
                  • During the restore process, do not perform any tasks with Cisco Unified CM IM and Presence Administration or IM and Presence User Pages.
                  Procedure
                    Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                    Step 2   Select Go.
                    Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                    Step 4   Select Restore > Restore Wizard.
                    Step 5   On the first screen of the Restore Wizard, select the backup device from which to restore.
                    Step 6   On the second screen of the Restore Wizard, 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.

                    Step 7   On the third screen of the Restore Wizard, select the features that you want to restore.

                    Only the features that were backed up to the file that you select display.

                    Step 8   On the final screen of the Restore Wizard, select Restore to start restoring the data

                    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 9   Restart the server.
                    Step 10   Use the utils dbreplication status CLI command to check the Replication Status value on all nodes. The value on each node should equal 2.

                    What to Do Next

                    View the restore status.

                    Related Information

                    Restore 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.

                    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 IM and Presence on these subsequent nodes.


                    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.


                    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.
                    • During the restore process, do not perform any tasks with Cisco Unified CM IM and Presence Administration or IM and Presence User Pages.
                    Procedure
                      Step 1   Select Navigation > IM and Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                      Step 2   Select Go.
                      Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                      Step 4   Select Restore > Restore Wizard.
                      Step 5   On the first screen of the Restore Wizard, select the backup device from which to restore.
                      Step 6   On the second screen of the Restore Wizard, select the backup file that you want to restore. The backup filename indicates the date and time that the system created the backup file.
                      Step 7   On the third screen of the Restore Wizard, select the features that you want to restore.

                      Only the features that were backed up to the file that you select display.

                      Step 8   On the final screen of the Restore Wizard, select Restore to start restoring the data

                      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 9   Use the utils dbreplication status CLI command to check the Replication Status value on all nodes. The value on each node should equal 2.

                      What to Do Next

                      View the restore status.

                      Related Information

                      Backup and restore history

                      Use these procedures to review the last 20 backup and restore jobs that you have performed.

                      View restore status

                      While the restore process is running, you can check the status of the current restore job.

                      Procedure
                        Step 1   Select Navigation > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                        Step 2   Select Go.
                        Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                        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 Tasks
                        Related Information

                        View 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 > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                          Step 2   Select Go.
                          Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                          Step 4   Select Backup > History to view the last 20 backup jobs.
                          Step 5   Select Refresh if required.

                          View 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 > IM and Presence Disaster Recovery System from the menu in the upper right corner of Cisco Unified CM IM and Presence Administration.
                            Step 2   Select Go.
                            Step 3   Enter the same Administrator username and password that you use for the Cisco Unified IM and Presence Operating System Administration .
                            Step 4   Select Restore > History to view the last 20 restore jobs.
                            Step 5   Select Refresh if required.

                            Related Tasks
                            Related Information

                            Data authentication and encryption

                            The system automatically activates both the Master Agent and the Local Agent on all nodes in the cluster. Each server in the IM and 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 IM and Presence cluster nodes. The Disaster Recovery System makes use of the IPSec certificates for its Public/Private Key encryption. IM and 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 IM and Presence 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.

                            Related References
                            Related Information

                            Trace files

                            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 Cisco Unified Communications Operating System Maintenance Guide for IM and Presence for more information.

                            Command Line Interface

                            The Disaster Recovery System also provides command-line access to a subset of backup and restore functions, as shown in the following table. For more information on these commands and on using the command line interface, see the Cisco Unified Communications Operating System Administration Guide.

                            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

                            Restore to virtual machine fails

                            Problem

                            A database restore may fail if you restore an IM and Presence server, that was originally installed on an MCS physical server, to one of the small (500 or 2000 user) OVA deployment virtual machines.

                            Cause

                            This failure occurs when you migrate from a physical server with storage of 80GB or more to a virtual machine configuration that is designed for a smaller database (less than 80GB).

                            Solution

                            Redeploy the virtual machine with one of the larger user deployment sizes (5000 or 15000) because these deployment sizes are provisioned with two 80GB virtual disks which can accommodate the larger database from the physical server. This solution requires you to reinstall the base IM and Presence image because you cannot add storage after installation.

                            Alarms

                            The Disaster Recovery System issues alarms for various errors that could occur during a backup or restore procedure. The following table 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.

                            CiscoDRFMABackupComponentFailure

                            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 an IM and Presence node, and the node disconnected before the backup operation completed.

                            CiscoDRFMARestoreComponentFailure

                            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 an IM and 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.