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
 

•  Before starting a restore, you may want to download the existing audit logs. Restore will replace the audit logs 
with those in the backup.  
•  Before starting a restore, make sure you know the appliance user names and passwords in effect at the time of 
the backup. Restore resets the user names and passwords to the ones configured when the backup was taken.  
•  If you are restoring to a different appliance from the one where the backup was taken, you must take extra 
precautions before starting the restore. Decommission the original appliance or reconfigure it to no longer 
manage the devices it was managing when the backup was performed. Serious errors can occur if multiple 
appliances attempt to manage the same devices.  
•  Before starting a restore, all users logged into the Matrix KVM Admin Console must log out. Otherwise, users will 
lose their work. Users are automatically logged out as soon as a restore starts. Users will be blocked from 
logging in during a restore.  
•  If the appliance being restored is running a version of the firmware that is incompatible with the backup, then 
install a compatible version of the firmware on the appliance before uploading the backup. The platform type, 
hardware model, major number, and minor number must match to restore a backup. The revision and build 
numbers do not need to match. The format of the appliance firmware version is <major number>.<minor 
number>.<revision number>-<build number>. If the backup is incompatible with the firmware on the 
appliance, then upload returns an error. If this happens, update the firmware or select a different backup.  
•  Make the backup accessible on the system where you plan to issue the upload request. If you are using an 
enterprise backup/restore product to archive backup files, take any steps required by your backup/restore 
product to prepare for the restore. 
•  For tracking purposes, it is recommended that you collect detailed information of any configuration changes that 
were performed after taking the backup. In particular, changes to cloud networking configuration, additions, 
modifications and removal of public IP’s to instances need to be collected. If the appliance has not failed 
catastrophically, much of this data can be collected from the cloud networking configuration settings, IP 
addresses, Instances and Activity Pages from the KVM Admin Console. This data will be useful for performing 
any required manual recovery actions post restore. 
Post Restore  
At the time of restore, non-existing instances on hosts that are activated and connected are  deleted and a 
corresponding audit message is generated. Instances where  no entry exists in the inventory, for example,   the 
instances that are created after backup, are reported and corresponding alerts/audit messages are provided. 
Instances that were in progress at the time of backup are updated to an active or shut-off state if their current power 
state is active or shutdown. Alerts are provided for instances for all the disconnected hosts.  
Alerts are generated for images without metadata,  for example, the images that were added after a  backup. In-
progress images are moved to a killed state (Refer to Appendix A) and corresponding audit messages are provided. 
Missing images and images that are in an inconsistent state are reported as alerts. Refer to Appendix C for more 
details on the various alerts and audit messages that are generated on restore. 
Post restore, complete the following steps along with the necessary manual recovery actions for the appliance to be 
fully operational: 
Step 1: Enable hosts to regain connectivity to the  appliance  by executing  the  commands  below  on all activated 
hosts. 
service network restart 
service openstack-nova-compute restart 
service openstack-nova-network restart 
Step 2: Delete any old certificates associated to the appliance from Matrix OE as below: 
In  Systems Insight Manager,  select  Options->Security->Credentials->Trusted Systems. Under  the    Trusted 
Certificates tab select the certificate and click the Delete button. 
Step 3: Set up an SSL certificate trust relationship between Matrix OE and the restored appliance. Refer to “Set up 
an SSL certificate trust relationship between Matrix OE and the restored  Matrix KVM Admin Console appliance” 
section of “HP Matrix 7.2 KVM Private Cloud Getting Started Guide”. 
8 










