HP P2000 G3, Cli Reference Manual

Page: 343 / 532

HP P2000 G3 MSA System CLI Reference Guide 343
volumecopy
Description Copies a standard, master, or snapshot volume to a new standard volume. The destination volume
you specify must be in a vdisk owned by the same controller as the source volume. If the source
volume is a snapshot, you can choose whether to include its modified data (data written to the
snapshot since it was created). The destination volume is completely independent of the source
volume.
The first time a volume copy is created of a standard volume, the volume is converted to a master
volume and a snap pool is created in the volume’s vdisk. The snap pool’s size is either 20% of the
volume size or 5.37 GB, whichever is larger. Before creating or scheduling copies, verify that the
vdisk has enough free space to contain the snap pool.
NOTE: In rare cases, a large amount of I/O can cause a snap pool that is too small to fill quickly.
This can result in all snapshots being deleted due to the snap pool running out of space. If you
expect the snap pool to have a high rate of data change, use the show snap-pools command to
view the snap pool’s size. If it is less than 50 GB, use the expand snap-pool command to expand its
size to at least 50 GB.
Before copying a master volume, verify that the snap-pool has space for a transient snapshot, which
is used to track changes to the master volume while the copy is in progress.
For a master volume, the volume copy creates a transient snapshot, copies the data from the
snapshot, and deletes the snapshot when the copy is complete. For a snapshot, the volume copy is
performed directly from the source; this source data may change if modified data is to be included
in the copy and the snapshot is mounted/presented/mapped and I/O is occurring to it.
To ensure the integrity of a copy of a master volume, unmount/unpresent/unmap the volume or at
minimum perform a system cache flush and refrain from writing to the volume. Since the system
cache flush is not natively supported on all operating systems, it is recommended to
unmount/unpresent/unmap temporarily. The volume copy is for all data on the disk at the time of
the request, so if there is data in the operating-system cache, that will not be copied over.
Unmounting/unpresenting/unmapping the volume forces the cache flush from the operating system.
After the volume copy has started, it is safe to remount/re-present/remap the volume and/or
resume I/O.
To ensure the integrity of a copy of a snapshot with modified data, unmount/unpresent/unmap the
snapshot or perform a system cache flush. The snapshot will not be available for read or write
access until the volume copy is complete, at which time you can remount/re-present/remap the
snapshot. If modified write data is not to be included in the copy, then you may safely leave the
snapshot mounted/presented/mapped. During a volume copy using snapshot modified data, the
system takes the snapshot offline.
While the copy operation is in progress, the destination volume type is shown as
standard*
;
when complete, it changes to
standard
. To see the volume copy’s progress use the show
volumecopy-status command.
Syntax
volumecopy
source-volume source-volume
dest-vdisk vdisk
[modified-snapshot yes|no]
[prompt yes|no|expert]
destination-volume
Parameters
source-volume source-volume
Name or serial number of the volume or snapshot to copy. For volume syntax, see Command syntax
on page 22.
dest-vdisk vdisk
Name or serial number of the destination vdisk. For vdisk syntax, see Command syntax on page 22.