The documents describes the procedure to recover the Virtual Cisco Policy and Charging Rules Function (vPCRF) instances deployed on an Ultra-M/OpenStack environment.
Cisco recommends that you have knowledge of these topics:
Cisco Policy Suite (CPS)
Compute on which affected instances were deployed is now available
Compute resources are available in the same availability zone as the affected instance
This document is not restricted to specific software and hardware versions.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Step 1. Elastic Services Controller (ESC)
Configurations in ESC-HA must be backed up monthly, before/after any scale-up or scale-down operation with the VNF and before/after configuration changes at ESC. It must be backed up in order to do a disaster recovery of ESC effectively.
ESC opdata as an XML
Follow this in order to export the ESC opdata as an XML:
1. Login to ESC with the use of admin credentials.
If the deployment ESC opdata (extracted in the previous step) contains any of the highlighted files, back them up with the help of this command.
tar –zcf esc_files_backup.tgz /opt/cisco/esc/cisco-cps/config/
Download this file to your local computer of ftp/sftp to a server outside the cloud.
Note: Although opdata is synced between ESC primary and standby, directories that contain user-data, XML and post-deploy scripts are not synced across both instances. It is suggested that customers push the contents of the directory that contain these files with the use of SCP or SFTP, these files should be constant across ESC-Primary and ESC-Standby in order to recover a deployment when ESC VM which was primary at the time of deployment is not available.
Suggested Backups Schedule in ESC
These are suggested crontab entries for the root user to be added in ESC Primary and ESC Standby. You can, however, modify the hours/day/month as per their requirements and frequency of changes in the network.
Cluster Manager acts as a puppet primary for one CPS cluster. Thus, it becomes necessary to take a snapshot of this instance. Also, Cisco provided backup and restore utility can be used to gather backups of mongoDB, policy configuration, grafana DB, users, networks and other pcrf configuration files. These files should be frequently backed up with the use of CPS backup utility and stored in a location outside Ultra-M cloud.
Snapshot of Cluster Manager VM
Cluster Manager Instance Snapshot must be backed up monthly, also before and after any configuration changes, patch updates and upgrades. Old snapshots can be deleted after successful activities to save disk space. This procedure describes the steps to backup the cluster manager instance as a snapshot:
1. This command to view the nova instances and note the name of the cluster manager VM instance:
2. Create a nova snapshot image as shown here:
nova image-create --poll <cluman_instance_name> <cluman_snapshot_name>
Server snapshotting... 100% complete
Note: Ensure that you have enough disk space for the snapshot. Cluster Manager sometimes becomes unreachable at the time of snapshot creation and resumes itself after the snapshot has been created. If the instance remains unreachable even after snapshot process has finished, check the status of VM with the use of the nova list command. If it is in SHUTOFF state, you need to start the VM manually, with the use of nova start command.
3. Ensure the snapshot image is created with this command.
4. When you perform any platform changes where Ceph might get impacted, it is always suggested to convert the snapshot of Cluster Manager to a QCOW file and save it to some remote location.
glance image-download --file /var/Pcrf/cluman_snapshot.raw <image-id of the snapshot>
5. Download this file to your local computer of ftp/sftp to a server outside the cloud.
Backup of CPS Configurations and Database
1. For backing up CPS configurations and database contents, config_br.py utility is inbuilt in the CPS platform. Details about the use of the config_br.py utility are present in CPS Backup and Restore Guide. This is a sample crontab in cluster manager to backup all configuration and databases at 0100 hrs every day.