Viewing Remote Replication Pairs

Context

• On the remote replication pair management page, click to refresh remote replication pairs.
• On the remote replication pair management page, click or next to a parameter and enter a keyword or select a parameter value to search for desired remote replication pairs.
• On the remote replication pair management page, click and select desired remote replication pair parameters to be viewed.

Procedure

1. Choose Data Protection > Protection Entity > Dtree > Remote Replication Pair.
2. Select a desired account from the Account drop-down list in the upper left corner.
3. Optional: Select a namespace to which dtrees belong from the Owning Namespace drop-down list. You can view the remote replication information of the dtrees in the namespace in the list below.
4. View information about existing remote replication pairs. Table 1 describes related parameters.

   Table 1 Remote replication pair parameters

   Parameter	Description
   Local Resource	Name of a local resource.
   Remote Resource	Name of a remote resource.
   ID	ID of a remote replication pair.
   Remote Device Name	Name of a remote device.
   Remote Device ESN	ESN of a remote device.
   Local Resource Role	Whether the local resource of a remote replication pair is the primary resource. If the local resource is the primary resource, Primary is displayed. Otherwise, Secondary is displayed.
   Health Status	Health status of a remote replication pair. The value can be: Normal: The pair is functioning normally. You can perform data synchronization. Fault: The primary or secondary resource of the pair malfunctions or the replication link is down. You cannot perform data synchronization.
   Running Status	Running status of a remote replication pair. The value can be: Normal: Data synchronization has been completed for the pair. Synchronizing: Data is being synchronized for the pair. Split: The pair is in the split status, and data synchronization is suspended. Interrupted: An internal I/O error occurs or or the replication link is down. Data cannot be synchronized for the pair temporarily. To be recovered: When Recovery Policy is set to Manual, the pair enters this status after the internal I/O error of remote replication is rectified or the replication link is up. In this case, you need to manually start data synchronization for the pair. Invalid: The pair is unavailable and cannot be restored, except being deleted. You must delete the pair on both the primary and secondary ends. Otherwise, subsequent pair creation may fail.
   Replication Mode	Data replication mode. Async: After data is written to the primary resource of a pair successfully, the host receives a write success response. At the same time, the primary site records the difference between the data so written and that in the secondary resource. Then, the data difference recorded by the primary site is synchronized to the secondary site, minimizing the write latency for foreground applications.
   Recovery Policy	Whether a remote replication pair automatically synchronizes data after an internal I/O error of remote replication is rectified or the replication link is up. The default value is Automatic. [Value range] Automatic: The system automatically synchronizes data. The pair enters the Synchronizing state. Manual: Data must be synchronized manually. The pair enters the To be recovered state.
   Speed	Data synchronization speed of a remote replication pair. The value ranges from 1 MB/s to 10,240 MB/s (or 1024 KB/s to 10,485,760 KB/s).
   Sync Type	Data synchronization mode of the primary and secondary resources of a pair. The value can be: Manual: Data must be manually synchronized between the primary and secondary resources. Timed wait after sync begins: The system starts timing as soon as the latest synchronization begins. After the time specified in Interval is reached, the system automatically starts data synchronization between the primary and secondary resources again. NOTE: If the last synchronization has not finished after the time specified in Interval is reached, the system performs the next synchronization after the last synchronization finishes. Timed wait after sync ends: The system starts timing after the last synchronization finishes. After the time specified in Interval is reached, the system automatically starts data synchronization between the primary and secondary resources again. Specific time policy: The system automatically synchronizes data between the primary and secondary resources based on a specific time policy.
   Interval	Synchronization interval for Timed wait after sync begins and Timed wait after sync ends. NOTE: This parameter is available only when Sync Type is set to Timed wait after sync begins or Timed wait after sync ends.
   Time Policy	Specific time policy: The system automatically synchronizes data between the primary and secondary resources based on a specific time policy. NOTE: This parameter is available only when Sync Type is set to Specific time policy.
   Primary Resource Data Status	Status of data in a primary resource. Data in the primary resource is always in the Consistent status.
   Secondary Resource Data Status	Status of a secondary resource. Consistent: Data in the secondary resource is a copy of the data in the primary resource (at the time when the latest successful synchronization starts). At this time, data in the secondary resource is available but not necessarily the same as the current data in the primary resource. Inconsistent: Data in the secondary resource is not a copy of the data in the primary resource (at the current point in time or at the time when the previous synchronization ends). In this status, data in the secondary resource is unavailable. You can synchronize the data to ensure data consistency between primary and secondary resources.
   Status of Secondary Resource Protection	Protection status of a secondary resource. Read-only: Data in the secondary resource can only be read. Read/Write: Data in the secondary resource can be read and written. Access prohibited: Data in the secondary resource cannot be accessed, ensuring data security of the secondary resource.
   Copy Snapshot Retention in Secondary Resource	Retention policy of copy snapshots. The value can be: Do not retain: No copy snapshot will be created in the secondary resources after pair synchronization. Retain: The system will create a copy snapshot in each secondary resource each time after pair synchronization to capture the data state of the primary resources at the time when pair synchronization begins. NOTE: A copy snapshot created under a copy snapshot retention policy in a secondary resource is a replication snapshot. To view such snapshots, choose Data Protection > Protection Entity > Dtree > Snapshot and filter snapshots by Type on DeviceManager.
   Copy Snapshots Retained in Secondary Resource	Number of copy snapshots retained in the secondary resources. When the number of copy snapshots at the secondary end exceeds the value of this parameter, the system deletes the earliest copy snapshots by default. [Value range] 1 to 512 NOTE: This parameter is available only when Copy Snapshot Retention in Secondary Resource is set to Retain. The name of a copy snapshot is prefixed by rep_copy.