Datasheet

8068ch09-Copy Servies.fm Draft Document for Review January 29, 2013 12:52 pm
384 IBM Flex System V7000 Storage Node Introduction and Implementation Guide
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 for the partnership.
򐂰 Partially Configured (Local Stopped)
Indicates that the local cluster is only defined to the 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.
򐂰 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.
򐂰 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, the IBM Flex System V7000 Storage Node determines the
inactive cluster or clusters by sorting all the clusters by their unique identifier in numerical
order. The inactive cluster partner that is not in the top four of the cluster unique identifiers
shows Fully Configured (Remote Exceeded).
Remote Copy relationships
A Remote Copy relationship is a relationship between two individual volumes of the same
size. These volumes are called a
master (source) volume and an auxiliary (target) volume.
Typically, the master volume contains the production copy of the data and is the volume that
the application normally accesses. The auxiliary volume typically contains a backup copy of
the data and is used for disaster recovery.
The master and auxiliary volumes are defined when the relationship is created, and these
attributes never change. However, either volume can operate in the primary or secondary role
as necessary. The primary volume contains a valid copy of the application data and receives
updates from the host application, which is analogous to a source volume. The secondary
volume receives a copy of any updates to the primary volume, because these updates are all
transmitted across the mirror link. Therefore, the secondary volume is analogous to a
continuously updated target volume. When a relationship is created, the master volume is
assigned the role of primary volume and the auxiliary volume is assigned the role of
secondary volume. The initial copying direction is from master to auxiliary. When the
relationship is in a consistent state, you can reverse the copy direction.