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
•
If the rgmanager is set to ON in chkconfig, set it to OFF before rebooting the system. This prevents the
auto-starting of the rgmanager after a system reboot.
• Reboot both nodes (due to the existing /dev/vg_osimage file that prevents the creation of a new
vg_osimage).
• Set rgmanager chkconfig ON/OFF to the previous state if it changed when the nodes came back
up.
3. Recreate the Images repository volume group and logical volume. Use the correct /dev/mapper/
to create
the volume group on one node.
pvcreate /dev/mapper/isc_glance
vgcreate vg_osimage /dev/mapper/isc_glance
vgchange –-addtag <heartbeat host name> -a y vg_osimage
lvcreate –LxxxG –n lv_osimage vg_osimage
4. Restore the contents of the Images repository disk from its backed up copy, using the storage management
tool of your choice. For example, to test this whitepaper, the 3PAR storage management tool “Promote the
virtual copy” feature was used to restore the contents from a backed up virtual copy.
5. On the same node perform the following:
vgchange –-deltag <heartbeat host name> -a n vg_osimage
6. Restart the cman and rgmanager services on both nodes.
service cman start
service rgmanager start
7. Follow “Completing the recovery process” and “Validation” to complete the recovery.
Once the above restore steps are completed, it is important to follow the steps outlined in “Validating the HA
configuration” to validate the proper functioning of the cluster.
Cluster restore
Cluster failures can be handled by following multiple primitive cases. However, the case can be simplified due to the
fact that both nodes are restored offline. In this scenario, it is assumed that the cluster nodes and the associated three
disks have failed and need to be replaced.
Recovery steps
1. Create three new external shared disks: Quorum disk, KVM Private Cloud appliance physical disk and the
Images repository disk.
2. Reinstall the KVM Host OS, using the 6.3 RedHat version following the “RedHat Enterprise Linux 6 –
Installation Guide”. Then install the add-ons as shown in the table below.
19