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

Replication, Remote systems

Page 20 highlights

4 Replication This chapter contains the following information: Topics: • Remote systems • Synchronization • Failover • Virtual volumes replication Remote systems Both remote replication and metro protection require a remote system connection between two PowerStore systems. In PowerStore, the remote system connection is associated with the replication rule. You can create a remote system connection before configuring remote replication. If you are using PowerStore manager, you can create a remote system connection while creating a replication rule. It is also possible to create a remote system when configuring metro on a volume. It is possible to create a remote connection between systems running different versions (1.x, 2.x, 3.x). The systems versions determine the supported capabilities. It is required that both systems run a PowerStore version for a capability that is included in this version to be supported. The following conditions should be met for replication of storage objects: ● Volume replication ○ The paired systems must run version 1.x or later. ● File replication ○ The paired systems must run version 3.x or later. ○ Connection type - TCP ● Virtual volumes replication ○ The paired systems must run version 3.x or later. ○ Connection type - TCP ● Metro ○ The paired systems must run version 3.x or later. ○ Connection type - TCP (see Metro pre-requisites and limitations) ○ Network latency - Low The Remote Systems table (under Protection) displays the configured remote system connections. In the Remote Systems table you can: ● View remote systems information - You can see the name and IP of the remote system, supported capabilities (visible only if supported by both systems), and data connection status. The detailed view provides IP connectivity status for all initiators. ● Click a remote system to modify its attributes. You can change the description and network latency of a remote system connection. ● Select a remote system and click Delete to remove it. You cannot delete a remote system in the following instances: ○ When there are active replication sessions. ○ When there is a replication rule that is associated with the remote system. ○ When there are Metro volumes ● Select a remote system and click More Actions > Verify and Update to verify and update the connection to the remote system. Verify and update detects changes in the local and remote systems and reestablishes data connections, while also taking the Challenge Handshake Authentication Protocol (CHAP) settings into account. ● Monitor the management and data connection status for troubleshooting purposes. 20 Replication

  • 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

Replication
This chapter contains the following information:
Topics:
Remote systems
Synchronization
Failover
Virtual volumes replication
Remote systems
Both remote replication and metro protection require a remote system connection between two PowerStore systems. In
PowerStore, the remote system connection is associated with the replication rule. You can create a remote system connection
before configuring remote replication. If you are using PowerStore manager, you can create a remote system connection while
creating a replication rule. It is also possible to create a remote system when configuring metro on a volume.
It is possible to create a remote connection between systems running different versions (1.x, 2.x, 3.x). The systems versions
determine the supported capabilities. It is required that both systems run a PowerStore version for a capability that is included in
this version to be supported. The following conditions should be met for replication of storage objects:
Volume replication
The paired systems must run version 1.x or later.
File replication
The paired systems must run version 3.x or later.
Connection type - TCP
Virtual volumes replication
The paired systems must run version 3.x or later.
Connection type - TCP
Metro
The paired systems must run version 3.x or later.
Connection type - TCP (see
Metro pre-requisites and limitations
)
Network latency - Low
The Remote Systems table (under
Protection
) displays the configured remote system connections. In the Remote Systems
table you can:
View remote systems information - You can see the name and IP of the remote system, supported capabilities (visible only if
supported by both systems), and data connection status. The detailed view provides IP connectivity status for all initiators.
Click a remote system to modify its attributes. You can change the description and network latency of a remote system
connection.
Select a remote system and click
Delete
to remove it. You cannot delete a remote system in the following instances:
When there are active replication sessions.
When there is a replication rule that is associated with the remote system.
When there are Metro volumes
Select a remote system and click
More Actions
>
Verify and Update
to verify and update the connection to the remote
system. Verify and update detects changes in the local and remote systems and reestablishes data connections, while also
taking the Challenge Handshake Authentication Protocol (CHAP) settings into account.
Monitor the management and data connection status for troubleshooting purposes.
4
20
Replication