HP Matrix 7.2 KVM Private Cloud Backup and Restore

Matrix KVM Private Cloud Appliance Data restore
The second kind of appliance disk failure occurs when data in the Matrix KVM Private Cloud appliance disk becomes
corrupted. Restore procedures are involved only in recreating the Matrix KVM Private Cloud appliance. Use the
existing Matrix KVM Private Cloud appliance logical volume to perform restore procedures for the Matrix KVM
Private Cloud. All the HA components are intact and do not need to be updated.
Recovery Steps
1. Stop the rgmanager service on both cluster nodes.
service rgmanager stop
2. Activate the volume group vg_iscvm
on one of the cluster nodes. To find the heartbeat host name for the
vgchange command, check the “volume_list” attribute configuration in the /etc/lvm/lvm.conf file.
vgchange -–addtag <heartbeat-host-name> -a y vg_iscvm
3. Recreate the KVM Private Cloud appliance.
4. Deactivate the volume group vg_iscvm and remove the tag.
vgchange –-deltag <heartbeat-host-name> -a n vg_iscvm
5. Start the rgmanager service on both cluster nodes.
service rgmanager start
6. Verify that the KVM Private Cloud is running under the cluster service.
clustat
virsh list
7. Restore the KVM Private Cloud data using the procedure in “Matrix KVM Private Cloud backup and
restore”.
Once the above restore steps are complete, it is important to follow the steps outlined in “Validating the HA
configuration” to validate that the cluster is functioning properly.
Images repository disk restore
It is possible for the Images repository disk to become corrupted or damaged in the cluster. To recover the Images
repository disk, the disk needs to be rebuilt and the contents need to be restored from a backed up copy using the
storage management tool of your choice.
Recovery steps
From an HA configuration perspective, Images repository recovery is similar to Matrix KVM Private Cloud appliance
disk recovery.
1. Stop the rgmanager and cman services on both nodes.
service rgmanager stop
service cman stop
2. Recover the damaged storage.
• Unexport the damaged disk to both cluster nodes.
• Create a new external shared disk (1 TB) for the Images repository disk.
• Export the disk to both cluster nodes (use the same LUN# used by the previous disk).
• Update multipath configuration in /etc/multipath.conf (update the WWID for the new disk). Edit
the WWID as highlighted in the sample configuration below, for the alias “isc_glance” to match the
newly exported Images repository disk’s configuration in your setup.
18