This section describes the backup procedure for the RMS provisioning solution. Two types of backups are defined:

Transcription

1 This section describes the backup procedure for the RMS provisioning solution. Two types of backups are defined: Full, on page 2 Application Data Backup, on page 4 A full system backup of the VM is recommended before installing a new version of Cisco RMS so that if there is a failure while deploying the new version of Cisco RMS, the older version can be recovered. Full system backups can be performed using the VMware snapshot features. Sufficient storage space must exist in the local data store for each server to perform a full system backup. For more information on storage space, Virtualization Requirements. Full system backups should be deleted or transported to external storage for long-duration retention. Application data backups can be performed using a set of tar and gzip commands. This document will identify the important data directories and database backup commands. Sufficient storage space must exist within each virtual machine to perform an application data backup. For more information on storage space, see Virtualization Requirements. Performing application data backup directly to external storage requires an external volume to be mounted within each local VM; this configuration is beyond the scope of this document. Both types of backups can support Online mode and Offline mode operations: Online mode backups are taken without affecting application services and are recommended for hot system backups. Offline mode backups are recommended when performing major system updates. Application services or network interfaces must be disabled before performing Offline mode backups. Full system restore must always be performed in Offline mode. Full, page 2 Application Data Backup, page 4 May 25, 2015 HF 1

2 Full Full Full system backups can be performed using the VMware vsphere client and managed by the VMware vcenter server. With VMware, there are two options to have full system backup: VM Snapshot VM snapshot preserves the state and data of a virtual machine at a specific point in time. It is not a full backup of VMs. It creates a disk file and keeps the current state data. If the full system is corrupted, it is not possible to restore. Snapshots can be taken while VM is running. Requires lesser disk space for storage than VM cloning. vapp/vm Cloning It copies the whole vapp/vm. While cloning, vapp needs to be powered off Note It is recommended to clone vapp instead of individual VMs. Requires more disk space for storage than VM snapshots. Back Up System Using VM Snapshot Note If offline mode backup is required, disable network interfaces for each virtual machine. Create Snapshot using the VMware vsphere client. Following are the steps to disable the network interfaces: Step 1 Step 2 Login as 'root' user to the RMS node through the Vsphere Client console. Run the command: #service network stop. 2 May 25, 2015 HF

3 Back Up System Using vapp Cloning Following are the steps to enable the network interfaces: Step 1 Step 2 Login as 'root' user to the RMS node through the Vsphere Client console. Run the command: #service network start. Back Up System Using vapp Cloning Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Log in to vcenter using the vsphere client. Select the VM or vapp to be cloned and in the Getting Started tab, click Power off vapp. After the power-off, right-click on vapp and select Clone. The Clone vapp Wizard is displayed. In the Host/Cluster/Resource screen, select the host where the cloned vapp is placed and click Next. Cloning of Vapp on a different host might take more time than cloning on the same host where the vapp is currently present. In the Name and Folder screen, enter the vapp name and select the vapp inventory location of the cloned vapp and click Next. In the DataStore screen, select the datastore where the files of the vapp are stored and click Next. In the Disk Format screen, select the Same format as source option and click Next. In the Network Mapping screen, select the vapp network and click Next. In the vapp Properties screen, for the properties where prompted with the message "A value must be provided", enter the following values and retain the remaining properties: Property Name Default Value Snmp_Read_Community snmp-read Snmp_Write_Community snmp-write SnmpTrap_Community snmp-trap Asr5k_Radius_Secret secret RMS_App_Password=Ch@ngeme1 Root_Password=Ch@ngeme1 Admin1_Password=Ch@ngeme1 Click Next. Step 10 Step 11 Step 12 In the Ready to Finish screen, click Finish. Return to the main screen of the vcenter, select the vapp to verify that the status of cloning is completed. The status is shown in Recent Tasks section of the window. Select the original vapp and in the Getting Started tab, click Power on vapp. May 25, 2015 HF 3

4 Application Data Backup Application Data Backup Application data backups are performed from the guest OS themselves. These backups will create compressed tar files containing required configuration files, database backups and other required files. The backups and restores are performed using root user. Excluding Upload AP diagnostic files, a typical total size of all application configuration files would be 2-3 MB. Upload AP diagnostic files backup size would vary depending on the size of AP diagnostic files. The rdu/postgres db backup files would depend on the data and devices. A snapshot of backup files with 20 devices running has a total size of around 100 MB. Perform the following procedure for each node to create an application data backup. Note Copy all the backups created to the local PC or some other repository to store them. Backup on the Central Node Follow the below procedure to back up the RDU DB, Postgres DB, and configuration files on the Central node: 1 Log in to the Central node and switch to 'root' user. 2 Execute the backup script to create the backup file. This script prompts for the following inputs: new backup directory: Provide a directory name with date included in the name to ensure that it is easy to identify the backup later when needed to restore. For example, CentralNodeBackup_March20. PostgresDB password: Provide the password as defined in the descriptor file for RMS_App_Password property during RMS installation. If RMS_App_Password property is not defined in the descriptor file, use the default password Ch@ngeme1. 4 May 25, 2015 HF

5 Backup on the Central Node cd /rms/ova/scripts/redundancy;./backup_central_vm.sh May 25, 2015 HF 5

6 Backup on the Central Node [blrrms-central50-ucs240-ha] /rms/ova/scripts/redundancy #./backup_central_vm.sh Existing backup directories: Enter name of new backup directory: CentralNodeBackup_March20 Enter password for postgresdb: Doing backup of Central VM configuration files. tar: Removing leading `/' from member names -rw root root Mar 20 05:13 /rms/backups/centralnodebackup_march20//central-config.tar.gz Completed backup of Central VM configuration files. Doing backup of Central VM Postgress DB. -rw root root Mar 20 05:13 /rms/backups/centralnodebackup_march20//postgres_db_bkup Completed backup of Central VM Postgress DB. Doing backup of Central VM RDU Berklay DB. Database backup started Back up to: /rms/backups/centralnodebackup_march20/rdu-db/rdu-backup Copying DB_VERSION. DB_VERSION: 100% completed. Copied DB_VERSION. Size: 394 bytes. Copying rdu.db. rdu.db: 1% completed. rdu.db: 2% completed.... rdu.db: 100% completed. Copied rdu.db. Size: bytes. Copying log log : 100% completed. Copied log Size: bytes. Copying history.log. history.log: 100% completed. Copied history.log. Size: bytes. Database backup completed Database recovery started Recovering in: /rms/backups/centralnodebackup_march20/rdu-db/rdu-backup This process may take a few minutes. Database recovery completed rdu-db/ rdu-db/rdu-backup / rdu-db/rdu-backup /db_version rdu-db/rdu-backup /log rdu-db/rdu-backup /history.log rdu-db/rdu-backup /rdu.db -rw root root Mar 20 05:14 /rms/backups/centralnodebackup_march20//rdu-db.tar.gz Completed backup of Central VM RDU Berklay DB. CentralNodeBackup_March20/ CentralNodeBackup_March20/rdu-db.tar.gz CentralNodeBackup_March20/postgres_db_bkup CentralNodeBackup_March20/.rdufiles_backup CentralNodeBackup_March20/central-config.tar.gz -rwxrwxrwx. 1 root root Mar 20 05:16 /rms/backups/centralnodebackup_march20.tar.gz backup done. [blrrms-central50-ucs240-ha] /rms/ova/scripts/redundancy # 6 May 25, 2015 HF

7 Backup on the Serving Node 3 Check for the backup file created in /rms/backups/ directory. ls -l /rms/backups [blrrms-central50-ucs240-ha] /rms/ova/scripts/redundancy # ls -l /rms/backups total rwxrwxrwx. 1 root root Mar 20 05:16 CentralNodeBackup_March20.tar.gz [blrrms-central50-ucs240-ha] /rms/ova/scripts/redundancy # Backup on the Serving Node Perform the following commands to create a backup of RMS component data on the Serving node. 1 Back up Femtocell Firmware Files: cd /root mkdir -p /rms/backup tar cf /rms/backup/serving-firmware.tar /rms/data/cscobac/dpe/files gzip /rms/backup/serving-firmware.tar ls /rms/backup/serving-firmware.tar.gz [root@rtpfga-ova-serving06 ~]# cd /root [root@rtpfga-ova-serving06 ~]# mkdir -p /rms/backup [root@rtpfga-ova-serving06 ~]# tar cf /rms/backup/serving-firmware.tar /rms/data/cscobac/dpe/files tar: Removing leading `/' from member names [root@rtpfga-ova-serving06 ~]# gzip /rms/backup/serving-firmware.tar [root@rtpfga-ova-serving06 ~]# ls /rms/backup/serving-firmware.tar.gz /rms/backup/serving-firmware.tar.gz [root@rtpfga-ova-serving06 ~]# 2 Back up Configuration Files: May 25, 2015 HF 7

8 Backup on the Upload Node cd /root mkdir -p /rms/backup tar cf /rms/backup/serving-config.tar /rms/app/cscoar/conf /rms/app/nwreg2/local/conf /rms/app/cscobac/dpe/conf /rms/app/cscobac/car_ep/conf /rms/app/cscobac/cnr_ep/conf /rms/app/cscobac/snmp/conf/ /rms/app/cscobac/agent/conf /rms/app/cscobac/jre/lib/security/cacerts gzip /rms/backup/serving-config.tar ls /rms/backup/serving-config.tar.gz ~]# cd /root ~]# mkdir -p /rms/backup ~]# tar cf /rms/backup/serving-config.tar /rms/app/cscoar/conf /rms/app/nwreg2/local/conf /rms/app/cscobac/dpe/conf /rms/app/cscobac/car_ep/conf /rms/app/cscobac/cnr_ep/conf /rms/app/cscobac/snmp/conf/ /rms/app/cscobac/agent/conf /rms/app/cscobac/jre/lib/security/cacerts tar: Removing leading `/' from member names ~]# gzip /rms/backup/serving-config.tar ~]# ls /rms/backup/serving-config.tar.gz /rms/backup/serving-config.tar.gz ~]# Backup on the Upload Node Perform the following commands to create a backup of RMS component data on the Upload node. 1 Back up Configuration Files: cd /root mkdir -p /rms/backup tar cf /rms/backup/upload-config.tar /opt/cscouls/conf gzip /rms/backup/upload-config.tar ls /rms/backup/upload-config.tar.gz [root@rtpfga-ova-upload06 ~]# cd /root [root@rtpfga-ova-upload06 ~]# mkdir -p /rms/backup [root@rtpfga-ova-upload06 ~]# tar cf /rms/backup/upload-config.tar /opt/cscouls/conf tar: Removing leading `/' from member names [root@rtpfga-ova-upload06 ~]# gzip /rms/backup/upload-config.tar [root@rtpfga-ova-upload06 ~]# ls /rms/backup/upload-config.tar.gz /rms/backup/upload-config.tar.gz 2 Back up AP Files: 8 May 25, 2015 HF

9 Backup on the Upload Node cd /root mkdir -p /rms/backup tar cf /rms/backup/upload-node-apfiles.tar /opt/cscouls/files gzip /rms/backup/upload-node-apfiles.tar ls /rms/backup/upload-node-apfiles.tar.gz ~]# cd /root ~]# mkdir -p /rms/backup ~]# tar cf /rms/backup/upload-node-apfiles.tar /opt/cscouls/files tar: Removing leading `/' from member names ~]# gzip /rms/backup/upload-node-apfiles.tar ~]# ls /rms/backup/upload-node-apfiles.tar.gz /rms/backup/upload-node-apfiles.tar.gz May 25, 2015 HF 9

10 Backup on the Upload Node 10 May 25, 2015 HF