Local Resource |
Name of a local resource. |
Remote Resource |
Name of a remote resource. |
Pair ID |
ID of a remote replication pair. |
Local Resource Role |
Whether a local resource of a remote replication pair is the primary resource. If local resources are primary resources, it displays as Primary. Otherwise, it displays as Secondary. |
Health Status |
Health status of a remote replication pair. Possible values are as follows:
- Normal: The pair is functioning normally. You can perform the synchronization operation.
- Fault: The primary resource or secondary resource of the pair malfunctions or the replication link is down. Therefore, you cannot perform the synchronization operation.
|
Running Status |
Running status of a remote replication pair. Possible values are as follows:
- Unknown: The system fails the query.
- Normal: indicates that the data synchronization of the pair is completed successfully.
- Synchronizing: indicates that the data of the pair is being synchronized.
- Split: indicates that the pair is in the split status, and the synchronization is suspended.
- Interrupted: indicates that the remote replication internal I/O error or the replication link is down, and you cannot perform the synchronization operation temporarily.
- To be recovered: indicates that after the faulty internal I/Os of the remote replication are rectified or the replication link is up, and if Recovery Policy is Manual, the pair is to be recovered. You need to manually start data synchronization for the pairs.
- Invalid: indicates that the pair is unusable and cannot be restored in this status, except deleting it. You must delete the pair on both primary and secondary storage devices. Otherwise, the pair creation may fail.
|
Remote Replication Consistency Group ID |
ID of a remote replication consistency group. |
Added to Remote Replication Consistency Group |
Whether to add a remote replication pair to a remote replication consistency group. |
Replication Mode |
Data replication mode.
- Asynchronous: After data is written to the primary resource successfully, the host receives a write success response. At the same time, the primary site records differences between the written data and the secondary resource data. Then the changed data recorded by the primary site is synchronized to the secondary site, minimizing the write latency for foreground applications.
- Synchronous: When data is written to the primary resource, the write request is also sent to the secondary resource. The host receives a write success message only after the data is written to both primary and secondary resources successfully, ensuring that data on the primary resource and secondary resource is synchronized in real time.
|
Secondary Resource Data Status |
Status of a secondary resource. Possible values are as follows:
- Consistent: Data on the secondary resource is a copy of the data on the primary resource (at the time when the latest successful synchronization starts). At this time, data on the secondary resource is available but not necessarily the same as the current data on 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 state, data in the secondary resource is unavailable. You can synchronize the data to ensure data consistency between primary and secondary resources.
- Synchronized: Data has been synchronized between primary and secondary resources. This value is available only for synchronous remote replication. For asynchronous remote replication, after data is synchronized between primary and secondary resources, the value is Consistent.
|
Secondary Resource Protection |
Protection status of a secondary resource. Once the protection for the secondary resource in a remote replication pair is enabled, the application server cannot modify the data on the secondary resource. Therefore, you can ensure the security of the data on the secondary resource. |