HP Matrix 7.2 KVM Private Cloud Backup and Restore

Appendix B: Images repository restore
resynchronization actions
This section contains supplemental information for restoring the images after an Images repository restore. Since the
Images repository and the KVM Private Cloud containing the images metadata can be independently restored from
backups taken at different timestamps, it is possible that inconsistencies could exist between the state indicated by the
metadata entry and the actual image stored in the Images repository. The table below explains the various alerts that
can be produced after a restore of the Images repository and the final image state after the restore.
Table 4. Summary of image states after image repository restore
Image state before restore
Image exists in the restored
repository
Alert
Image state after restore
Creating
No
An alert is generated
notifying of missing image.
Deleted
Yes (could happen when an
older appliance is restored)
An audit message will be
generated after a stale
period.
Killed (after the stale period
expires)
Image is not deleted from the
Images repository.
Saving
No
An alert is generated
notifying of missing image.
Deleted
Yes
An alert will be generated if
the size is mismatched
between the metadata and
the image repository.
Killed
Active
No
An alert is generated
notifying of missing image.
Deleted
Yes
a) An alert will be generated
if the size is mismatched
between the metadata and
the image repository.
b) No alert/audit generated
if there is no inconsistency.
a) Killed
b) Active (No change)
Killed
No
An alert is generated
notifying of missing image.
Deleted
Yes
No change
Killed (No change)
Deleted
No
No alert
Deleted (No change)
Yes
An alert is generated with the
orphan image details.
Deleted (No change)
No metadata entry
Yes
An alert is generated with the
orphan image details.
No metadata entry
25