HP Matrix 7.2 KVM Private Cloud Backup and Restore

Table Of Contents
Note
The KVM Private Cloud data is backed up and restored
using the backup/restore procedures covered in the ‘Matrix KVM
Private Cloud backup and restore’ section above. The
Images repository data is backed up and restored using the
procedures described in the previous section.
Scope
The scope of this section is to only cover backup and restore procedures for the HA cluster configuration data.
Backup procedure for HA cluster configuration environment
The following table lists all of the configuration files that are required to restore an HA cluster environment for the
Matrix KVM Private Cloud. Use the file management tool of your choice to back up the following files from each
node in the cluster. The backups should be performed when both nodes are in the same cluster configuration version
and in full operational condition without errors.
Table 2: List of files to be backed up
Directory or file
Description
/etc/cluster/cluster.conf
/etc/lvm/lvm.conf
/etc/hosts
Files related to cluster/lvm configuration
/etc/sysconfig/network-scripts/ifcfg-bond*
/etc/sysconfig/network-scripts/ifcfg-eth*
/etc/sysconfig/network-scripts/ifcfg-br*
Files related to network bonding
/etc/multipath.conf
File related to redundant storage
/vm/config/<vm>.xml
File required for KVM Private Cloud failover
Note
If the firewall is configured, then the /etc/sysconfig/iptables should also be
backed up.
Refer to Appendix D, for a sample list of the files.
Restore procedures for HA cluster configuration environment
In a clustered environment there are multiple components like the KVM management host(s), the Quorum disk, the
KVM Private Cloud appliance disk and the Images repository disk. The following sections describe the recovery
procedure for each of the components in the KVM Private Cloud HA cluster.
Single KVM management host restore
In the KVM management cluster where the KVM Private Cloud runs, if the active node fails, the KVM Private Cloud
will failover to the stand-by node. Therefore, the recovery process for the failed node should not interfere with the
activities on the running node.
13