Hp Storage Mirroring Software User Manual Page 605

  • Download
  • Add to my manuals
  • Print
  • Page
    / 678
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 604
Snapshots Page 604 of 677
l Automatic action taken for scheduled and automatic snapshots—Scheduled
and automatic snapshots will be delayed until a restore is completed or the
Snapshot Reverted 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 Snapshot Reverted state by performing a mirror. Once
the restoration or mirror is complete, manual snapshots can be taken normally.
Restore complete
l State—Good
l Description—Because the restoration is complete, the data on the source and
target is synchronized.
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.
To be completely assured that your data on the target is good, automatic and scheduled
snapshots only occur when the data is in a good Storage Mirroring Recover state.
However, manual snapshots can be taken during any state. There are instances when
you may want to take a manual snapshot, even if the target data is in a bad state. For
example, if you drop an operation, that does not necessarily mean your data on the
target is corrupt or the target would be unable to stand in for the source in the event of a
failure. A snapshot of a bad state may be useful and usable, depending on your
environment. If your source is a file server and an operation has been dropped, it is just
one user file that is out-of-date. All of the remaining target files are intact and can be
accessed in the event of a failure.
However, if your source is an application server and an operation has been dropped,
that one file could cause the application not to start on the target in the event of a failure.
In these cases, manual snapshots of a bad state depend on the context of your
environment.
Note: Because the driver for Volume Shadow Copy is started before the driver for
Storage Mirroring Recover, if you revert any files on the source that are contained
in your replication set, Storage Mirroring Recover will not be aware of the revert
and, therefore, the file change will not be replicated to the target. The file change
will be mirrored to the target during the next mirroring process.
Page view 604
1 2 ... 600 601 602 603 604 605 606 607 608 609 610 ... 677 678

Comments to this Manuals

No comments