vCloud Availability for vCloud Director Portal contains replication management scripts. You can use these scripts to delete replications, to move replications between datastores, or to switch replications between vSphere Replication Server instances. You perform these operations without impacting tenant replication.

Мoving Replications Between Datastores

If you need to free space on existing datastore, to rebalance I/O for specific datastores, or to move replications to different datastore, use the move-replications command of the vCloud Availability Installer Appliance.

Use a command line in the following format: vcav move-replications SUBCOMMAND [ARGUMENT].

You can pass the following subcommand values and arguments:

SUBCOMMAND

ARGUMENT

Description

start

<vc_host_ip> <source_ds_name> <target_ds_name>

Moves replications of the <vc_host_ip> from <source_ds_name> to <target_ds_name>.

For example: vcav move-replications start 10.26.235.63 ds_local3_10_26_236_148 ds_local3_10_26_236_148.

continue

None

Continues the operation if the start command fails at some point.

abort

None

Aborts the operation if the start command fails at some point.

Switching Replications Between vSphere Replication Server Instances

If you need to move replications from one vSphere Replication Server to another, for example if the first instance has to enter maintenance mode or to be evacuated, use the switch-vr command of the vCloud Availability Installer Appliance.

Use a command line in the following format: vcav switch-vr SUBCOMMAND [ARGUMENT].

You can pass the following subcommand values and arguments:

SUBCOMMAND

ARGUMENT

Description

start

<vc_host_ip> <source_vr_server_host_ip> <target_vr_server_host_ip>

Switches the replications of the <vc_host_ip> from <source_vr_server_host_ip> to <target_vr_server_host_ip>.

For example, vcav switch-vr start 10.26.235.63 10.26.235.27 10.26.235.28.

continue

None

Continues the operation if the start command fails at some point.

abort

None

Aborts the operation if the start command fails at some point.

Deleting Replications

Use the delete-vdc command of the vCloud Availability Installer Appliance to delete replications.

Use a command line in the following format: vcav delete-vdc SUBCOMMAND [ARGUMENT].

You can pass the following subcommand values and arguments:

SUBCOMMAND

ARGUMENT

Description

start

--orgs <org_name1>[<org_name2>...<org_nameN>]

Deletes replications of <org_name1>[<org_name2>...<org_nameN>]. It breaks all tenant peers.

start

--vdcs <vdc_name1>[<vdc_name2>...<vdc_nameN>]

Deletes replications of <vdc_name1>[<vdc_name2>...<vdc_nameN>]. It breaks all tenant peers.

start

--replications <replication_id1> [<replication_id2>...<replication_idN>]

Deletes replications specified by <replication_id1> [<replication_id2>...<replication_idN>].

For example,

vcav delete-vdc start --replications d090f67c-24e3-4648-a2c3-9a3926d0782d--CGID-29d48892-c754-4f9d-8839-225547a851be.

continue

None

Continues the operation if the start command fails at some point.

abort

None

Abort the operation if the start command fails at some point.

Note:

You can combine subcommands into a single line. For example, vcav delete-vdc start --orgs <org_name1> <org_name2> --vdcs <vdc_name1> <vdc_name2>.

Script Error Logging

You can view the errors during the script execution in the errorReport.txt file in the current working directory.

In case of an error in the script, you can read the error message in the file.

In case an error occurs during the task execution, you can check the task ID in the file. You can use the task ID with the vCloud Director API to find out more about the error.