HP Storage Mirroring Software - Manual (Page 604)

Snapshots Page 603 of 677
l
Automatic action taken for scheduled and automatic snapshots—Scheduled
and automatic snapshots will occur normally.
l
User interaction required for manual snapshots—Manual snapshots can be
taken normally.
Target restarted without connection persistence
l
State—Bad
l
Description—The target service has been restarted and was unable to persist
connection information, therefore, operations that were in the queue have been
lost.
l
Automatic action taken for scheduled and automatic snapshots—An
automatic snapshot will be taken after the target restarts, if the target data was in a
good state prior to the target restart and the connection is configured to auto-
remirror on auto-reconnect. Scheduled snapshots will be delayed until the target
data is back in a good state.
l
User interaction required for manual snapshots—Start a mirror, wait until it is
complete and the data is in a good state, and then take a manual snapshot.
Restore required
l
State—Good or bad
l
Description—The data on the target no longer matches the data on the source
because of a failover. This does not necessarily mean that the data on the target is
bad.
l
Automatic action taken for scheduled and automatic snapshots—Scheduled
and automatic snapshots will be delayed until a restore is completed or the
Restore Required state is overruled by a mirror. Once the restoration or mirror is
complete, automatic and scheduled snapshots will occur normally.
l
User interaction required for manual snapshots—Restore the target data back
to the source or override the Restore Required state by performing a mirror. Once
the restoration or mirror is complete, manual snapshots can be taken normally.
Snapshot reverted
l
State—Good or bad
l
Description—The data on the target no longer matches the data on the source
because a snapshot has been applied on the target. This does not necessarily
mean that the data on the target is bad.