Use the Viewing Metro and
Global Mirror Cluster Partnerships panel in the SAN Volume Controller Console to
view or create all Metro
Mirror or Global Mirror cluster
partnerships.
Introduction
Metro Mirror and Global Mirror partnerships define
the relationship between a local cluster and a remote cluster. Each cluster can have a maximum of three partner
clusters, with a maximum of four clusters connected directly or indirectly.
By creating multiple partnerships between clusters, administrators
can design topologies for disaster recovery and data migration.
For example, administrators can create
multiple partnerships between four clusters: Cluster A to Cluster
B partnership, Cluster A to Cluster C partnership, and Cluster A to
Cluster D partnership. In this example, Cluster A might be the central
disaster recovery site for the other three clusters. In the event
of a disruption of service to Cluster B, C, or D, Cluster A can be
used to recover important applications and to resume normal operations
from a remote site. Another example topology for multiple cluster
partnerships provides data migration and disaster recovery using three
clusters. In this example, Cluster A and Cluster B are in a partnership;
Cluster A and Cluster C are partners; and Cluster B and Cluster C
are in a partnership. An administrator can use this topology to migrate
a data center from Cluster B to Cluster C. If Cluster A hosts production,
then Cluster B and C can also provide disaster recovery.
On this panel you can either view all the cluster partnerships
that are defined on this cluster, or if cluster partnerships are not
defined, you can click Create to open the Create
Cluster Partnership panel.
This panel displays two sets of properties that are related
to cluster partnerships. The first table contains properties that
pertain to Global Mirror partnerships that are defined on the selected
cluster. The second table displays properties for each of the clusters
that are defined in partnerships with the selected cluster.
Attributes
The following properties pertain to all the Global Mirror
partnership in the cluster:
- Link Tolerance
- Displays the length of time that the primary response time remains
impacted before relationships are suspended. Valid values are 0 -
86400 seconds. A value of zero disables this feature. The default
value is 300 seconds.
- Inter-Cluster Delay Simulation
- Displays the amount of time to delay I/O writes to the intercluster
secondary VDisk. Valid values are 0 - 100 milliseconds. A value
of zero disables this feature. The default value is zero.
- Intra-Cluster Delay Simulation
- Displays the amount of time to delay I/O writes to the intracluster
secondary VDisk. Valid values are 0 - 100 milliseconds. A value
of zero disables this feature. The default value is zero.
Attributes
The
following attributes are displayed in the table if a cluster partnership
exists:
- Select
- Select the object to perform an action from the task list.
Note: Only
one row can be selected at a time.
- Cluster Name
- Displays the name of the selected cluster.
- IP address (IPv4)
- Displays the IPv4 IP address of the local or remote partner cluster.
- IP address (IPv6)
- Displays the IPv6 IP address of the local or remote partner cluster.
- State
- Displays the current state of the partnership. The following values
are possible:
- Partially Configured
- Indicates that only one cluster partner is defined from a local
or remote cluster to the displayed cluster and is started. For the
displayed cluster to be configured fully and to complete the partnership,
you must define the cluster partnership from the cluster that is displayed
to the corresponding local or remote cluster. You can do this by issuing
the mkpartnership command on the local and remote cluster that
are in the partnership, or by using the SAN Volume Controller Console to
create a partnership on both the local and remote clusters.
- Fully Configured
- Indicates that the partnership is defined on the local and remote
clusters and is started.
- Remote Not Present
- Indicates that the remote cluster is not present to the partnership.
- Partially Configured (Local Stopped)
- Indicates that the local cluster is only defined to remote cluster
and the local cluster is stopped.
- Fully Configured (Local Stopped)
- Indicates that a partnership is defined on both the local and
remote clusters and the remote cluster is present, but the local cluster
is stopped.
- Fully Configured (Remote Stopped)
- Indicates that a partnership is defined on both the local and
remote clusters and the remote cluster is present, but the remote
cluster is stopped.
- Fully Configured (Local Excluded)
- Indicates that a partnership is defined between a local and remote
cluster; however, the local cluster has been excluded. Usually this
state occurs when the fabric link between the two clusters has been
compromised by too many fabric errors or slow response times of the
cluster partnership. Check the error log for 1720 errors by selecting to resolve these errors.
- Fully Configured (Remote Excluded)
- Indicates that a partnership is defined between a local and remote
cluster; however, the remote cluster has been excluded. Usually this
state occurs when the fabric link between the two clusters has been
compromised by too many fabric errors or slow response times of the
cluster partnership. Check the error log for 1720 errors by selecting to resolve these errors.
- Fully Configured (Remote Exceeded)
- Indicates that a partnership is defined between a local and remote
cluster and the remote is available; however, the remote cluster exceeds
the number of allowed clusters within a cluster network. The maximum
of four clusters can be defined in a network. If the number of clusters
exceeds that limit, SAN Volume Controller determines
the inactive cluster or clusters by sorting all the clusters by their
unique identifier in numerical order. The inactive cluster partner
which is not in the top four of the cluster unique identifiers displays Fully
Configured (Remote Exceeded).
- Bandwidth (MBps)
- Displays the bandwidth that was specified,
shown in megabytes per second (MBps).
Actions
You
can select one of the following tasks from the task list:
- Create a Partnership
- Modify a Partnership
- Delete a Partnership
- Start a Partnership
- Stop a Partnership
Note: With the exception of the Create a Partnership task,
you must first select a partner cluster before you can select a task.
- Go
- Click this button after selecting a task from the task list. Clicking Go launches
the panel for the task that you selected.
- Modify
- Click this button to change the properties for Global
Mirror partnerships.
- Refresh
- Click this button to refresh the table with changed values.