Name
|
Indicates the name of the protected group.
|
Protection Policy
|
Indicates the protection policy of the protected group.
|
Production Site
|
Indicates the site where the protected objects in the group reside (the protected site). Service systems of enterprises are running on the site.
|
DR Site
|
Indicates the site running the DR system. This site provides DR backup services for the protected objects. If a disaster occurs, it can be used to recover services.
|
Protected Object Type
|
Indicates the types of the protected objects. eReplication enables you to create protected groups based on the following applications:
- Oracle
- IBM DB2
- Microsoft SQL Server
- Microsoft Exchange Server
- Local File system
- NAS File System
- VMware VM
- LUN
- FusionCompute VM
- SAP HANA
|
Configured RPO
|
- If the protection policy type is synchronous replication (SAN), or HyperMetro (SAN), the expected recovery point objective (RPO) is 0 by default.
- If the policy template type of a protected group is asynchronous replication, the RPO of the protected group is configured as follows:
- If the protection policy is Period-based scheduling, you can specify the expected RPO manually. If none is specified, the expected RPO is --.
- If the protection policy is On-demand scheduling, the expected RPO is --.
|
Actual RPO
|
- When the replication devicea is online and the protected group is valid:
- If the protection policy type of a protected group is synchronous replication (SAN), or HyperMetro (SAN):
- If synchronization status is normal, the actual RPO is 0.
- If synchronization status is abnormal, the actual RPO is --.
- If synchronization status is synchronizing and data is consistent, the actual RPO is 0.
- If synchronization status is normal, the actual RPO is 0.
- If synchronization status is abnormal, the actual RPO is --.
- If synchronization status is synchronizing and data is consistent, the actual RPO is 0.
- If the protection policy type of a protected group is asynchronous replication (SAN), backup (SAN), backup (NAS), or clone (SAN):
- If the protection policy is Period-based scheduling, a snapshot protected group has multiple copies. If all copies are inactivated or invalid, the actual RPO is --.
- If the protection policy is Period-based scheduling, and the start time of the last copy activation can be obtained, the actual RPO is the time difference between the current system time and start time of the last copy activation.
- If the protection policy is Period-based scheduling, and no protected group is executed successfully, the actual RPO is --.
- If the protection policy is On-demand scheduling and RPO statistics is not supported, the actual RPO is --.
- If the replication device is online but the protected group is invalid, RPO statistics is not supported and the actual RPO is --.
- If the replication device is offline, the actual RPO is --.
|
Estimated RTO
|
When the replication device is online and the protected group is valid:
- If the protection policy type of a protected group is asynchronous replication (SAN), or HyperMetro (SAN), RTO statistics is not supported. Therefore, the estimated RTO is --, an invalid value.
- If the protection policy type of a protected group is asynchronous replication (SAN), backup (SAN), backup (NAS), the RTO is supported only when recovery plans are created and tested. Calculate the average value based on a maximum of 50 successful test records. The calculated result is used as the estimated RTO. If reprotection is performed for recovery plans. Calculate the average value based on the latest 50 successful test records.
|
Execution Result
|
Indicates the execution result of the protected group.
NOTE: For example, the shows in the Execution Result list, means succeed 21 times, and failed 11 time.
|
a: Replication device indicates the storage device in array-based replication DR.
|