Shell Commands › Volume Management › copy (Volume Management)--Copy a Volume

copy (Volume Management)--Copy a Volume

Copy a volume.

Syntax

volume copy <src> <dst> [comment=<val> | --stripcomment] [size=<val>] [fs_options=<val>] [--use-filer] [--fscpy [--prefill]] [ -n ] [--overwrite [--force]]  

Options

<src>

Name of the existing volume to copy. May specify any volume

<dst>

Name of the new copied volume. Must specify an application user or singleton class volume or global volume

comment=<val>

Comment that is to be set for the destination volume

--stripcomment

Set the comment for the destination volume to empty.

size=<val>

Specify size for new volume. If not specified, the destination volume is created with the same size as the source volume. Units may be specified(for example, 128M[B], 2G[B]). If units are not specified, it is assumed that the size is in MB.

fs_options=<val>

File system-specific options. Only valid if --fscpy argument is specified.

--use-filer

If the copy operation can be done as a block level copy and this option is specified, do the block level copy in the filer instead of on the controller. This can be used for partitioned or unpartitioned volumes.

--fscpy

Perform filesystem level copy when copying the volume. If this option is not specified, block-level copy is performed.

--prefill

Allocate ALL blocks for new volume. This option is only valid if --fscpy is specified; otherwise it is ignored.

--overwrite

Overwrite destination volume if it exists

--force

Do not prompt for confirmation of overwrite

-n

Skip verification that volume reference is in the class descriptor if destination volume is an application singleton class volume.

Notes:

• When the ctl_blk_cpy parameter in applogic.conf file is set to 0, block level copies are performed using a Linux Filer. When either it is not present, or it is set to 1, the block level copy operations are performed using Controller. Default is 1.
• The “mirrored=” argument is not useful on CA AppLogic for System z® as disk mirroring is not managed by the product. Providing “mirrored=” to “vol copy” will produce a warning but it will otherwise be ignored.
• Only grid maintainers may copy a volume to a global read-only volume (that is, _GLOBAL_RO:<volume>) When copying partitions as opposed to whole volumes, only one partition/lvm logical volume can be copied at a time.
• Size cannot be used if any of the src or dst is used, or the source volume is partitioned (use vol resize instead)
• No changes are done to the partitioning table of the destination volume.
• Specifying partitions, as is available in the distributed version of the product, will currently result in an error.
• The value specified for the fs_options parameter is filesystem specific.
• The following are the options available for each supported filesystem:

  ext2 | ext3 | swap

  <any option> - any option understood by mkfs.<filesystem>. The options will be passed directly to the mkfs tool for the chosen filesystem.

  ext3-snapshot

  vol_group_name - string specifying the name of the LVM volume group to create on the volume. If not specified, a volume group name is randomly generated.

  data_percentage - percentage of the volume that is used to store data, remaining portion of the volume is for snapshots. If not specified, 80% of the volume is used for data.

  <any option> - any option understood by mkfs.ext3. The options will be passed directly to the mkfs tool and will be used for the data volume.

Examples

volume copy my-app:data my-app:data2

Copy application user volume. The volume may be partitioned or unpartitioned.

volume copy my-app:data my-app:data2 --fscpy

Copy application user volume using filesystem level copy. (The operation will fail if any of the partitions are not supported by the Filer.)

volume copy /system:MYSQL5.boot my-app:DBASE.boot -n

Copy global catalog class volume.

volume copy my-app:DBASE.boot my-app2:DBASE.boot