addvolumecopy
Use the addvolumecopy command to add a copy to an existing volume. On a standard topology system, you can use this command to add a mirrored copy to an existing volume. On a stretched or HyperSwap® topology system, you can use this command to convert an existing basic volume into a highly available volume by adding a copy of that volume at a second site.
Syntax
>>- addvolumecopy -- -- -pool --+- storage_pool_id ---+-- ------> '- storage_pool_name -' >--+------------------------------+-- --------------------------> '- -iogrp --+- iogroup_id ---+-' '- iogroup_name -' >--+---------------------------+-- -----------------------------> '- -cache --+- none ------+-' +- readonly --+ '- readwrite -' >--+----------------------------+-- --+-------------------+-----> '- -image --+- mdisk_id ---+-' '-+- -thin -------+-' '- mdisk_name -' '- -compressed -' >-- --+-----------------------------------------+-- ------------> '- -buffersize --+- buffer_size --------+-' '- buffer_percentage% -' >--+-------------------+-- -------------------------------------> | .- mb -. | '- -unit --+- b --+-' +- kb -+ +- gb -+ +- tb -+ '- pb -' >--+---------------------------------------+-- -----------------> '- -warning --+- warning_capacity ----+-' '- warning_percentage% -' >--+-----------------+-- --+-------------------------+-- -------> '- -noautoexpand -' '- -grainsize --+- 32 --+-' +- 64 --+ +- 128 -+ '- 256 -' >--+- volume_id ---+-- ---------------------------------------->< '- volume_name -'
Parameters
- (Required) Specifies the storage pool in which to create the new volume copy. Remember: For stretched and hyperswap topology systems, the site of storage pool must not be the same as the site of the existing volume copy.
- (Optional) Specifies the I/O group that the new volume copy is cached in. Note: This parameter applies only when you are creating a HyperSwap volume and requires that the system topology be hyperswap.The I/O group must be in the same site as the storage pool that is being specified.
- (Optional) Specifies the caching options for the volume copy. Valid entries are:
- readwrite enables the cache for the volume *
- readonly disables write caching but allows read caching for a volume
- none disables the cache mode for the volume
Note: This parameter applies only when you are creating a HyperSwap volume and requires that the system topology be hyperswap. - (Optional) Specifies that the volume copy is to be created (on any topology) in image mode and
it specifies which currently unused MDisk to use. Note: For a stretched or hyperswap topology system the MDisk site must match the storage pool site. If the storage pool is empty, the MDisk site must be 1 or 2, and the MDisk site cannot be the same as the site of the existing volume copy.
- (Optional) Specifies that the volume copy is to be created with
thin-provisioning. You cannot specify this parameter with -compressed. Note: If you do not specify either -thin or -compressed the volume copy is created as one that is fully-allocated.
- (Optional) Specifies that the volume copy is to be created compressed. You cannot specify this parameter with -thin.
- (Optional) Specifies the pool capacity the volume attempts to reserve as a buffer for thin-provisioned and compressed volumes. You must specify either -thin or -compressed with this parameter.
- (Optional) Specifies a threshold at which a warning error log
is generated for the volume copy. A warning is generated when the
used disk capacity on the thin-provisioned or compressed copy exceeds
the specified threshold. You can specify the threshold by using warning_capacity to
specify a size, which defaults to MB unless the -unit parameter
is specified.Note: You can also specify a warning_percentage%, to use a percentage of the volume size. If you do not specify a warning threshold, a default value of 80% is used. To disable warnings, specify 0.
You must specify either -thin or -compressed with this parameter.
- (Optional) Specifies the data units for the -buffersize and -warning parameters.
- (Optional) Specifies that the volume copy not automatically expand
as it is written to; the available buffer capacity decreases as the
used capacity increases. The copy goes offline if the buffer capacity
is consumed.
The buffer capacity can be increased by specifying expandvdisksize -rsize. You must specify either -thin or -compressed with this parameter. If you do not specify this keyword the copy automatically expands as it is written to.
- (Optional) Sets the grain size (KB) for a thin-provisioned volume. If you are using the thin-provisioned volume in a FlashCopy® map, use the same grain size as the map grain size for best performance. If you are using the thin-provisioned volume directly with a host system, use a small grain size. The grain size value must be 32, 64, 128, or 256 KB. The default is 256 KB.
- (Required) Specifies the volume to add the volume copy to.
Description
Use the addvolumecopy command to add a copy to an existing volume. The new volume copy is synchronized with the current copy.
On a standard topology system, you can use this command to add a mirrored copy to an existing volume. On a stretched or HyperSwap topology system, you can use this command to convert an existing basic volume into a highly available volume by adding a copy of that volume to a second site.
A volume copy cannot be created in the same site as an existing copy of the volume. This command automatically adds the caching I/O group to the access I/O group set of the volume.
Add a volume copy to an existing volume
addvolumecopy -pool 2 volume5The detailed resulting output:
No feedbackAdd a thin volume copy to an existing volume
addvolumecopy -pool site2pool1 -thin 0The detailed resulting output:
No feedbackAdd a fully-allocated image-mode volume copy
addvolumecopy -image mdisk12 -pool 3 volume2The detailed resulting output:
No feedback