HP Matrix 7.2 KVM Private Cloud Backup and Restore
Table Of Contents
- Abstract
- Matrix Operating Environment with Matrix KVM Private Cloud Overview
- Backup and restore strategy for Matrix OE with Matrix KVM Private Cloud
- Matrix KVM Private Cloud backup and restore
- Matrix KVM Private Cloud Images repository backup and restore
- Matrix KVM Private Cloud High Availability (HA) cluster configuration backup and restore
- Appendix A: KVM Private Cloud restore resynchronization actions
- Appendix B: Images repository restore resynchronization actions
- Appendix C: Alerts and Audit messages
- Appendix D: HA Cluster details
- Appendix E: Backup and Restore REST API
- Appendix F: Sample Backup Script
- Appendix G: Sample Restore Script
- References
- For more information
4. Update the multipath configuration in /etc/multipath.conf (update the WWID for the new disk). Edit
the WWID that is highlighted in the sample configuration below, for the alias “isc_quorum” to match the
newly exported Quorum disk’s configuration in your setup.
5.
Stop the rgmanager and the cluster service on both nodes using the following command:
service rgmanager stop
service cman stop
6. Restart the multipath service on both hosts.
service multipathd restart
7. Set the service to start automatically when the system reboots (both hosts).
chkconfig mutipathd on
8. Display the multipath topology (both hosts) to verify that the isc_root, isc_glance and isc_quorum
disks are displayed.
multipath –ll
9. Create a Quorum disk called “clqdisk” on one of the hosts in the cluster using the following command:
mkqdisk –c /dev/mapper/isc_quorum –l clqdisk
Enter “y” for the message.
Ignore the message: “WARNING: About to destroy all data on /dev/mapper/….”
10. Verify that the Quorum disk has been created successfully. The following command should display the detail
of the qdisk created from the previous step:
mkqdisk -L
11. Restart the cluster and associated services on both nodes.
service cman restart
service rgmanager restart
Once the restore steps are complete, it is important to follow the steps outlined in the section “Validating the HA
configuration” (page 18) to validate that the cluster functions properly.
Matrix KVM Private Cloud Appliance Physical disk restore
In this appliance disk failure scenario the physical KVM Private Cloud disk is damaged. Both the data and the disk
need to be restored in order for the KVM Private Cloud to function properly.
Unlike the Quorum disk, which is a raw disk, the KVM Private Cloud appliance resides in an HA LVM disk. For that
reason, a logical volume needs to be created before restoring the KVM Private Cloud.
Recovery Steps
1. Stop the rgmanager and cman services on both the nodes.
service rgmanager stop
service cman stop
16