must maintain the number of back up snapshots on the management node. The
backup of the management node is possible only after complete deployment of at
least one Cisco VIM. Two copies of backup directories are maintained at the
management node itself and the older copy will be overwritten when a next
backup is performed.
During the backup
operation, activities such as pod management, software update or upgrade, and
addition or deletion or replacement of nodes cannot be performed.
The REST API and
ELK services are stopped during the backup operation, the OpenStack logs are
cached on the control, compute, and storage nodes till the restoration of the
management node is completed.
As part of the
backup operation, two files are created: .backup_files and .backup_hash.
.backup_files is a list of files that are backed up, while the second one is
the hash. These two files are placed under the backup directory
/var/cisco/backup_<tag>_<date-time> at the management node and also
at the /var/cisco/ directory of all three controllers. These two files are used
during the restore validation. When user attempt to restore from a particular
backup, these two files within this backup are compared to those at the
controllers. If there is any discrepancy, the restore validation will fail and
user will be prompted to either terminate the restore operation or continue
despite the validation failure. Only one copy of the .backup_files and
.backup_hash are kept at the controllers, that is every time a new backup is
created, these two files are overwritten with the most recent ones. Hence the
restore validation will only pass when the latest backup is used for restore.
Figure 1. Cisco NFVI
Management Node Backup Operation
Before You Begin
management node information (for example, IP address of the management node)
for use during the restore operation.
Ensure that you
have the br_mgmt and br_api IP addresses and respective network information.
||Launch a SSH
session to the Cisco NFVI management node.
||Navigate to the
What to Do Next
The backup operation
takes approximately 30 minutes and creates the
backup_<tag>_<date-time> directory in the /var/cisco/ path.
Copy the directory
to a remote server to recover the management node using rsync.
For example, to copy
the backup directory to the remote server 18.104.22.168 /var/cisco/directory ,
execute the following command sequence:
rsync -e ssh -rtvpX --numeric-ids /var/cisco/backup_2017-01-09_14-04-38 firstname.lastname@example.org:/var/cisco/
On the remote
server, protect the backup directory for any unauthorized access as the backup
files may contain sensitive information
At the remote
server, change directory to where the backup directory is copied to; in this
To verify if the
backup is not corrupted or modified, execute
depends on the following packages, they should be installed on the server where
check_integrity is executed.