Backing Up RMS
Backing Up RMS
This section describes the backup procedure for the RMS provisioning solution. Two types of backups are
defined:
• System Backup, page 1
• Application Data Backup, page 4
System Backup
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.
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
1
Backing Up RMS
Full System Backup
Full System Backup
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:
Procedure
Step 1
Step 2
Login as 'root' user to the RMS node through the Vsphere Client console.
Run the command: #service network stop.
Cisco RAN Management System Installation Guide, Release 5.1
2
July 6, 2015
Backing Up RMS
Full System Backup
Using VM Snapshot
Procedure
Step 1
Step 2
Step 3
Step 4
Log in to vCenter using vSphere client.
Right-click on the VM and click Take Snapshot from the Snapshot menu.
Specify the name and description of the snapshot and click OK.
Verify that the snapshot taken is displayed in the Snapshot Manager. To do this, right-click on the VM and
select Snapshot Manager from Snapshot menu.
Back Up System Using vApp Cloning
Follow the below procedure to clone the Upload node with partitions and skip the steps 5 to 19 to clone the
Central and Serving nodes with or without partition.
Procedure
Step 1
Step 2
Log in to vCenter using the vSphere web client.
Select the vApp of the VM to be cloned, right-click and in the Getting Started tab, click Power off vApp.
Step 3
After the power-off, right-click on the VM and click Edit Settings.
If there are no additional hard disks configured, skip the steps 4 to 17.
Step 4
Click on the additionally-configured hard disk (other than the default hard disk – Hard Disk 1) from the
drop-down list. For example, Hard Disk 2. Repeat the steps for all the additionally configured hard disks.
Exmaple, Hard Disk 3, Hard Disk 4, and so on.
Make a note of the Disk File from the drop-down list.
Close the drop-down and remove (click on the "X" symbol against each additionally added hard disk) the
additional hard disks. Example, Hard Disk 2. Repeat the steps 5 and 6 on all the additionally-configured hard
disks. For example, Hard Disk 3, Hard Disk 4 and so on. Click Ok. Note:
Note
Do not check the checkbox because that would delete the files from the datastore, which cannot be
recovered.
Right-click on the vApp and select All vCenter Actions and click Clone. The New vApp Wizard is displayed.
In the Select a creation type screen, select Clone an existing vApp and click Next.
In Select a destination screen, select a host which has to be cloned and click Next.
In Select a name and location screen, provide a name and target folder/datacenter for the clone and click Next.
In Select storage screen, select the virtual disk format from the drop-down, which has the same format as the
source and the destination datastore and click Next.
Click Next in Map Networks, vApp properties, and Resource allocation screens.
In the Ready to complete screen, click Finish.
The status of the clone is shown in the Recent Tasks section of the window.
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
Step 12
Step 13
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
3
Backing Up RMS
Application Data Backup
Step 14 After the task is completed, to remount the additional hard disks in step r above, right-click on the cloned VM
and select Edit Settings.
Step 15 Select the new device as Existing Hard Disk and click Add.
Step 16 In the Select File screen, select the disk file as noted before the clone in Step 5 and click Ok. Repeat this step
for each additional hard disk seen in Step 4.
Step 17 Repeat the Steps 14 to 16 on the original VM.
Step 18 Select the vApp (either cloned or original) to be used and in the Getting Started tab, click Power on vApp.
Note
Make sure Serving node and Upload node is powered on only after the Central node is completely
up and running.
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 take backup of the RDU DB, postgres DB, and configuration files are 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 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 Rmsuser@1.
Cisco RAN Management System Installation Guide, Release 5.1
4
July 6, 2015
Backing Up RMS
Backup on the Central Node
Enter:
cd /rms/ova/scripts/redundancy;
./backup_central_vm.sh
Output:
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
5
Backing Up RMS
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: Rmsuser@1
Doing backup of Central VM configuration files.
tar: Removing leading `/' from member names
-rw-------. 1 root root 181089 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-------. 1 root root 4305935 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-20150320-051308
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: 5364383744 bytes.
Copying log.0000321861.
log.0000321861: 100% completed.
Copied log.0000321861. Size: 10485760 bytes.
Copying history.log.
history.log: 100% completed.
Copied history.log. Size: 23590559 bytes.
Database backup completed
Database recovery started
Recovering in:
/rms/backups/CentralNodeBackup_March20/rdu-db/rdu-backup-20150320-051308
This process may take a few minutes.
Database recovery completed
rdu-db/
rdu-db/rdu-backup-20150320-051308/
rdu-db/rdu-backup-20150320-051308/DB_VERSION
rdu-db/rdu-backup-20150320-051308/log.0000321861
rdu-db/rdu-backup-20150320-051308/history.log
rdu-db/rdu-backup-20150320-051308/rdu.db
-rw-------. 1 root root 664582721 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 649192608 Mar 20 05:16
/rms/backups/CentralNodeBackup_March20.tar.gz
backup done.
[blrrms-central50-ucs240-ha] /rms/ova/scripts/redundancy #
Cisco RAN Management System Installation Guide, Release 5.1
6
July 6, 2015
Backing Up RMS
Backup on the Serving Node
3 Check for the backup file created in /rms/backups/ directory.
ls -l /rms/backups
Enter:
Output:
[blrrms-central50-ucs240-ha] /rms/ova/scripts/redundancy # ls -l
/rms/backups
total 634604
-rwxrwxrwx. 1 root root 649192608 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:
Enter:
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
Output:
[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:
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
7
Backing Up RMS
Backup on the Upload Node
Enter:
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
Output:
[root@rtpfga-ova-serving06 ~]# cd /root
[root@rtpfga-ova-serving06 ~]# mkdir -p /rms/backup
[root@rtpfga-ova-serving06 ~]# 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
[root@rtpfga-ova-serving06 ~]# gzip /rms/backup/serving-config.tar
[root@rtpfga-ova-serving06 ~]# ls /rms/backup/serving-config.tar.gz
/rms/backup/serving-config.tar.gz
[root@rtpfga-ova-serving06 ~]#
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:
Enter:
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
Output:
[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:
Cisco RAN Management System Installation Guide, Release 5.1
8
July 6, 2015
Backing Up RMS
Backup on the Upload Node
Enter:
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
Output:
[root@rtpfga-ova-upload06 ~]# cd /root
[root@rtpfga-ova-upload06 ~]# mkdir -p /rms/backup
[root@rtpfga-ova-upload06 ~]# tar cf
/rms/backup/upload-node-apfiles.tar /opt/CSCOuls/files
tar: Removing leading `/' from member names
[root@rtpfga-ova-upload06 ~]# gzip /rms/backup/upload-node-apfiles.tar
[root@rtpfga-ova-upload06 ~]# ls /rms/backup/upload-node-apfiles.tar.gz
/rms/backup/upload-node-apfiles.tar.gz
Cisco RAN Management System Installation Guide, Release 5.1
July 6, 2015
9
Backing Up RMS
Backup on the Upload Node
Cisco RAN Management System Installation Guide, Release 5.1
10
July 6, 2015
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising