HP Matrix 7.2 KVM Private Cloud Backup and Restore

Appendix A: KVM Private Cloud restore
resynchronization actions
This section contains supplemental information that explains state changes after an appliance restore. The tables
below indicate alerts and state changes that occur after a restore for various instances and images.
Table 2: Summary of instance states post appliance restore
Instance details
Instance exists on the
host
Is host active and
connected?
Instance state after restore
Orphaned Instance
Yes
Yes
No change
In-Progress Instance
(Incomplete task for an
instance)
Yes
Yes
Active if instance is running, Shutoff if
instance is shutdown
Unknown
No
Instance moved to error state
Missing Instance
No
Yes
Instance is marked deleted
Disconnected Instance
Unknown
No
No change
Table 3: Summary of image states post appliance 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.
Killed
Saving
No
An alert is generated
notifying of missing image.
Deleted
Yes
An inconsistent image 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
No change
Yes
An orphaned image alert is
generated with the image
details.
No change
No metadata entry
Yes
An alert is generated with the
orphan image details.
No metadata entry
24