Dell PowerStore 1200T EMC PowerStore Protecting Your Data - Page 21

Add a remote system connection, Synchronization

Get Dell PowerStore 1200T PDF manuals and user guides View all Dell PowerStore 1200T manuals
Add to My Manuals
Save this manual to your list of manuals

Page 21 highlights

Add a remote system connection Configure a remote system connection between the source and destination systems. A remote system connection is used by asynchronous replication and/or metro. Prerequisites Before creating a remote system connection, ensure that you have obtained the following remote system details: ● System IP address ● User authentication credentials for connecting to the system If you are using jumbo frames, ensure that jumbo frames are configured on both sides of the remote system connection (hosts and network ports), as well as on all ports between the two storage arrays. MTU size mismatch results in a warning in the following cases: ● Configuring a remote system connection. ● Modifying remote system connection settings. ● Using the Verify and update option. NOTE: It is not recommended to change the MTU size of a storage network when a replication session is active. To change the MTU size: 1. Pause replication session. 2. Change MTU the storage network MTU size. 3. Run Verify and update on the remote system to confirm that no warning is issued. 4. Resume the replication session. Steps 1. Select Protection > Remote Systems. 2. In the Remote Systems window, click Add. 3. In the Add Remote System slide-out panel, configure the following: ● Management IP address ● Description (optional) ● Network latency ● Username and password 4. Click Add. Synchronization PowerStore enables you to asynchronously update the destination resource with changes (such as changes in content, size, and membership) that occurred on the source resource since the last synchronization cycle. Synchronization can occur either automatically - according to a set schedule - or manually. Snapshots are synchronized from the source system to the destination system, and maintain block sharing efficiency. When a volume on the destination system is mapped to a host, the system sets the node affinity for this volume, and as a result, all I/Os are automatically directed to the selected node. There is no need to pause and resume the replication session for the I/O redirection to take effect. Setting node affinity for volumes on the destination system provides load balancing and prevents latency of replication. You can set the node affinity manually using REST API. NOTE: If you cannot see the node affinity column in the Volumes table, add it using theShow/Hide Table Columns. NOTE: When you add volumes to a volume group or change the size of the volume group during an asynchronous replication session, the changes do not immediately appear on the destination. You can either perform a manual synchronization or wait until the synchronization occurs based on the RPO. For NAS servers, all file systems on a protected NAS server are synchronized from the source to destination system. When file systems are modified during an asynchronous replication session, the changes are reflected on the destination system at the next synchronization cycle. You can synchronize a replication session when it is in the following states: Replication 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
Add a remote system connection
Configure a remote system connection between the source and destination systems. A remote system connection is used by
asynchronous replication and/or metro.
Prerequisites
Before creating a remote system connection, ensure that you have obtained the following remote system details:
●
System IP address
●
User authentication credentials for connecting to the system
If you are using jumbo frames, ensure that jumbo frames are configured on both sides of the remote system connection (hosts
and network ports), as well as on all ports between the two storage arrays. MTU size mismatch results in a warning in the
following cases:
●
Configuring a remote system connection.
●
Modifying remote system connection settings.
●
Using the
Verify and update
option.
NOTE:
It is not recommended to change the MTU size of a storage network when a replication session is active. To change
the MTU size:
1.
Pause replication session.
2.
Change MTU the storage network MTU size.
3.
Run
Verify and update
on the remote system to confirm that no warning is issued.
4.
Resume the replication session.
Steps
1.
Select
Protection
>
Remote Systems
.
2.
In the
Remote Systems
window, click
Add
.
3.
In the
Add Remote System
slide-out panel, configure the following:
●
Management IP address
●
Description (optional)
●
Network latency
●
Username and password
4.
Click
Add
.
Synchronization
PowerStore enables you to asynchronously update the destination resource with changes (such as changes in content, size, and
membership) that occurred on the source resource since the last synchronization cycle.
Synchronization can occur either automatically - according to a set schedule - or manually. Snapshots are synchronized from
the source system to the destination system, and maintain block sharing efficiency.
When a volume on the destination system is mapped to a host, the system sets the node affinity for this volume, and as a result,
all I/Os are automatically directed to the selected node. There is no need to pause and resume the replication session for the
I/O redirection to take effect. Setting node affinity for volumes on the destination system provides load balancing and prevents
latency of replication. You can set the node affinity manually using REST API.
NOTE:
If you cannot see the node affinity column in the Volumes table, add it using the
Show/Hide Table Columns
.
NOTE:
When you add volumes to a volume group or change the size of the volume group during an asynchronous
replication session, the changes do not immediately appear on the destination. You can either perform a manual
synchronization or wait until the synchronization occurs based on the RPO.
For NAS servers, all file systems on a protected NAS server are synchronized from the source to destination system. When file
systems are modified during an asynchronous replication session, the changes are reflected on the destination system at the
next synchronization cycle.
You can synchronize a replication session when it is in the following states:
Replication
21