CliQr is now part of Cisco Learn More About Cisco

Backup and Recovery in Non-HA Mode

Recommendations

To effectively manage your CloudCenter deployment, backup your deployment on a daily basis – you can setup a cronjob to automatically perform this backup.

Icon

If you are upgrading the CloudCenter deployment, be aware that the process may differ. See the Upgrade in Non-HA Mode or Upgrade in HA Mode for additional context.

Icon

Use this procedure to backup and recover data for the following releases on a per-component basis:

  • CloudCenter 4.6.x
  • CloudCenter 4.7.x

The backup and recover procedure is performed on a per component basis and the procedure for backup is the same for all components. Instead of repeating this procedure for each role, the procedure identifies the applicable roles for each component in the HA and standalone modes. For the HA mode, see Backup and Recovery in HA Mode.

CCM

Use this procedure for the CCM, CCM_SA, and MGMTPOSTGRES roles (see Component Modes and Roles for additional context).

Backup CCM Data

Backup the webapp folder containing the exploded war files to a backup folder (the following example uses /mnt, you can change this directory as applicable).

This backup only applies to the CCM and CCM_SA servers.

Backup the CCM Database

This procedure applies to the CCM server or the MGMTPOSTGRES server.

  1. SSH into the CCM or MGMTPOSTGRES server.

  2. Back up the existing CCM database: 
    1. mkdir /root/backup_date
    2. cd backup_date
    3. pg_dump -U cliqr  -d cliqrdb   > pg_dump.sql

      Icon

      Enter the PostgreSQL username and password at the prompt.

      • Username = cliqr
      • Password = cliqr

Restore the CCM Database

  1. SSH into the CCM server.

  2. Recover the CCM database: 

    psql -U cliqr -d  cliqrdb < pg_dump.sql

    Icon

    Enter the PostgreSQL username and password at the prompt.

    • Username = cliqr
    • Password = cliqr

    If the cliqrdb and the cliqr user does not exist, run the following commands after logging into PostgreSQL as the root user.

    1. createdb -U postgres -E UNICODE cliqrdb 
      (enter the PostgreSQL user password at the prompt)

    2. psql -U postgres -d cliqrdb  
      (enter the PostgreSQL user password at the prompt)

CCO

Use this procedure for the CCO role (see Component Modes and Roles for additional context).

Backup CCO Database

  1. SSH into the CCO server.
  2. Back up the existing CCO database:  
    1. mkdir /root/backup_date
    2. cd backup_date
    3. mongodump

Restore the CCO Database

  1. SSH into the CCO server.
  2. Recover the CCO database from the current directory: 
    mongorestore
  3. Restart the Tomcat service after restoring.
    /etc/init.d/tomcat restart 

AMQP

The back up scenario is not applicable in the non-HA mode as there is no known data that can be persisted.

To restore, simply launch a new VM and reconfigure the VM.

Health Monitor

The back up scenario is not applicable in the non-HA mode as there is no known data that can be persisted.

To restore, simply launch a new VM and reconfigure the VM.

 

  • No labels