Administrator Guide

NOTE: You can change protocols used in the peer connection between FC and iSCSI by modifying the peer
connection to use the remote port address of the new protocol.
4. Enter the name and password of a user assigned a manage role on the remote system.
5. Click OK. The peer connection is modified and the Peer Connections table is updated.
Deleting a peer connection
You can delete a peer connection if there are no replication sets that belong to the peer connection. If there are replications sets that
belong to the peer connection, you must delete them before you can delete the peer connection. For more information, see Deleting a
replication set.
NOTE: If the peer connection is down and there is no communication between the primary and secondary systems, use
the local-only parameter of the delete replication-set CLI command to delete the replication set.
NOTE: If CHAP is enabled on one system within a peer connection, be sure that CHAP is configured properly on the
corresponding peer system before initiating this operation. For more information about configuring CHAP, see CHAP
and replication.
Delete a peer connection
1. In the Replications topic, select the peer connection to be deleted in the Peer Connections table.
2. Select Action > Delete Peer Connection.
3. Click OK. The peer connection is deleted and the Peer Connections table is updated.
Creating a replication set from the Replications
topic
You can create a replication set, which specifies the components of a replication. The Create Replication Set panel enables you to create
replication sets. You can access this panel from both the Replications and Volumes topics.
Performing this action creates the replication set and the infrastructure for the replication set. For a selected volume, snapshot, or volume
group, the action creates a secondary volume or volume group and the internal snapshots required to support replications. By default, the
secondary volume or volume group and infrastructure are created in the pool corresponding to the one for the primary volume or volume
group (A or B). Optionally, you can select the other pool.
A peer connection must be defined to create and use a replication set. A replication set can specify only one peer connection and pool.
When creating a replication set, communication between the peer connection systems must be operational during the entire process.
If a volume group is part of a replication set, volumes cannot be added to or deleted from the volume group.
If a replication set is deleted, the internal snapshots created by the system for replication are also deleted. After the replication set is
deleted, the primary and secondary volumes can be used like any other base volumes or volume groups.
Primary volumes and volume groups
The volume, volume group, or snapshot that will be replicated is called the primary volume or volume group. It can belong to only one
replication set. If the volume group is already in a replication set, individual volumes may not be included in separate replication sets.
Conversely, if a volume that is a member of a volume group is already in a replication set, its volume group cannot be included in a
separate replication set.
The maximum number of individual volumes and snapshots that can be replicated is 32 in total. If a volume group is being replicated, the
maximum number of volumes that can exist in the group is 16.
Using a volume group for a replication set enables you to make sure that the contents of multiple volumes are synchronized at the same
time. When a volume group is replicated, snapshots of all of the volumes are created simultaneously. In doing so, it functions as a
consistency group, ensuring consistent copies of a group of volumes. The snapshots are then replicated as a group. Though the snapshots
may differ in size, replication of the volume group is not complete until all of the snapshots are replicated.
Working in the Replications topic
121