Create a Replication Partner

NOTE: This procedure does not apply to synchronous replication. The replication partners for synchronous replication are pool partners and are created automatically.

Use the management subnet for replication when any of the following conditions apply:

Your data IPs are not routable across the network
You want to separate replication traffic from iSCSI traffic.
Your replication arrays are running release 1.4 or release 2.0 or later versions, and you want to separate replication traffic from iSCSI traffic

NOTE: For release 2.x and later, replication over a data subnet is available; however, it requires the replication control traffic to be transferred over a management subnet. If you choose to replicate over a data subnet, you must be able to do the following:

Route the management subnet between replication partners by the default gateway for replication control traffic
Route the data subnet between replication partners by a static route for replication data transfer traffic
Replication partners can run different data access protocols. For example, a Fibre Channel (FC) replication partner can be created for an iSCSI array, and an iSCSI replication partner can be created for a Fibre Channel array. For replication to function on an FC array, you must also configure an Ethernet link or IP subnet.

For Fibre Channel arrays, you do not need to separate the replication traffic; replication traffic never runs over Fibre Channel.

Select Manage → Data Protection, then click You want to separateReplication Partners in the left pane.
Click Add to add a new replication partner.
Select a replication type. If you select Cloud Replication, enter your HPE CV credentials.
Enter the group name (case-sensitive) of the replication partner for on-premises replication.
(Optional) Enter a description of the partner group.
Perform the following steps for on-premises replication only.
1. Enter the hostname or IP address of the partner group.
2. Type a shared secret. Type it again to confirm.
  
  NOTE: The shared secret must be eight or more printable alphanumeric characters with no spaces or special characters. Special characters include: ' " ` ~ ! @ # $ ^ & ( )+ [ ] {} * ; : ' " . , | < > ? / \ = % .
3. Choose which subnet to use for the replication network. Select one of the following options:
  - Use management or controller IP addresses for replication traffic
  - Use data IP addresses for replication traffic
  NOTE: For release 2.x and later, replication over a data subnet is available; however, it requires the replication control traffic to transverse a management subnet.
Select a location for the inbound replication pool from the Inbound Location list.
(Optional for on-premises replication) Check Use the same pool and folder as the source location.
Click Next.
(Optional) Create a Quality of Service (QoS) policy, which is a bandwidth limit for replication traffic, click Add Policy and complete the fields in the dialog box.
A Quality of Service (QoS) policy defines how the network resources are allocated for the replication partner.
NOTE: Without a QoS policy, the replication partner can use unlimited network bandwidth.
1. (Optional) Enter a description of the policy.
2. Enter a number value and choose a bandwidth in Kbps or Mbps.
3. Indicate the time interval when the policy is in effect.
  The time should be the time in the array time zone, not the client time zone.
4. Check the boxes for the days of the week when the policy is in effect.
5. Click Create.
Click Create.
It can take up to ten minutes for the partners to establish contact.