What is the effect on a clone of a snapshot rollback?
A.
Nothing
B.
Performance may be impacted during the snapshot rollback as the system restores the original
blocks of the share
C.
The clone may disappear if the snapshot being rolled back was taken prior to the clone’s
original snapshot
D.
As long as the clone was promoted prior to the snapshot rollback, no impact will be noticed.
Explanation:
Rolling back to a Snapshot
In addition to accessing the data in a filesystem snapshot directory, snapshots can also be used
to roll back to a previous instance of the filesystem or LUN. This requires destroying any newer
snapshots and their clones, and reverts the share contents to what they were at the time the
snapshot was taken. It does not affect any property settings on the share, though changes to
filesystem root directory access will be lost, as that is part of the filesystem data.
To rollback a filesystem, click the icon for the destination snapshot. A confirmation dialog
will appear, and if there are any clones of the snapshot, any newer snapshots, or their
descendents, they will be displayed, indicating that they will be destroyed as part of this process.
Note:A clone is a writable copy of a share snapshot, and is treated as an independent share for
administrative purposes. Like snapshots, a clone will initially take up no extra space, but as newdata is written to the clone, the space required for the new changes will be associated with the
clone.
Sun ZFS Storage 7000 System Administration Guide, Rolling back to a Snapshot