Cisco Prime Collaboration Analytics Guide, 10.0
Backup and Restore for Prime Collaboration Analytics
Downloads: This chapterpdf (PDF - 1.17MB) The complete bookPDF (PDF - 2.17MB) | Feedback

Backup and Restore for Prime Collaboration Analytics

Backup and Restore for Prime Collaboration Analytics

Backup and restore for Prime Collaboration Analytics can be done only with root user privileges.

Performing Backup and Restore for Prime Collaboration Analytics

Prime Collaboration Analytics allows you to perform backup and restore, while you continue to use the Prime Collaboration Analytics GUI. However, until the backup is complete, the data displayed in the GUI may not be the latest.

Remember the following:
  • Do not take backup of the files in the same machine, because, the data for Prime Collaboration Analytics is huge. We recommend you to take backup on archive Linux server where you can create NFS mount.
  • Make a backup for Prime Collaboration Analytics first and then the Prime Collaboration Assurance backup. However, you must first restore the Prime Collaboration Assurance data, followed by the Prime Collaboration Analytics data.

To backup and restore the data:


    Step 1   On archive server, login as root and create a backup directory for backup storage and setup mounting point for remote access.To check if the user postgres user id is 448 and group id is 208, enter the following commands:

    id -u postgres

    id -g postgres

    1. If postgres does not exist, enter the following command to create it: useradd -g 208 -u 448 postgres.
    2. If postgres exists with a different user id or group id, execute the following commands:

      usermod -u 448 postgres

      groupmod -g 208 postgres

      find / -user <current uid> -exec chown -h 448 {}\;

      find / -group <current gid> -exec chown -h 208 {}\;

      usermod -g 208 postgres

    3. To create a folder for the backup, execute the following command: mkdir /opt/backup
    4. Open the file /etc/exports in an editor and add the following line: /opt/backup *(rw,sync,no_subtree_check,no_root_squash,anonuid=448,anongid=208)
    5. Change the user and group ownership of the backup folder: chown -R postgres:postgres /opt/backup
    6. Execute this command in the archive server to restart the nfs services: service nfs restart
    7. Set up the firewall for remote access. Open the file /etc/sysconfig/iptables in an editor and add the following line as first "-A INPUT" statements:

      -A INPUT -s <Assurance server IP Address> -m state --state NEW -p udp -j ACCEPT

      -A INPUT -s <Assurance server IP Address> -m state --state NEW -p tcp -j ACCEPT

    8. Execute this command to restart the IP tables services. service iptables restart.
    Step 2   On Prime Collaboration Assurance server , create a backup directory, which mounts the archive server.
    1. Login as root using SSH with port 26.
    2. To check if the remote mount point is set up, enter the following command: showmount -e <remote archive server ip>
    3. Enter the following command: su - postgres
    4. Enter the following command to create a folder for the backup. mkdir /opt/postgres/9.2/backup
    5. Exit
    6. Enter the following command to mount the backup folder: mount <archive backup server ip>:/opt/backup /opt/postgres/9.2/backup
    Step 3   To configure backup on the Prime Collaboration Assurance server :
    1. Enter the goemsam command.
    2. Enter the following command: ./bin/analytics_backup_config.sh /opt/postgres/9.2/backup
    Step 4   To back up the Prime Collaboration Assurance server , start the online backup as root user.
    1. Enter the goemsam command.
    2. Enter the following command: ./bin/analytics_online_backup.sh /opt/postgres/9.2/backup
    Step 5   On restore Prime Collaboration Assurance server , restore the backup as root user.
    1. If the restore Prime Collaboration Assurance server is different from the backup server, then set up the remote mounting point as defined in Step 2. Ensure the firewall is also set properly on the archive server: the restore server ip is configured in /etc/sysconfig/iptables on the archive server.
    2. Enter the goemsam command.
    3. Enter the following command: ./bin/analytics_restore.sh /opt/postgres/9.2/backup
    4. After restore, restart the Prime Collaboration Assurance server :

      ./bin/cpcmcontrol.sh stop

      ./bin/cpcmcontrol.sh start

    Step 6   (Optional) Since Analytics data is not updated during the backup, it is recommended to back up the Prime Collaboration Assurance during weekends or non-business hours.
    1. For example, to schedule for a backup every Saturday morning at 8.00, enter the following commands:

      crontab -e: to update the current cron job.

      Append the following line in config file, save, and exit: 0 8 * * 6 /opt/emms/emsam/bin/analytics_online_backup.sh /opt/postgres/9.2/backup

    2. To disable the weekly cron job, remove the same line (mentioned above) by executing crontab -e: again.
    Step 7   (Optional) On Prime Collaboration Assurance server , to clean up the archive server disk space after a successful restore, perform the following:
    Note    Before the cleanup, ensure if the restored Prime Collaboration Analytics server works fine.
    1. Enter the goemsam command.
    2. Enter the following command to clean up the disk space: ./bin/analytics_clean_backup.sh /opt/postgres/9.2/backup