HP Matrix 7.2 KVM Private Cloud Backup and Restore

Completing the recovery process
Once the Matrix KVM Private Cloud appliance is re-started, the appliance will synchronize with the restored Images
repository contents. Since the Matrix KVM Private Cloud appliance and the Images repository can be backed up and
restored independently, there could be inconsistency between the metadata stored in the KVM Private Cloud
database for the images stored in the Images repository. Possible inconsistent scenarios that may arise and the
corresponding manual recovery actions are listed below:
1. The metadata in the KVM Private Cloud points to an image that no longer exists in the restored Images
repository. The image could be in any of the following states at the time of the restore: active, saving.
• Notification: A missing image alert will be generated in the Matrix KVM Admin Console, stating that
the image has been marked deleted.
• Manual recovery action: You should re-add the image by uploading the image through the Matrix
KVM Admin Console for future provisioning.
2. The image was in a transitory state (creating, saving, queued) at the time of restore and there is a
corresponding image found in the restored Images repository.
• Notification: An audit message will be generated in the Matrix KVM Admin Console audit logs, stating
that the image has been moved to a killed state after a configured stale period.
• Manual recovery action: You should manually delete the image and upload the image again for future
provisioning.
3. An image exists in the Images repository but the metadata is an older version that was restored. There is no
reference to this image in the metadata, leading to orphaned images in the restored Images repository.
• Notification: An orphaned image alert will be generated in the Matrix KVM Admin Console with the
UUID of the orphaned image.
• Manual recovery action: You should manually delete the image in the Images repository and re-upload
the image for future provisioning.
4. The size of the image stored in the Matrix KVM Private Cloud metadata is different from that of the image
stored in the restored Images repository.
• Notification: An inconsistent image alert will be generated in the Matrix KVM Admin Console,
indicating that the image has been moved to a killed state with the image details.
• Manual recovery action: You should manually delete the image in the Images repository and upload
the image again for future provisioning.
5. In the Matrix KVM Private Cloud, an image can be added in various formats. The user should not change
the format after adding an image to the appliance. Any image formats that are inconsistent between the
metadata and the Images repository will not be detected after a restore of the Images repository.
More details on the errors that can occur during various image states can be found in Appendix B, “Images
repository restore resynchronization actions”.
Validation
It is recommended that you validate the restored images and general health of the KVM Private Cloud before
provisioning new tasks. Suggested validation steps are as follows:
1. Verify that the restart of the KVM Private Cloud succeeded without errors.
2. Verify that the previously added images are in an active state.
3. Provision an instance using the restored images and verify that the operation is successful.
Matrix KVM Private Cloud High Availability (HA)
cluster configuration backup and restore
The KVM management cluster configuration is required to run Matrix KVM Private Cloud in a High Availability (HA)
configuration. If the KVM management cluster hosting the KVM Private Cloud becomes lost or corrupted, it may be
necessary to restore the cluster configuration from a previously backed up copy.
12