Cisco Prime Collaboration Assurance Guide - Standard, 10.0
Performing Backup and Restore
Downloads: This chapterpdf (PDF - 1.39MB) The complete bookPDF (PDF - 3.21MB) | Feedback

Performing Backup and Restore

Prime Collaboration allows you to back up and restore your data. You can schedule periodic backups using the Prime Collaboration user interface, or run backup commands manually by logging in to the system as an admin user (CLI user). However, you must manually run restore commands by logging in to the system as an admin user.


Note


  • CLI is supported only through SSH; telnet is not supported. The port used for Prime Collaboration Assurance is 26, for Prime Collaboration Provisioning it is 22.
  • The application stop cpcm command takes 10 minutes to complete execution and application start cpcm takes 10 to 15 minutes to complete execution.

Overview of Backup and Restore

Although the Prime Collaboration Assurance and Prime Collaboration Provisioning applications (UI) are converged, you must perform backups on the respective Assurance and Provisioning servers.

Only Prime Collaboration Assurance backup and restore are covered in this guide. For information about Prime Collaboration Provisioning backup and restore, see "Provisioning Database Backup and Restore" chapter in Cisco Prime Collaboration 10.0 Provisioning Guide.


Note


Not all information covered in this section is applicable to Prime Collaboration Assurance Standard mode. See Standard and Advanced Prime Collaboration Assurance for information about feature support in Standard and Advanced modes.

Prime Collaboration Assurance uses the following purge policy:

The backup and restore service allows you back up the database, configuration files, and log files to either a remote location or a local disk. Files in following folders are backed up by the backup service:

Folder Name

Type of Data

emms database

Database

cpcm/conf

Configuration files

cpcm/export

Troubleshooting and endpoint utilization reports

cpcm/logs and tomcat/logs

Assurance application and Tomcat log files

jre/lib/security

Keystore files


Note


The data backup may take a long time (up to12 hours), depending on the number of managed devices in the Prime Collaboration Assurance server. It is recommended that you schedule backups during the non-business hours, because, this operation will severely slow down the Prime Collaboration Assurance UI performance.

Scheduling Backup using Prime Collaboration User Interface

You can schedule and run backup for both Assurance and Provisioning from the user interface. You can use SFTP, FTP, or local connection to create backup.

You must be logged in as an administrator to perform backup.

To create a new backup job:


    Step 1   Choose Administration > Backup Management.
    Step 2   In the Backup Management page, click New.
    Step 3   Enter a name for the backup job.

    If backup name is not specified, the Backup Title field is defaulted with date stamp.

    Step 4   Select the backup category.
    Step 5   Enter the Connection settings.

    You can use SFTP, FTP, or local connection to create backup.

    If you select SFTP or FTP, provide the following details:

    • IP address of the server where the backup files need to be saved
    • Path to the backup location
    • Port (for SFTP only)
    • Username
    • Password

    Click Test to test the SFTP or FTP connection using the credentials.

    If you select local, specify the location to save the backup files on your local machine.

    For a local backup, you can specify the number of backup files to be saved, using the Backup History drop-down list. By default, the last two backup files are saved. You can save upto nine backup files.

    Step 6   Specify the backup start time and recurrence interval.

    The time displayed in the date picker is the client browser time.

    Step 7   (Optional) Enter the e-mail IDs to which the backup status notification needs to be sent. You must separate the e-mail IDs using comma.
    Step 8   Click Save.

    The scheduled backup job is listed in the Backup Management page.

    You can click Run Now to run the backup immediately.


    Backup using CLI

    Backup and Restore using CLI can be performed in the following ways:

    Restoring on the Same System

    The following sections describe the process of backing up data and restoring it on the same system.

    Creating a Repository on an FTP, SFTP, or TFTP Server

    You must create a repository before backing up the data. By default, the backup service creates a *.tar.gpg file under the configured repository. The backed-up file is in a compressed format. The repository can be on CD-ROM, disk, HTTP, FTP, SFTP, or TFTP.

        Command or Action Purpose
      Step 1 Log in to the Prime Collaboration Assurance server with the account that you created during installation. The default login is admin.    
      Step 2 Enter the following commands to create a repository on a disk:  
      admin# config t
      admin(config)# repository RepositoryName
      admin(config-Repository)# url ftp://ftpserver/directory
      admin(config-Repository)# user UserName password {plain | hash} Password
      admin(config-Repository)# exit
      admin(config)# exit

      Where:

      • RepositoryName is the location to which files should be backed up. This name can contain a maximum of 30 alphanumeric characters.
      • ftp://ftpserver/directory is the FTP server and the directory on the server to which the file is transferred. You can also use SFTP, HTTP, disk, or TFTP instead of FTP.
      • UserName and { plain | hash} Password are the username and password for the FTP, SFTP, or TFTP server. hash specifies an encrypted password, and plain specifies an unencrypted plain text password. For example:
        
                        
                      admin# config t
        admin(config)# repository tmp
        admin(config-Repository)# url ftp://ftp.cisco.com/incoming
        admin(config-Repository)# user john password plain john!23
        admin(config-Repository)# exit
        admin(config)# exit
       

      Backing Up Data

      After creating the repository, log in to the Prime Collaboration Assurance server as admin and run the following command to back up the data:

      admin# backup Backupfilename repository RepositoryName application cpcm
      

      Where,

      • Backupfilename—Name of the backup file (without the extension-.tar.gpg). This name can be a maximum of 100 alphanumeric characters.
      • RepositoryName—Location to which the files are be backed up. This name can contain a maximum of 30 alphanumeric characters.

      The following message appears after the backup is complete:

      % Creating backup with timestamped filename: Backupfilename-Timestamp.tar.gpg
      

      % Creating backup with timestamped filename: Backupfilename-Timestamp.tar.gpg

      The backup file is suffixed with the time stamp ( YYMMDD-HHMM) and file extension .tar.gpg and saved in the repository. For example:

      
                 
               
      admin# backup cmbackup repository tmp application  
                 cpcm
      

      The following message appears after the backup is complete:

      
                 
               
      % Creating backup with timestamped filename: cmbackup-110218-0954.tar.gpg
      

      Restoring Data

      To restore the data, Log in to the Prime Collaboration Assurance server as admin and run the following command:

      
                 
               admin# restore Backupfilename repository RepositoryName application cpcm

      Where , Backupfilename is the name of the backup file suffixed with the timestamp ( YYMMDD-HHMM) and file extension .tar.gpg.

      For example:

      
                 
               
      admin# restore cmbackup-110218-0954.tar.gpg repository tmp application cpcm
      

      Restoring on a New System

      Prime Collaboration allows you to back up the data of a system and restore the data in another system in the event of total system failure.

      Before you back up files, change the “qovr” database instance password in the system where you perform backup and use the same password in the new system (where you restore the files).

      The process for creating a backup is the same as in the case of Restoring on the Same System see also, Creating a Repository on an FTP, SFTP, or TFTP Server.

      To change the “qovr” database instance password of a system in execution, before backup:


        Step 1   Log in to the system as a root user.
        Step 2   Stop the Prime Collaboration Assurance server:
        
                     
                   
        /opt/emms/emsam/bin/cpcmcontrol.sh stop
        

        (the process takes 10 minutes to complete)

        Step 3   Run the following command:
        
                     
                   
        perl opt/CSCOpx/bin/dbpasswd.pl dsn=qovr npwd=”new password”
        

        Use this new qovr database password in the new system where you restore the files.

        Step 4   Start the Prime Collaboration Assurance server:
        
                     
                   
        /opt/emms/emsam/bin/cpcmcontrol.sh start
        

        (the process takes 15 minutes to complete)

        Step 5   Log in as administrator and perform backup as described in Backing Up Data. See also, Creating a Repository on an FTP, SFTP, or TFTP Server.

        What to Do Next

        To restore the backup from another system, the following prerequisites must be met:

        • Ensure that the system to which data is restored must have the same MAC address as that of the system that was backed up (IP address and the hostname can be different). In the case you are unable to assign the MAC address of the original system (that was backed up) to another system, contact Cisco TAC for information on a new license file (for a new MAC address).
        • Change the “qovr” database instance password in the system where you perform backup and use the same password in the new system (where you restore the files)

        To restore the backup from another system, log in as administrator and perform restore as described in Restoring Data.


        Note


        You must rediscover all the devices post restore.

        Listing the Repository Data

        You can list the data within a repository, Log in to the Prime Collaboration Assurance server as admin and run the following command:

        admin# show repository RepositoryName
        

        For example:

        
                  
                
        admin#  
                 show repository tmp
        cmbackup-110218-0954.tar.gpg
        admin#
        

        Checking the Backup History

        You can check the backup history. Log in to the Prime Collaboration Assurance server as admin and run the following command:

        admin# show backup history

        For example:

        
                  
                
        admin#  
                 show backup history
        Fri Feb 18 09:54:39 UTC 2011: backup cmbackup-110218-0954.tar.gpg to repository
        temp: success
        Fri Feb 18 18:29:48 UTC 2011: backup cmbackup-110218-1829.tar.gpg to repository
        tmp: success
        admin#