Overview
Various items in a Cisco Policy Suite (CPS) cluster require periodic backups.
This document describes the procedure to use the config_br.py script to back up the configuration and the data from a CPS cluster, and the steps to restore the backups, in case of any failures.
For general information about the config_br.py script and all the options, see the About the Backup and Restore Script.
Before You Begin
Before you begin any backup and restore procedures, ensure you have performed the following tasks:
-
Install CPS and have it running successfully. Backups are stored on customer-provided hardware, preferably in a location apart from where CPS is currently running.
-
Initiate backups from the cluster manager VM. Ensure that there is adequate storage space on the cluster manager VM before taking a backup.
-
pcrfclient01/OAM01 VM is up and running for SVN repository backup.
-
lbvip01 VIP is available on Policy Director (LB) VMs.
Note |
Cisco recommends that the backup of the cluster manager be performed by taking a snapshot of the cluster manager VM. This operation requires administrator access to OpenStack or VMware (depending on the environment that CPS is deployed in). |
Backup Schedule
Your first backup operation should occur after a successful installation and configuration. This provides a baseline and tests your backup procedures with respect to hardware, software, and protocols.
Then, do backup on this schedule as a best practice.
Backup this... |
...this often |
---|---|
Cluster Manager VM |
Monthly and after any configuration changes, patch updates, or upgrades |
Databases |
Daily |
Policy Builder Configurations |
Weekly or after any changes |