To prepare a volume for the creation of instant and break-off snapshots
If both commands return a value of
on, the volume can be used for instant snapshot operations, and you should skip to step 3. Otherwise continue with step 2.
It is only necessary to run the
prepare command on a volume if it does not already have a version 20 DCO volume (for example, if you have run the
unprepare command on the volume).
See "Creating a volume with a version 20 DCO volume" on page 261.
See "Preparing a volume for DRL and instant snapshots" on page 285.
See "Removing support for DRL and instant snapshots from a volume" on page 289.
For example, to prepare the volume, my
vol, in the disk group,
mydg, use the following command:
vxsnap -g mydg prepare myvol regionsize=128k ndcomirs=2 \
This example creates a DCO object and redundant DCO volume with two plexes located on disks
mydg11, and associates them with
myvol. The region size is also increased to 128KB from the default size of 64KB. The region size must be a power of 2, and be greater than or equal to 16KB. A smaller value requires more disk space for the change maps, but the finer granularity provides faster resynchronization.
See "Creating a shared cache object" on page 330.
For full-sized instant snapshots and linked break-off snapshots, you must prepare a volume that is to be used as the snapshot volume. This volume must be the same size as the data volume for which the snapshot is being created, and it must also have the same region size.
See "Creating a volume for use as a full-sized instant or linked break-off snapshot" on page 331.
To create a shared cache object
vxassistcommand to create the volume that is to be used for the cache volume. The following example creates a mirrored cache volume,
cachevol, with size 1GB in the disk group,
mydg, on the disks
vxassist -g mydg make cachevol 1g layout=mirror \
init=active mydg16 mydg17
init=active is specified to make the cache volume immediately available for use.
cachecommand to create a cache object on top of the cache volume that you created in the previous step:
vxmake [-g diskgroup
] cache cache_object
] [autogrow=on] \
If the region size,
regionsize, is specified, it must be a power of 2, and be greater than or equal to 16KB (
16k). If not specified, the region size of the cache is set to 64KB.
All space-optimized snapshots that share the cache must have a region size that is equal to or an integer multiple of the region size set on the cache. Snapshot creation also fails if the original volume's region size is smaller than the cache's region size.
If the region size of a space-optimized snapshot differs from the region size of the cache, this can degrade the system's performance compared to the case where the region sizes are the same.
If the cache is to be allowed to grow in size as required, specify
autogrow=on. By default, the ability to automatically grow the cache is turned off.
In the following example, the cache object,
cobjmydg, is created over the cache volume,
cachevol, the region size of the cache is set to 32KB, and the
autogrow feature is enabled:
vxmake -g mydg cache cobjmydg cachevolname=cachevol \
vxcache [-g diskgroup
] start cache_object
For example to start the cache object,
vxcache -g mydg start cobjmydg
See "Removing a cache" on page 354.
To create an empty volume for use by a full-sized instant snapshot or a linked break-off snapshot
vxprintcommand on the original volume to find the required size for the snapshot volume.
The command as shown assumes that you are using a Bourne-type shell such as
bash. You may need to modify the command for other shells such as
vxprintcommand on the original volume to discover the name of its DCO:
] -F%dco_name volume
vxprintcommand on the DCO to discover its region size (in blocks):
] -F%regionsz $DCONAME'
vxassistcommand to create a volume, snapvol, of the required size and redundancy, together with a version 20 DCO volume with the correct region size:
] logtype=dco drl=off \
] regionsz=$RSZ \
Specify the same number of DCO mirrors (
ndcomirror) as the number of mirrors in the volume (
init=active attribute is used to make the volume available immediately. You can use storage attributes to specify which disks should be used for the volume.
As an alternative to creating the snapshot volume and its DCO volume in a single step, you can first create the volume, and then prepare it for instant snapshot operations as shown here:
] init=active \