Silicon Graphics InfiniteStorage 4000 Series, Configuring And Maintaining, Page: 107 / 276

Chapter 5: Using the Snapshot (Legacy) Premium Feature 95
This example shows how to use the command in a script file:
recreate snapshot volumes

[“Mars_Spirit_4-2” “Mars_Spirit_4-3”];
If you do not intend to use a snapshot (legacy) volume again, you can delete the
snapshot (legacy) volume by using the
delete volume
command. When you
delete a snapshot (legacy) volume, the associated snapshot (legacy) repository volume
also is deleted.
Starting,
Stopping, and
Resuming a
Snapshot
(Legacy)
Rollback The snapshot (legacy) volume rollback commands provide a way for you to manage
the content that is maintained by a snapshot (legacy) volume. A snapshot (legacy)
rollback operation enables you to restore the contents of a base volume to a
point-in-time image that was captured in a snapshot (legacy) volume. The base
volume is then immediately accessible for read/write operation using the rolled-back
content after the controller firmware accepts the rollback request. The read/write can
take place while the rolled-back content is being transferred to the base volume. After
the rollback operation is finished, the associated repository volume will be empty. The
associated repository volume still has the capacity required to track new changes
made by a host write operation after the point at which the rollback request was
accepted.
Keep the these guidelines in mind when managing a snapshot (legacy) volume
rollback:

A rollback operation copies from the repository volume only the data clusters
that were changed between the time that the snapshot (legacy) was created and
the time that the rollback was requested.

Users can write to a snapshot (legacy) volume. Any changes made to a snapshot
(legacy) volume after the creation of the original snapshot (legacy) image are
included in the snapshot (legacy) rollback. Because of this, the rollback image to
the base volume might not have the exact content as when the snapshot (legacy)
image was originally created.

The source snapshot (legacy) content is fully preserved and can be reused if you
want to roll the snapshot (legacy) back again until you change the content of the
snapshot (legacy) volume.

You can perform only one snapshot (legacy) rollback operation at a time for a
given base volume.

While a rollback operation is taking place, you cannot delete the snapshot
(legacy) volume.

Rollback operations are mutually exclusive with volume copy operations that
involve the base volume,either as the source or the destination of the volume
copy. A request to start a rollback will be rejected if any volume copy
relationship exists for the base volume. Similarly, an attempt to create a volume
copy involving the base volume will be rejected if that base volume has a
rollback operation in progress.