Failure of Sites A and B
This section describes how the DR Star trio handles the failure of sites A and B and how it restores to the original state before the failure.
DR Mechanism
- On the storage system at site C, split the asynchronous remote replication relationship between sites A and C.
This operation may fail if the storage system at site A is faulty. Failure of this operation does not affect subsequent operations.
- On the DR Star Trios page, choose More > Disable Write Protection for Third Site.
- Map the secondary LUN of asynchronous remote replication to the host. Site C takes over services.
Restoration
- After sites A and B recover, check whether the asynchronous remote replication relationship between sites A and C is split. If yes, go to the next step. If no, split remote replication before going to the next step.
- Perform a primary/secondary switchover between sites A and C.
Before the switchover, site A is the primary site and site C is the secondary site. After the switchover, site A is the secondary site and site C is the primary site.
- Suspend the HyperMetro relationship between sites A and B (Stop the host services at site B).
- Set the secondary resource to read-only (select Enable Protection for Secondary Resource) for asynchronous remote replication between sites A and C.
- Synchronize data from site C to site A.
- After the synchronization, remove the mapping between the host and the storage system at site C.
- Manually start incremental synchronization from site C to site A to ensure data consistency.
- Split the asynchronous remote replication relationship between sites A and C.
- Set the secondary resource to readable and writeable (select Disable Protection for Secondary Resource) for asynchronous remote replication between sites A and C.
- On the storage system at site A, perform a primary/secondary switchover for asynchronous remote replication between sites A and C.
Before the switchover, site A is the secondary site and site C is the primary site. After the switchover, site A is the primary site and site C is the secondary site.
- Set the secondary resource to read-only (select Enable Protection for Secondary Resource) for asynchronous remote replication between sites A and C, and that between sites B and C.
- Start synchronization.
Data is synchronized from site A to site C. After synchronization, the running status returns to normal.
- Run services on the production host at site A.
- Start HyperMetro synchronization between sites A and B.