The chpartnership command modifies the bandwidth of the partnership between the local cluster and the remote cluster that is specified in the command. This affects the bandwidth that is available for background copy in a cluster partnership by either Metro Mirror or Global Mirror operations. This command can also be used to disable and re-enable the partnership, to permit the local cluster to be disconnected and then reconnected to the remote cluster.
Syntax
>>- svctask -- -- chpartnership -- -----------------------------> >--+-----------------------------------+-- --+----------+-- ----> '- -bandwidth -- bandwidth_in_mbps -' +- -start -+ '- -stop --' >--+- remote_cluster_id ---+----------------------------------->< '- remote_cluster_name -'
Parameters
- -bandwidth bandwidth_in_mbps
- (Optional) Specifies the new bandwidth in megabytes per second (MBps). This bandwidth is used to cap the background remote copy progress. Set the bandwidth to the maximum rate that the remote copies should resynchronize at. Write operations from the host add to the use of the cluster link. If this parameter is set to a value that is greater than the intercluster links can sustain, the actual copy rate defaults to what is available on the link.
- -start | -stop
- (Optional) Starts or stops a Metro Mirror or Global Mirror partnership. To start or stop a partnership, run the svctask chpartnership command from either cluster.
- remote_cluster_id | remote_cluster_name
- (Required) Specifies the cluster ID or name of the remote cluster. The intracluster bandwidth cannot be modified, so if you enter the local cluster name or ID, an error occurs.
Description
This command modifies the bandwidth of the partnership between the local cluster and the remote cluster that is specified in the command. This affects the bandwidth that is available for a background copy in Metro Mirror or Global Mirror relationships, in the direction from the local to the remote cluster. To modify the background copy bandwidth in the other direction (remote cluster –> local cluster), it is necessary to issue the corresponding chpartnership command to the remote cluster.
When you stop the cluster partnership, you temporarily disable the partnership and disconnect the local cluster from the remote cluster. The configuration is retained. The cluster partnership must be in either the partially_configured_stopped or fully_configured_stopped states to be started.
An invocation example
svctask chpartnership -bandwidth 20 cluster1 svctask chpartnership -stop cluster1
The resulting output
No feedback