mkpartnership

The mkpartnership command establishes a one-way Metro Mirror or Global Mirror relationship between the local cluster and a remote cluster.

Syntax

To establish a fully functional Metro Mirror or Global Mirror partnership, you must issue this command to both clusters. This step is a prerequisite to creating Metro Mirror or Global Mirror relationships between VDisks on the clusters.

Read syntax diagramSkip visual syntax diagram
>>- svctask -- -- mkpartnership -- ----------------------------->

>-- -bandwidth -- bandwidth_in_mbps -- ------------------------->

>--+- remote_cluster_id ---+-----------------------------------><
   '- remote_cluster_name -'   

Parameters

-bandwidth bandwidth_in_mbps
(Required) Specifies the bandwidth, in megabytes per second (MBps), that is used by the background copy process between the clusters. It adjusts the bandwidth that is used by Metro Mirror or Global Mirror for the initial background copy process. Set the bandwidth to a value that is less than or equal to the bandwidth that can be sustained by the intercluster link. If the -bandwidth parameter is set to a higher value than the link can sustain, the background copy process uses the actual available bandwidth.
remote_cluster_id | remote_cluster_name
(Required) Specifies the cluster ID or name of the remote cluster. Issue the svcinfo lsclustercandidate command to list the remote clusters that are available. If two or more remote clusters have the same name and the name is included in this command, the command fails and it requests the ID of the cluster instead of the name.

Description

This command creates a one-way partnership between the local cluster and the remote cluster that you specify in the command. To create a two-way partnership, the equivalent svctask mkpartnership command must be issued from the other cluster. The maximum supported number of clusters in a partnership set is four.

Intercluster Mirror relationships can be created between primary VDisks in the local cluster and auxiliary VDisks in the remote cluster. Intracluster relationships can be created between VDisks that reside in a local cluster. The VDisks must belong to the same I/O group within the cluster.

Note: Background copy bandwidth can impact foreground I/O latency. To set the background copy bandwidth optimally, you must consider all three resources: the primary storage, intercluster link bandwidth, and secondary storage. Provision the most restrictive of these three resources between the background copy bandwidth and the peak foreground I/O workload.

An invocation example

svctask mkpartnership -bandwidth 20 cluster1

The resulting output

No feedback
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2003, 2009. All Rights Reserved.