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
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 | mdisk_name } ] [ { -thin | -compressed } [ -deduplicated ] ] [ -buffersize { buffer_size | buffer_percentage% } ] [ -unit { b | kb | mb | gb | tb | pb } ] [ -warning { warning_capacity | warning_percentage% } ] [ -noautoexpand ] [ -grainsize { 32 | 64 | 128 | 256 } ] { volume_id | volume_name }
Parameters
- -poolstorage_pool_id | storage_pool_name
- (Required) Specifies the storage pool in which to create the new volume copy.
Remember: For hyperswap topology systems, the site of storage pool
must not be the same as the site of the existing volume copy.
- -iogrpiogroup_id | iogroup_name
- (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.
- -cachenone | readonly | readwrite
- (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.
- -imagemdisk_id | mdisk_name
- (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
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.
- -thin
- (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 parameters, the system creates
a fully allocated volume copy.
- -compressed
- (Optional) Specifies that the volume copy is to be created compressed. You cannot specify
this parameter with -thin.
- -deduplicated
- (Optional) Adds a deduplicated volume. If you specify -deduplicated,
you must also specify -thin or -compressed because
it applies only to thin or compressed volumes.
Note: Data deduplication works only with data
reduction storage pools. You can only create deduplicated volumes and volume copies in an I/O
group if no compressed volumes or volume copies exist in the storage pools.
- -buffersizebuffer_size | buffer_percentage%
- (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.
- -warningwarning_capacity | warning_percentage%
- (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.
- -unitb | kb | mb | gb | tb | pb
- (Optional) Specifies the data units for the -buffersize and
-warning parameters.
- -noautoexpand
- (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.
- -grainsize32 | 64 | 128 | 256
- (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.
- volume_id | volume_name
- (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.
Note: A volume cannot have volume copies in different
storage pools if cloud backup is enabled on the volume.
On some node types, you can create a compressed volume copy in a data
reduction storage pool for an I/O group. A compressed volume copy in a data
reduction pool can only be created in an I/O group with V5030, V7000, or SVC node types.
You can create thin-provisioned volume copies on any node type. Volumes can also have fully
allocated volume copies in data reduction storage pools.
Compressed volumes/copies cannot be created if the
I/O group in which the copy is being created supports only software compression and:
- The I/O group already has Real-time compression copies and the copy is data reduction.
- The I/O group already has data reduction copies and the copy uses Real-time
compression.
You cannot specify -buffersize if the volume copy is
created in a data reduction storage pool. Specify -thin or
-compressed to enable thin provisioning or compression.
You cannot specify -noautoexpand when you create
thin-provisioned or compressed volume copies from a data reduction storage pool.
You cannot create a volume copy that is a thin-provisioned or compressed
volume in a data reduction storage pool, and the volume caching mode is none or
readonly. You must specify chvdisk to change the volume
caching mode to readwrite.
You cannot specify -warning for a thin-provisioned or
compressed volume copy in a data reduction storage pool.
You cannot specify -grainsize for thin-provisioned and
compressed volume copies in data reduction storage pools. This type of volume copy is created
with a size of 8 KB.
Thin-provisioned or compressed volume copies in data reduction pools cannot
be created if the data reduction storage pool is offline and requires recovery. If the recovery
is still in progress, you must wait until the recovery is complete and the pool is in
online state.
On a standard topology system, you can use this command to add a mirrored copy to an existing
volume. On a 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.
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.
Scenario 1
If the I/O group contains:
- At least one 8 GB node.
- At least one thin-provisioned or compressed volume in a data reduction
pool.
- And you try to set the FlashCopy bitmap size for that I/O group to at least 1.5 GB.
The command fails due to insufficient resources available.
Scenario 2
When a thin-provisioned or compressed volume
is created within a data reduction pool, the pool must have enough
capacity to create more volumes that track SCSI unmap operations from
the host. If this capacity is not available, the command fails.
Scenario 3
Volumes cannot be created in a data reduction
pool if offline thin-provisioned or compressed volumes exist in a
data reduction pool, either because of thin provisioning (out of space
or corruption), or a component underneath thin provisioning is holding
a volume in the pool offline.
Add a volume copy to an existing
volume
addvolumecopy -pool 2 volume5
The detailed resulting
output:
No feedback
Add a thin-provisioned volume copy to an existing volume
addvolumecopy -pool site2pool1 -thin 0
The detailed
resulting output:
No feedback
Add a fully allocated image-mode volume
copy
addvolumecopy -image mdisk12 -pool 3 volume2
The detailed
resulting output:
No feedback
Add a thin-provisioned volume copy
addvolumecopy -pool paulgilbertl7 -thin thinvdisk3
The detailed resulting output:
No feedback
An invocation example to add a deduplicated volume copy
addvolumecopy -pool datareductionpool10 -thin -deduplicated deduplicatedvolume6
The resulting output:
Vdisk [6] copy [1] successfully created