HP Matrix 7.2 KVM Private Cloud Backup and Restore

2. Recover the damaged storage.
• Unexport the damaged disk to both cluster nodes.
• Create a new external shared disk (200GB) for the KVM Private Cloud.
• Export the disk to both cluster nodes (use the same LUN# used by the previous disk).
• Update the 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_root” to match the
newly exported KVM Private Cloud disk’s configuration in your setup.
• If the rgmanager is set to ON in chkconfig, set it to OFF before rebooting the system. This prevents the
rgmanager from auto-starting after the system reboot.
• Reboot both nodes (due to the existing /dev/vg_iscvm file that prevents a new vg_iscvm from being
created).
• Set rgmanager chkconfig ON/OFF to the previous state if it changed when the nodes came back
up.
3.
Recreate the Matrix KVM Private Cloud appliance volume group and logical volume on one node. To find
the heartbeat host name for the vgchange command, check the “volume_list” attribute configuration in the
/etc/lvm/lvm.conf file
.
pvcreate /dev/mapper/isc_root
vgcreate vg_iscvm /dev/mapper/isc_root
vgchange –-addtag <heartbeat host name> -a y vg_iscvm
lvcreate –L200G –n lv_iscvm vg_iscvm
4. Recreate the Matrix KVM Private Cloud appliance.
5. On the same node perform the following command:
vgchange -–deltag <heartbeat host name> -a n vg_iscvm
6. Start the cman and the rgmanager service on both cluster nodes using the following command:
service cman start
service rgmanager start
7. Verify that the KVM Private Cloud is running under the cluster service using the following command:
clustat
8. Restore the Matrix KVM Private Cloud data using the procedure documented in “Matrix KVM Private Cloud
backup and restore”.
Once the restore steps are completed, it is important to follow the steps outlined in the section “Validating the HA
configuration” to validate that the cluster functions properly.
17