Disaster Recovery System Administration Guide for Cisco Unified Communications Manager and IM & Presence Service, Release 9.0(1)
Cisco Unified CM Disaster Recovery System
Downloads: This chapterpdf (PDF - 1.4 MB) The complete bookPDF (PDF - 1.14 MB) | Feedback

Cisco Unified CM Disaster Recovery System

Contents

Cisco Unified CM Disaster Recovery System

Disaster Recovery System

The Disaster Recovery System (DRS), which can be invoked from Cisco Unified Communications Manager Administration, provides full data backup and restore capabilities for all servers in a Cisco Unified Communications Manager cluster. The Disaster Recovery System allows you to perform regularly scheduled automatic or user-invoked data backups.

The Disaster Recovery System performs a cluster-level backup, which means that it collects backups for all servers in a Cisco Unified Communications Manager cluster to a central location and archives the backup data to physical storage device.

DRS restores its own settings (backup device settings and schedule settings) as part of the platform backup/restore. DRS backs up and restores the drfDevice.xml and drfSchedule.xml files. When the server is restored with these files, you do not need to reconfigure DRS backup device and schedule.


Caution


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.



Caution


Before running a backup or restore, make sure that all cluster nodes are running the same version of Cisco Unified Communications Manager. If different nodes are running different versions of Cisco Unified Communications Manager, you will end up with a certificate mismatch and your backup or restore could fail.



Caution


Before you restore Cisco Unified Communications Manager, ensure that the hostname, IP address, DNS configuration, version, and deployment type of the restore matches the hostname, IP address, DNS configuration, version, and deployment type of the backup file that you want to restore.


When performing a system data restoration, you can choose which nodes in the cluster you want to restore.

The Disaster Recovery System includes the following capabilities:

  • A user interface for performing backup and restore tasks.

  • A distributed system architecture for performing backup and restore functions.

  • Scheduled backups.

  • Archive backups to a physical tape drive or remote SFTP server.

The Disaster Recovery System contains two key functions, Master Agent (MA) and Local Agent (LA). The Master Agent coordinates backup and restore activity with Local Agents.

The system automatically activates both the Master Agent and the Local Agent on all nodes in the cluster.


Caution


DRS encryption depends on the cluster security password. If you change this security password through the Command Line Interface or a fresh install, then it is recommended that you take a fresh backup immediately or remember the old security password.



Note


The Disaster Recovery Systemuses an SSL-based communication between the Master Agent and the Local Agent for authentication and encryption of data between the Cisco Unified Communications Manager cluster nodes. DRS makes use of the IPSec certificates for its Public/Private Key encryption. Be aware that if you delete the IPSEC truststore(hostname.pem) file from the Certificate Management pages, then DRS will not work as expected. If you delete the IPSEC-trust file manually, then you must ensure that you upload the IPSEC certificate to the IPSEC-trust. For more details, refer to the certificate management help pages in the Cisco Unified Communications Manager Security Guides.



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, refer to the Data Migration Assistant User Guide.



Caution


Schedule backups during off-peak hours to avoid call-processing interruptions and impact to service.



Caution


When you restore your data, the hostname, server IP address, and the deployment type must be the same as it was during the backup. DRS does not restore across different hostnames, IP addresses and deployment types.


Quick-Reference Tables for Backup and Restore Procedures

The following tables provide a quick reference for the backup and restore procedures.


Note


DRS backs up and restores the drfDevice.xml and drfSchedule.xml files. These backup device settings and schedule settings get restored as a part of the platform backup/restore. After the server is restored with these files, you do not need to reconfigure DRS backup device and schedule.


Backup Quick Reference

Table 1 provides a quick, high-level reference to the major steps, in chronological order, that you must perform to do a backup procedure by using the Disaster Recovery System.

Procedure
    Step 1   Create backup devices on which to back up data.

    Set Up Backup Devices

    Step 2   Create and edit backup schedules to back up data on a schedule. Either a manual or a scheduled backup backs up the whole cluster.

    Create and Edit Backup Schedules

    Step 3   Enable and disable backup schedules to back up data.

    Enable, Disable, and Delete Schedules

    Step 4   Estimate size of backup tar taken to SFTP device

    Estimate Size of Backup tar

    Step 5   Optionally, run a manual backup.

    Manual Backup

    Step 6   Check the Status of the Backup—While a backup is running, you can check the status of the current backup job.

    Check Current Backup Job Status


    Restore Quick Reference

    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.

    Procedure
      Step 1   Choose Storage Location—You must first choose the storage location from which you want to restore a backup file.
      Step 2   Choose the Backup File—From a list of available files, choose the backup file that you want to restore.
      Step 3   Choose Features—From the list of available features, choose the features that you want to restore.
      Step 4   Choose Nodes—If the feature was backed up from multiple nodes, you must choose the nodes that you want to restore.
      Step 5   Start the Restore.
      Step 6   Check the Status of the Restore—While the restore process is running, you can check the status of the current restore job.

      Supported Features and Components

      Disaster Recovery System can back up and restore the following components. The system backs up all of its components automatically.

      • Cisco Unified Communications Manager database (CCMDB), includes Cisco Unified Communications Manager/CDR Analysis and Reporting/Call Detail Records)

      • Platform

      • Music On Hold (MOH) Audio Files

      • BAT Bulk Provisioning Service (BPS)

      • CCM Preference Files (CCMPREFS)

      • TFTP Phone device files (TFTP)

      • SNMP Syslog Component (SYSLOGAGT SNMP)

      • SNMP CDP Subagent (CDPAGT SNMP)

      • Trace Collection Tool (TCT)

      • Cluster Manager (CLM)

      • Cisco Extended Functions (CEF)

      System Requirements

      To back up data to a remote device on the network, you must have an SFTP server that is configured. Cisco allows you to use any SFTP server product but recommends SFTP products that have been certified with Cisco Technology Partners. Technology partners, such as GlobalSCAPE, certify their products with specified versions of Cisco Unified Communications Manager. For information on which vendors have certified their products with your version of Cisco Unified Communications Manager, see the Solutions Catalog on the Cisco Developer Network.

      For information on using GlobalSCAPE with supported Cisco Unified Communications versions, contact GlobalSCAPE.


      Note


      We recommend that you retest the DRS with your SFTP server after you upgrade your Unified Communications Manager, upgrade your SFTP server, or you switch to a different SFTP server. Perform this step to ensure that these components operate correctly together. As a best practice, perform a backup and restore on a standby or backup server.


      Use the information in the following table to determine which SFTP server solution to use in your system.

      Table 1 SFTP Server Information

      SFTP Server

      Information

      SFTP Server from a Technology Partner

      These servers are third party provided, third party tested, and jointly supported by TAC and the Cisco vendor.

      Version compatibility depends on the third party test. See the Technology Partner page if you upgrade their SFTP product and/or upgrade UCM for which versions compatible:

      https:/​/​marketplace.cisco.com

      SFTP Server from another Third Party

      These servers are third party provided, have limited Cisco testing, and are not officially supported by Cisco TAC.

      Version compatibility is on a best effort basis to establish compatible SFTP versions and Unified Communications Manager versions.

      For a fully tested and supported SFTP solution, use Cisco Prime Collaboration Deployment or a Technology Partner.

      Cisco uses the following servers for internal testing. You may use one of the servers, but you must contact the vendor for support:

      • Open SSH

      • Cygwin

      • Titan

      For information on how to configure Cygwin for use with Cisco Unified Communications Manager, see http:/​/​www.cisco.com/​en/​US/​docs/​security/​security_management/​cs-mars/​6.0/​initial/​configuration/​ig.pdf.

      Cisco does not support using the SFTP product freeFTDP. This is because of the 1 GB file size limit on this SFTP product.


      Note


      For issues with third-party products that have not been certified through the Cisco Technology Developer Program process, contact the third-party vendor for support



      Note


      While a backup or restore is running, you cannot perform any OS Administration tasks, because Disaster Recovery System blocks all OS Administration requests by locking the platform API. However, Disaster Recovery System does not block most CLI commands, because only the CLI-based upgrade commands use the Platform API locking package.



      Tip


      Schedule backups during periods when you expect less network traffic.



      Note


      Be aware that if you migrate to an HP DL380-G6 server (software-only), you will not be able to install older versions of Cisco Unified Communications Manager (5.x and 6.x) on the new server. Therefore, to be able to run a DRS backup, you must install the older version of Cisco Unified Communications Manager on your old publisher (which may no longer be supported). After this backup is complete, you can restore it on your HP DL380-G6 (software-only) publisher.


      Log In to Disaster Recovery System

      To access the Disaster Recovery System, choose Disaster Recovery System from the Navigation drop-down list box in the upper right corner of the Cisco Unified Communications Manager Administration window. 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.


      Note


      You set the Administrator username and password during Cisco Unified Communications Manager installation, and you can change the Administrator password or set up a new Administrator account by using the CLI. See the Command Line Interface Reference Guide for Cisco Unified Communications Solutions for more information.


      Master Agent

      The system automatically starts the Master Agent service on each node of the cluster, but the Master Agent is functional only on the publisher node. The Master Agents on the subscriber nodes do not perform any functions.

      The system automatically starts the Master Agent (MA) on the publisher node. The Master Agent performs the following duties:

      • The MA stores system-wide component registration information.

      • The MA maintains a complete set of scheduled tasks in an XML file. The MA updates this file when it receives updates of schedules from the user interface. The MA sends executable tasks to the applicable Local Agents, as scheduled. (Local Agents execute immediate-backup tasks without delay.)

      • You access the MA through the Disaster Recovery System user interface to perform activities such as configuring backup devices, scheduling backups by adding new backup schedules, viewing or updating an existing schedule, displaying status of executed schedules, and performing system restoration.

      • The MA stores backup data on a remote network location.

      Master Agent Functions

      The Master Agent (MA) performs the following duties:

      • The MA stores system-wide component registration information.

      • The MA maintains a complete set of scheduled tasks in an XML file. The MA updates this file when it receives updates of schedules from the user interface. The MA sends executable tasks to the applicable Local Agents, as scheduled. (Local Agents execute immediate-backup tasks without delay.)

      • You access the MA through the Disaster Recovery System user interface to perform activities such as configuring backup devices, scheduling backups by adding new backup schedules, viewing or updating an existing schedule, displaying status of executed schedules, and performing system restoration.

      • The MA stores backup data on a locally attached tape drive or a remote network location.

      Local Agents

      The server has a Local Agent to perform backup and restore functions.

      Each node in a Cisco Unified Communications Manager cluster, including the node that contains the Master Agent, must have its own Local Agent to perform backup and restore functions.


      Note


      By default, a Local Agent automatically gets activated on each node of the cluster.


      Local Agent Functions

      The Local Agent runs backup and restore scripts on the server.

      In a cluster, the Local Agent runs backup and restore scripts on each node in the cluster.


      Note


      The Disaster Recovery System uses an SSL-based communication between the Master Agent and the Local Agent for authentication and encryption of data between cluster nodes. DRS makes use of the IPsec certificates for its Public/Private Key encryption. This certificate exchange is handled internally. You do not need to make any configuration changes to accommodate this exchange.


      Set Up Backup Devices

      Before you use the Disaster Recovery System, you must configure the locations where you want the backup files to be stored. You can configure up to ten backup devices. You can add, delete, and list devices through the CLI. Perform the following steps to configure backup devices.

      Procedure
        Step 1   Log in to the Disaster Recovery System with the same administrator username and password that you use for Cisco Unified OS Administration or IM and Presence OS Administration .
        Step 2   Select Backup > Backup Device. The Backup Device List window displays.
        Step 3   Do either of the following:
        • To create a new backup device, click Add New.
        • To edit an existing backup device, select the device in the Backup Device list and click Edit Selected.
        • To delete a backup device, select it in the Backup Device list and click Delete Selected.

        You cannot delete a backup device that is configured as the backup device in a backup schedule.

        Step 4   Enter the backup device name in the Backup device name field.
        Note   

        The backup device name may contain only alphanumeric characters, spaces ( ), dashes (-) and underscores (_). Do not use any other characters.

        Step 5   In the Select Destination area, choose the location to which you want to save the backup file. The options are:
        1. Tape Device—Stores the backup file on a locally attached tape drive. Choose the tape device from the list.
          Note   

          Be aware that you cannot span tapes or store more than one backup on a tape.

          Note   

          Be aware that if you are logged in through a VMware virtual machine, you cannot back up on a tape. This is because the tape device option is disabled for VMware users.

        2. Network Directory—Stores the backup file on a network drive that is accessed through an SFTP connection. DRS only supports SFTP servers that are configured with an IPv4 address or hostname/Fully Qualified Domain Name (FQDN). Enter the following required information:
          • Host name/IP address: Hostname 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.

          Note   

          You must have access to an SFTP server to configure a network storage location. The SFTP path must exist before you create the backup. The account that is used to access the SFTP server must have write permission for the selected path.

        Step 6   Click Save.

        The DRS Master Agent validates the selected backup device to ensure that the username, password, server name, and directory path are valid. If any of these values are invalid, the save operation fails.


        Create and Edit Backup Schedules

        You can create up to fourteen backup schedules. 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


        Schedule backups during off-peak hours to avoid call-processing interruptions and impact to service.



        Note


        You can list and add backup schedules through the Command Line Interface.



        Note


        Be aware that your backup .tar files are encrypted by a randomly generated password. This password is then encrypted by using the cluster security password and gets saved along with the backup .tar files. You must remember this security password or take a backup immediately after the security password change/reset.


        Perform the following steps to manage backup schedules:

        Procedure
          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 creating and editing backup schedules for IM and Presence nodes, 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 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 OS 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 Backup > Scheduler.

          The Schedule List window displays.

          Step 4   Do one of the following steps to add a new schedule or edit an existing schedule
          1. To create a new schedule, click Add New.
          2. To configure an existing schedule, click its name in the Schedule List column.

            The scheduler window displays.

          Step 5   Enter a schedule name in the Schedule Name field.
          Note   

          You cannot change the name of the default schedule.

          Step 6   Select the backup device in the Select Backup Device area.
          Step 7   Select the features to back up in the Select Features area. You must choose at least one feature.
          Step 8   Choose the date and time when you want the backup to begin in the Start Backup at area.
          Step 9   Choose the frequency at which you want the backup to occur in the Frequency area: Once, Daily, Weekly, or Monthly. If you choose Weekly, you can also choose the days of the week when the backup will occur.
          Tip   

          To set the backup frequency to Weekly, occurring Tuesday through Saturday, click Set Default.

          Step 10   To update these settings, click Save.
          Step 11   To enable the schedule, click Enable Schedule.

          The next backup occurs automatically at the time that you set.

          Note   

          Ensure that all servers in the cluster are running the same version of Cisco Unified Communications Manager or Cisco IM and Presence Service and are reachable through the network. Servers that are not reachable at the time of the scheduled backup will not get backed up.

          Step 12   To disable the schedule, click Disable Schedule.

          Enable, Disable, and Delete Schedules


          Note


          You can enable, disable, and delete backup schedules through the Command Line Interface. For more information on CLI commands for DRS, refer to the Command-Line Interface.


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

            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   Navigate to Backup > Scheduler.

            The Schedule List window displays.

            Step 4   Check the check boxes next to the schedules that you want to modify.
            1. To select all schedules, click Select All.
            2. To clear all check boxes, click Clear All.
            Step 5   To enable the selected schedules, click Enable Selected Schedules.
            Step 6   To disable the selected schedules, click Disable Selected Schedules.
            Step 7   To delete the selected schedules, click Delete Selected.

            Estimate Size of Backup tar

            Follow this procedure to estimate the size of the backup tar that is performed on an SFTP device.


            Note


            Be aware that the calculated size is not an exact value but an estimated size of the backup tar. Size is calculated based on the actual backup size of a previous successful backup and may vary if the configuration changed since the last backup.



            Note


            Be aware that if no backup history exists for one or more of the selected features, Cisco Unified Communications Manager cannot estimate the size of the backup tar.


            Procedure
              Step 1   Log in to the Disaster Recovery System by using the same administrator username and password that you use for Cisco Unified OS Administration or IM and Presence OS Administration.
              Step 2   Select the Backup > Manual Backup menu.

              The Manual Backup window appears.

              Step 3   In the Select Features area, select the features to back up.
              Step 4   Click Estimate Size to get the estimated size of backup for the selected features.

              Manual Backup

              Follow this procedure to start a manual backup.


              Note


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



              Note


              Be aware that your backup .tar files are encrypted by a randomly generated password. This password is then encrypted by using the cluster security password and gets saved along with the backup .tar files. You must remember this security password or take a backup immediately after the security password change/reset.



              Note


              Before you run a backup, make sure that all cluster nodes are running the same version of Cisco Unified Communications Manager or Cisco Unified Communications Manager IM and Presence Service. If different nodes are running different versions, the certificates will not match and your backup could fail.


              Procedure
                Step 1   Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified OS Administration or IM and Presence OS Administration.
                Step 2   Navigate to Backup > Manual Backup. The Manual Backup window displays.
                Step 3   In the Select Backup Device area, select a backup device.
                Step 4   In the Select Features area, select the features to back up.
                Step 5   Click Start Backup to start the manual backup.
                Note   

                Be aware that because of “no space in remote server” or “interruptions in network connectivity” or any other reason, the backup process could fail. If this happens, address the reasons that caused the backup to fail and then start a fresh backup.


                Backup status

                You can check the status of the current backup job and cancel the current backup job. To view the backup history, see the Backup and Restore History.


                Caution


                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.


                Check Current Backup Job Status

                Perform the following steps to check the status of the current backup job.


                Caution


                Be aware that if the backup to the remote server is not completed within 20 hours, the backup session times out and you must begin a fresh backup.


                Procedure
                  Step 1   Log in to the Disaster Recovery System by using the same Administrator username and password that you use for Cisco Unified OS Administration or IM and Presence Administration.
                  Step 2   Select Backup > Current Status. The Backup Status window displays.
                  Step 3   To view the backup log file, click the log filename link.
                  Step 4   To cancel the current backup, click Cancel Backup.
                  Note   

                  The backup cancels after the current component completes its backup operation.


                  Restore Scenarios


                  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. Configuration changes include any changes that you make in Cisco Unified Communications Manager Administration, Cisco Unified Serviceability, and the User Option windows.



                  Caution


                  Do not perform any configuration tasks until the restore completes on all servers in the cluster, and until you have verified that database replication is functioning.



                  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 host name 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.



                  Note


                  For more information about replacing a server, refer to the Replacing a Single Server or Cluster for Cisco Unified Communications Manager guide.



                  Note


                  Before running a DRS restore, make sure that all cluster nodes are running the same version of Cisco Unified Communications Manager. If different nodes are running different versions of Cisco Unified Communications Manager, you will end up with a certificate mismatch and your restore could fail.



                  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.



                  Tip


                  For more information, see the "Installing the CTL Client" and "Configuring the CTL Client" procedures in the Cisco Unified Communications Manager Security Guide.


                  Restore Node Or Cluster to Last Known Good Configuration

                  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.


                  Procedure
                    Step 1   Choose Restore > Restore Wizard. 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.
                    Note   

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

                    Step 4   Click Next. The Restore Wizard Step 3 window displays.
                    Step 5   Choose the features that you want to restore.
                    Note   

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

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

                    The file integrity check is optional and is only required in the case of SFTP backups.

                    Note   

                    Be aware that the file integrity check process consumes a significant amount of CPU and network bandwidth, which considerably slows down the restore process.

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

                    This option appears only if the backup file that you selected includes the CCMDB database component and if the node that you chose is a publisher node.

                    Note   

                    In order to resolve the hostname, you must first configure a DNS server on the publisher, or to navigate to System > Server on the publisher to add the subscriber for which the database is going to be restored from.

                    Step 10   To start restoring the data, click Restore.
                    Note   

                    If you selected the Perform file integrity check using SHA1 Message Digest checkbox in Step 9, DRS runs a file integrity check on each file when you click Restore. If the system finds discrepancies in any .tar file during the check, the restore process will ERROR out the component that failed the integrity check and move to restore the next .tar file (that is, the next component).

                    Note   

                    After you choose the node to which you want the data restored, any existing data on that server gets overwritten.

                    Note   

                    If you choose the first node to restore the data, DRS automatically restores the Cisco Unified Communications Manager database on the subsequent nodes. Read Restore the First Node Only for more details.

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

                    During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.

                    Note   

                    Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore.

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

                    If you are restoring only to the first node, you must restart all nodes in the cluster. Make sure that you restart the first node before you restart the subsequent nodes.

                    Note   

                    After the first node has restarted and runs the restored version of Cisco Unified Communications Manager, restart the subsequent nodes.

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

                    Database replication on the subsequent nodes may take enough time to complete after the subsequent nodes restart, depending on the size of the cluster.

                    Tip   

                    If replication does not set up properly, use the "utils dbreplication rebuild" CLI command as described in the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.


                    Restore the First Node Only

                    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.


                    Procedure
                      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.
                      Note   

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

                      Step 5   Click Next. The Restore Wizard Step 3 window displays.
                      Step 6   Choose the features that you want to restore.
                      Note   

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

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

                      Do not select the subsequent (subscriber) nodes in this condition as this will result in failure of the restore attempt.

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

                      This option appears only if the backup file that you selected includes the CCMDB database component. Initially, only the publisher node is fully restored, but when you perform Step 15 and restore the subsequent cluster nodes, the Disaster Recovery System performs database replication and fully synchronizes all cluster node databases. This ensures that all cluster nodes are using current data.

                      Note   

                      Make sure the subscriber node that you chose is up and connected to the cluster. A subscriber node can be added manually to the cluster in Cisco Unified Communications Manager Administration (System > Server).

                      Step 10   To start restoring the data, click Restore.
                      Step 11   Your data gets restored on the publisher node.
                      Note   

                      During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.

                      Note   

                      Restoring the first node restores the whole Cisco Unified Communications Manager database to the cluster. This may take up to several hours based on number of nodes and size of database that is being restored.

                      Note   

                      Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore.

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

                      Restart of all the nodes in the cluster is required in case of restoring only to the first node.

                      Note   

                      Ensure that you restart the first node before you restart the subsequent nodes.

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

                      Database replication on the subsequent nodes may take enough time to complete after the subsequent nodes restart, depending on the size of the cluster.

                      Tip   

                      If replication does not set up properly, use the "utils dbreplication rebuild" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.


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


                      Procedure
                        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.
                        Note   

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

                        Step 5   Click Next. The Restore Wizard Step 3 window displays
                        Step 6   Click Next. The Restore Wizard Step 4 window displays.
                        Step 7   Choose all the nodes when prompted to choose restore nodes.
                        Step 8   Click Restoreto restore the data.
                        Note   

                        During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.

                        Note   

                        Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore.

                        Step 9   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(s). For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide.
                        Note   

                        Make sure that you restart the first node before you restart the subsequent nodes.

                        Note   

                        After the first node has restarted and is running the restored version of Cisco Unified Communications Manager, restart the subsequent nodes.

                        Step 10   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.
                        Note   

                        Database replication on the subsequent nodes may take enough time to complete after the subsequent node restarts, depending on the size of the cluster.

                        Tip   

                        If replication does not set up properly, use the "utils dbreplication rebuild" CLI command as described in the Command Line Interface Reference Guide for Cisco Unified Communications Solutions.


                        Restore Subsequent Cluster Nodes

                        Follow this procedure to restore one or more subsequent nodes in the cluster.

                        Before You Begin

                        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.

                        Procedure
                          Step 1   Click Restore > Restore Wizard. 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.
                          Note   

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

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

                          During the restore process, do not perform any tasks with Cisco Unified Communications Manager Administration or User Options.

                          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.

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


                          Procedure
                            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 Restore > Restore Wizard. 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.
                            Note   

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

                            Note   

                            Choose only the backup file of the cluster from which you want to restore the entire cluster.

                            Step 8   Click Next. The Restore Wizard Step 3 window displays.
                            Step 9   Choose the features that you want to restore.
                            Note    Only the features that were backed up to the file that you chose display.
                            Step 10   Click Next. The Restore Wizard Step 4 window displays.
                            Step 11   Click One-Step Restore.
                            Note   

                            This option appears on Restore Wizard Step 4 window only if the backup file selected for restore is the backup file of the cluster and the features chosen for restore includes the feature(s) that is registered with both publisher and subscriber nodes.

                            Note   

                            This option allows the publisher to become cluster aware and will take five minutes to do so. Once you click on this option, a status message displays as “Please wait for 5 minutes until Publisher becomes cluster aware and do not start any backup or restore activity in this time period.”

                            Note   

                            After the delay, if the publisher becomes cluster aware, a status message displays as “Publisher has become cluster aware. Please select the servers and click on Restore to start the restore of entire cluster.”

                            Note   

                            After the delay, if the publisher has not become cluster aware, a status message displays as “Publisher has failed to become cluster aware. Cannot start one-step restore. Please go ahead and do a normal two-step restore.” To restore the whole cluster in two-step (publisher and then subscriber), perform the steps mentioned in Restore the First Node Only and Restore Subsequent Cluster Nodes.

                            Step 12   When you get prompted to choose the nodes to restore, choose all the nodes in the cluster.
                            Note    The Disaster Recovery System restores the Cisco Unified Communications Manager database (CCMDB) 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 is being restored.
                            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.
                            Note    Depending on the size of your database and the components that you choose to restore, the system can require a few hours to restore.
                            Step 15   When the restoration completes and the Percentage Complete field on the Restore Status window in the Disaster Recovery System shows 100 percent, Check the Replication Status value on all nodes by using the “utils dbreplication runtimestate” CLI command as described in the Command Line Reference Guide for Cisco Unified Communications Solutions. The value on each node should equal 2.
                            Note   

                            Database replication on the subsequent nodes may take enough time to complete depending on the size of the cluster.

                            Tip   

                            If replication does not set up properly, use the “utils dbreplication reset “CLI command as described in the Command Line Reference Guide for Cisco Unified Communications Solutions.

                            Step 16   If the database replication status is 2, restart the servers. For more information on restarting, see the Cisco Unified Communications Operating System Administration Guide.
                            Note   

                            Make sure that you restart the subsequent nodes before you restart the first node

                            Note   

                            When the subsequent nodes have restarted, and is running the restored version of Cisco Unified Communications Manager, restart the first node.


                            Check Current Restore Job Status

                            To check the status of the current restore job, perform the following steps:

                            Procedure
                              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 Navigation > IM and Presence Disaster Recovery System 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 Restore > Status. 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.

                              Backup and Restore History

                              Using the following procedures, you can see the last 20 backup and restore jobs:

                              View Backup History

                              Perform the following steps to view the backup history.


                              Note


                              Backup files are encrypted and can be opened only by the system software.


                              Procedure
                                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 viewing backup history for IM and Presence nodes, 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 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 Backup > History. The Backup History window displays.
                                Step 4   From the Backup History window, you can view the backups that you have performed, including filename, backup device, completion date, result, version, features that are backed up, and failed features.
                                Note   

                                The Backup History window displays only the last 20 backup jobs.


                                View Restore History

                                Perform the following steps to view the restore history.

                                Procedure
                                  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 viewing restore history for IM and Presence nodes, 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 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 Restore > History. The Restore History window displays.
                                  Step 4   From the Restore History window, you can view the restores that you have performed, including filename, backup device, completion date, result, version, features that were restored, and failed features.
                                  Note   

                                  The Restore History window displays only the last 20 restore jobs.


                                  Trace Files

                                  In this release of the Disaster Recovery System, trace files for the Master Agent, the GUI, each Local Agent, and the JSch library get written to the following locations:

                                  • For the Master Agent, find the trace file at platform/drf/trace/drfMA0*

                                  • For each Local Agent, find the trace file at platform/drf/trace/drfLA0*

                                  • For the GUI, find the trace file at platform/drf/trace/drfConfLib0*

                                  • For the JSch, find the trace file at platform/drf/trace/drfJSch*

                                  You can view trace files by using the Command Line Interface. See the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions 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 Table 3. For more information on these commands and on using the command line interface, see the Command Line Interface Reference Guide for Cisco Unifed Communications Solutions.

                                  Table 2 Disaster Recovery System Command Line Interface

                                  Command

                                  Description

                                  utils disaster_recovery estimate_tar_size

                                  Displays estimated size of backup tar from SFTP/Local device and requires one parameter for feature list

                                  utils disaster_recovery backup

                                  Starts a manual backup by using the features that are configured in the Disaster Recovery System interface

                                  utils disaster_recovery jschLogs

                                  Enables or disables JSch library logging

                                  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

                                  utils disaster_recovery device add

                                  Adds the network or tape device

                                  utils disaster_recovery device delete

                                  Deletes the device

                                  utils disaster_recovery device list

                                  Lists all the devices

                                  utils disaster_recovery schedule add

                                  Adds a schedule

                                  utils disaster_recovery schedule delete

                                  Deletes a schedule

                                  utils disaster_recovery schedule disable

                                  Disables a schedule

                                  utils disaster_recovery schedule enable

                                  Enables a schedule

                                  utils disaster_recovery schedule list

                                  Lists all the schedules

                                  Alarms and Messages

                                  The Disaster Recovery System (DRS) issues alarms and other messages for various errors and other conditions that occur during a backup or restore procedure. Table 4 provides a list of Cisco DRS alarms.

                                  Table 3 Disaster Recovery System Alarms and Messages

                                  Alarm Name

                                  Description

                                  Explanation

                                  DRFBackupDeviceError

                                  DRF backup process has problems accessing device.

                                  DRS backup process encountered errors while it was accessing device.

                                  DRFBackupFailure

                                  Cisco DRF Backup process failed.

                                  DRS backup process encountered errors.

                                  DRFBackupInProgress

                                  New backup cannot start while another backup is still running

                                  DRS cannot start new backup while another backup is still running.

                                  DRFInternalProcessFailure

                                  DRF internal process encountered an error.

                                  DRS internal process encountered an error.

                                  DRFLA2MAFailure

                                  DRF Local Agent cannot connect to Master Agent.

                                  DRS Local Agent cannot connect to Master Agent.

                                  DRFLocalAgentStartFailure

                                  DRF Local Agent does not start.

                                  DRS Local Agent might be down.

                                  DRFMA2LAFailure

                                  DRF Master Agent does not connect to Local Agent.

                                  DRS Master Agent cannot connect to Local Agent.

                                  DRFMABackupComponentFailure

                                  DRF cannot back up at least one component.

                                  DRS requested a component to back up its data; however, an error occurred during the backup process, and the component did not get backed up.

                                  DRFMABackupNodeDisconnect

                                  The node that is being backed up disconnected from the Master Agent prior to being fully backed up.

                                  While the DRS Master Agent was running a backup operation on a Cisco Unified Communications Manager node, the node disconnected before the backup operation completed.

                                  DRFMARestoreComponentFailure

                                  DRF cannot restore at least one component.

                                  DRS requested a component to restore its data; however, an error occurred during the restore process, and the component did not get restored.

                                  DRFMARestoreNodeDisconnect

                                  The node that is being restored disconnected from the Master Agent prior to being fully restored.

                                  While the DRS Master Agent was running a restore operation on a Cisco Unified Communications Manager node, the node disconnected before the restore operation completed.

                                  DRFMasterAgentStartFailure

                                  DRF Master Agent did not start.

                                  DRS Master Agent might be down.

                                  DRFNoRegisteredComponent

                                  No registered components are available, so backup failed.

                                  DRS backup failed because no registered components are available.

                                  DRFNoRegisteredFeature

                                  No feature got selected for backup.

                                  No feature got selected for backup.

                                  DRFRestoreDeviceError

                                  DRF restore process has problems accessing device.

                                  DRS restore process cannot read from device.

                                  DRFRestoreFailure

                                  DRF restore process failed.

                                  DRS restore process encountered errors.

                                  DRFSftpFailure

                                  DRF SFTP operation has errors.

                                  Errors exist in DRS SFTP operation.

                                  DRFSecurityViolation

                                  DRF system detected a malicious pattern that could result in a security violation.

                                  The DRF Network Message contains a malicious pattern that could result in a security violation like code injection or directory traversal. DRF Network Message has been blocked.

                                  DRFTruststoreMissing

                                  The IPsec truststore is missing on the node.

                                  The IPsec truststore is missing on the node. DRF Local Agent cannot connect to Master Agent.

                                  DRFUnknownClient

                                  DRF Master Agent on the Pub received a Client connection request from an unknown server outside the cluster. The request has been rejected.

                                  The DRF Master Agent on the Pub received a Client connection request from an unknown server outside the cluster. The request has been rejected.

                                  DRFLocalDeviceError

                                  DRF is unable to access local device.

                                  DRF is unable to access local device.

                                  DRFBackupCompleted

                                  DRF backup completed successfully.

                                  DRF backup completed successfully.

                                  DRFRestoreCompleted

                                  DRF restore completed successfully.

                                  DRF restore completed successfully.

                                  DRFNoBackupTaken

                                  DRF did not find a valid backup of the current system.

                                  DRF did not find a valid backup of the current system after an Upgarde/Migration or Fresh Install.