Table of Contents
Advertisement
2 Commands
l
l
l
l
l
l
l
l
l
l
2-154
You can delete a snapshot mirroring from a volume or volume set by running the command
vxsnap [-g diskgroup] rmmir {snapvol|snapobject}. If the name of a volume set is
specified, a mirroring is deleted from each volume in the volume set.
You can separate an original volume from its snapshot volume and release the relation
between the volume and related snapshots by running the command vxsnap [-f] [-g
diskgroup] split {volume|volset}. In this way, snapshots are released.
Ensure that the snapshot volume at the top of the layer architecture must be completely
–
synchronized. Otherwise, the command cannot be run successfully.
The snapshots at lower layers do not need to be completely resynchronized.
–
If the operation is applied to a volume set or its component volumes, the layer
–
architecture may be inconsistent when the system crashes or hardware fails.
If the operation is applied to a volume set, you must set the –f parameter.
–
You can pause the synchronization of a snapshot by running the command vxsnap [-g
diskgroup] syncpause {volume|volset}.
You can resume the synchronization of a snapshot by running the command vxsnap [-g
diskgroup] syncresume {volume|volset}.
You can start the volume synchronization by running the command vxsnap [-b] [-g
diskgroup] [-o optarg[,optarg]...] [-t tasktag] syncstart {volume|volset}. If you set the –
b parameter, the operation is performed in background mode.
You can stop the volume synchronization by running the command vxsnap [-g
diskgroup] syncstop {volume|volset}.
You can exit the command by running the command vxsnap [-g diskgroup] syncwait
{volume|volset}.
If a volume is invalid (for example, an space-optimized instant snapshot is invalid) or
–
the volume is not synchronized, an error occurs.
You cannot wait for the synchronization completion of a reassociated instant snapshot
–
by running the command.
You can disable the instant snapshot and DRL function of a volume by running the
command vxsnap [-g diskgroup] unprepare {volume|volset}. In addition, the DCOs and
DCO volumes associated with the volume are deleted. If the volume belongs to the snapshot
layer architecture, the command fails to be properly run.
The space-optimized instant snapshot does not need the complete copy of the storage space
on an original volume; however, storage cache is required. When creating a snapshot, you
can set the size of the cache. Before writing data to the original volume, the VxVM keeps
the original data in the cache. The storage cache requires much less storage space than the
original volume, so the storage cache is called optimized capacity. If the data in the cache
is too much, you can use the VxVM to automatically expand the capacity of the cache with
any free space in a disk group.
The space-optimized instant snapshot is not suitable for the volume with a large amount of
write operations (for example, rerecord the log of the database), because the copied
mechanism during write operations may degrade the performance of the volume. If you
want to place the volume and the snapshot in different disk groups (for example, set the
status of the host to offline), you must use the full-sized instant snapshot that is synchronized
or separated snapshot of the third mirroring that does not require the cache object. The
space-optimized instant snapshot cannot be used. If the area specified by a volume is smaller
than the area set for the cache, creating the space-optimized instant snapshot by using the
shared cache fails. If the area specified by a volume is smaller or larger than the area set
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
OceanStor VIS6000 Series Virtual Intelligent Storage
System
Command Reference
Issue 06 (2010-05-10)
Advertisement
Table of Contents
