The following are the differences between the two:
•
Read-Only snapshot virtual disks provide the host read access to a copy of the data contained in the snapshot image. However, the
host cannot modify the snapshot image. A Read-Only snapshot virtual disk does require an associated repository.
•
Read-Write snapshot virtual disks require an associated repository to provide the host write access to a copy of the data contained in
the snapshot image. A Read-Write snapshot virtual disk requires its own repository to save any subsequent modifications made by the
host application to the base virtual disk without affecting the referenced snapshot image. The snapshot is allocated from the storage
pool from which the original snapshot image is allocated. All I/O writes to the snapshot image are redirected to the snapshot virtual disk
repository that was allocated for saving data modifications. The data of the original snapshot image remains unchanged. For more
information, see
Understanding Snapshot Repositories
Snapshot groups and consistency groups
The Snapshot Virtual Disk premium feature supports the following types of snapshot groups:
•
Snapshot groups — A snapshot group is a collection of point-in-time images of a single associated base virtual disk.
•
Consistency groups — A consistency group is a group of virtual disks that you can manage as a single entity. Operations performed on
a consistency group are performed simultaneously on all virtual disks in the group.
Snapshot groups
The purpose of a snapshot group is to create a sequence of snapshot images on a given base virtual disk without impacting performance.
You can set up a schedule for a snapshot group to automatically create a snapshot image at a specific time in the future or on a regular
basis.
When creating a snapshot group, the following rules apply:
•
Snapshot groups can be created with or without snapshot images.
•
Each snapshot image is can be a member of only one snapshot group.
•
Standard virtual disks and thin virtual disks are the only types of virtual disks that can contain a snapshot group. Non-standard virtual
disks, such as snapshot virtual disks, cannot be used for snapshot groups.
•
The base virtual disk can reside on either a disk group or a disk pool.
•
Snapshot virtual disks and snapshot groups cannot exist on the same base virtual disk.
A snapshot group uses a repository to save all data for the snapshot images contained in the group. A snapshot image operation uses less
disk space than a full physical copy because the data stored in the repository is only the data that has changed since the latest snapshot
image.
A snapshot group is created initially with one repository virtual disk. The repository initially contains a small amount of data, then increases
over time with subsequent data updates. You can increase the size of the repository by increasing the capacity of the repository, or add
virtual disks to the repository.
Snapshot consistency groups
To perform the same snapshot image operations on multiple virtual disks, you can create a consistency group containing the virtual disks.
Any operation performed on the consistency group is performed simultaneously on all of the virtual disks in that group, which creates
consistent copies of data between each virtual disk. Consistency groups are commonly used to create, schedule, or rollback virtual disks.
Each virtual disk belonging to a consistency group is referred to as a member virtual disk. When you add a virtual disk to a consistency
group, the system automatically creates a new snapshot group that corresponds to this member virtual disk. You can set up a schedule for
a consistency group to automatically create a snapshot image of each member virtual disk in the group at a specific time in the future or on
a regular basis.
110
Premium feature—Snapshot Virtual Disk
