Hello, everyone,
Now, let's talk about the conditions for the secondary LUN of HyperReplication/A to be writable.
By default, the secondary LUN of an asynchronous remote replication pair is read-only. The secondary LUN of an asynchronous remote replication pair can be set to writable only when the following two conditions are met:
The remote replication pair is in the split or interrupted state.
Data on the secondary LUN is consistent after initial synchronization. When data on the secondary LUN is inconsistent, the data is unavailable, and the secondary LUN cannot be set to writable.
If the secondary LUN of an asynchronous remote replication pair is set to writable and the previous data synchronization is not complete, a rollback will be triggered to roll the data on the secondary LUN back to the latest available data.
OceanStor Dorado storage systems can record the differences between the primary and secondary LUNs after host data is written to the secondary LUN. After the production storage system at the primary site recovers, users can perform incremental synchronization to quickly switch back services.

