mkpartnership

You can use the mkpartnership command to establish a one-way Remote Copy partnership between the local cluster and a remote cluster. To establish a fully functional Remote Copy partnership, you must issue this command to both clusters. This step is a prerequisite to creating Remote Copy relationships between VDisks on the clusters.

Syntax

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

>--+----------------------------------+-- ---------------------->
   '- -bandwidth -- bandwidth_in_mbs -'

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

Parameters

-bandwidth bandwidth_in_mbs
Optionally specifies the bandwidth to be used by the background copy process between the clusters. It may be used to throttle the bandwidth used by Remote Copy for the initial background copy process. The bandwidth defaults to 50 MBps (megabytes per second) if you do not specify it. The bandwidth should be set to a value that is less than or equal to the bandwidth that can be sustained by the intercluster link. If the parameter is set to a higher value than the link can sustain, the background copy process will simply use the actual available bandwidth.
remote_cluster_id | remote_cluster_name
Specifies the cluster ID or name of the remote cluster. You can use 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 will fail and ask for 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 specified by the command. The equivalent svctask mkpartnership command must also then be issued from the other cluster to create a fully-configured two-way partnership.

Inter-cluster Remote Copy relationships can now be created between primary VDisks in the local cluster and auxiliary VDisks in the remote cluster. Intra-cluster relationships may also be created, where both VDisks reside in the local cluster.

Possible failures

Examples

An invocation example

svctask mkpartnership -bandwidth 20 cluster1