CLI Guide

Arguments
Required arguments
--file pathname * Directory and filename of migration plan file. Relative paths can be used. If no directory is specified,
the default directory is /var/log/VPlex/cli on the management server.
Optional arguments
[-s|transfer-
size] size
Maximum number of bytes to transfer as one operation per device. Specifies the size of read sector
designated for transfer in cache. Setting transfer size to a lower value implies more host I/O outside
the transfer boundaries. Setting transfer size to a higher value may result in faster transfers. See About
transfer-size below. Valid values must be a multiple of 4 K.
● Range: 40 K - 128 M.
● Default: 128 K.
--force
Do not ask for confirmation when starting individual migrations. Allows this command to be run using a
non-interactive script, .
--paused
Starts the migration in a paused state. The migration remains paused until restarted using the batch-
migrate resume command.
* - argument is positional.
Description
Starts a migration for every source/target pair in the given migration-plan.
CAUTION:
Inter-cluster migration of volumes is not supported on volumes that are in use. Schedule this activity
as a maintenance activity to avoid Data Unavailability.
Consider scheduling this activity during maintenance windows of low workload to reduce impact on applications
and possibility of a disruption.
If a migration fails to start, the command prints a warning to the console. The command continues until every migration item
completes been processing.
Individual migrations may ask for confirmation when they start. Use the --force argument to suppress these requests for
confirmation.
Batch migrations across clusters can result in the following error:
VPlexcli:/> batch-migrate start /var/log/VPlex/cli/migrate.txt
The source device 'SveTest_tgt_r0_case2_1_0002' has a volume
'SveTest_tgt_r0_case2_1_0002_vol' in a view. Migrating to device
'SveTest_src_r0_case2_2_0002' will create a synchronous distributed device. In this GEO
system, this can increase the per I/O latency on 'SveTest_tgt_r0_case2_1_0002_vol'. If
applications using 'SveTest_tgt_r0_case2_1_0002_vol' are sensitive to this latency, they
may experience data unavailability. Do you wish to proceed ? (Yes/No) y
WARNING: Failed to start migration /clusters/cluster-1/devices/
SveTest_tgt_r0_case2_1_0002 --> /clusters/cluster-2/devices/SveTest_src_r0_case2_2_0002
: Evaluation of <<dm migration start -n BR0_0 -f /clusters/cluster-1/devices/
SveTest_tgt_r0_case2_1_0002 -t /clusters/cluster-2/devices/SveTest_src_r0_case2_2_0002 -
s 128kB>> failed.
Failed to create a new data-migration.
Unable to attach mirror 'SveTest_src_r0_case2_2_0002' to distributed Device
'MIGRATE_BR0_0'.
Firmware command error.
Active metadata device does not have a free slot.
Started 0 of 1 migrations.
Refer to the troubleshooting section of the metro node procedures in the SolVe Desktop for instructions on increasing the
number of slots.
Commands
49