Users Guide

Репликация
В этой главе содержится следующая информация:
Темы:
• Remote systems
• Synchronization
• Failover
Remote systems
Configuring a remote system connection between the source and destination systems enables remote replication. In
PowerStore, the remote system connection is associated with the replication rule. You can create a remote system connection
ahead of time, or while creating a replication rule.
NOTE: It is possible to create a remote connection between systems running different versions (1.x, 2.x).
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
To add a remote system connection:
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.
In the Remote Systems table you can:
● View remote systems connection status.
● Click a remote system to modify its attributes. You can change the management cluster IP address, 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:
○ If there are active replication sessions.
○ If there are remote protection policies active in the system associated with the remote system.
○ If there is a replication rule associated with the remote system.
● 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.
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.
4
14 Репликация