The following figure shows the difference between rolling back the master volume to the data that
existed when a specified snapshot was created (preserved), and rolling back preserved and modified
data.
MasterVolume-1
When you use the rollback feature, you
can choose to exclude the modified data,
which will revert the data on the master
volume to the preserved data when
the snapshot was taken.
MasterVolume-1
Or you can choose to include the modified
data since the snapshot was taken, which
will revert the data on the master volume
to the current snapshot.
Figure 2
Rolling back a master volume
Snapshot operations are I/O-intensive. Every write to a unique location in a master volume after a
snapshot is taken will cause an internal read and write operation to occur in order to preserve the snapshot
data. If you intend to create snapshots of, create volume copies of, or replicate volumes in a vdisk, ensure
that the vdisk contains no more than four master volumes, snap pools, or both. For example: 2 master
volumes and 2 snap pools; 3 master volumes and 1 snap pool; 4 master volumes and 0 snap pools.
Related topics
• Installing a license
•
Creating a snapshot
•
Changing a snapshot's default mapping
• Deleting snapshots
• Resetting a snapshot
•
Viewing information about a snapshot
system
(page
• Rolling back a volume
• Deleting schedules
28
Getting started
on page 41
(page
69) or multiple snapshots
on page 69
on page 70
89)
on page 73
on page 77
Snap Pool-1
Snap Pool-1
(page
68)
(page
66) or explicit mappings
(page
96), a vdisk
(page
Snapshot-1
Preserved Data
(Monday)
Modified Data
(Tuesday)
Snapshot-1
Preserved Data
(Monday)
Modified Data
(Tuesday)
(page
67)
92), all vdisks
(page
91), or the