Why Information About the Primary Device and Secondary Device in a Remote Replication Relationship Cannot Be Updated in Real Time?
Question
Why information about the primary device and secondary device in a remote replication relationship cannot be updated in real time?
Answer
The symptoms and reasons are as follows:
- Symptom 1
After data synchronization between the primary LUN and the secondary LUN is initiated, the secondary device does not display the synchronization progress in real time.
To display the synchronization progress in real time during data synchronization, the secondary device must send a query task to the primary device. This affects system performance.
- Symptom 2
After the name of the primary device is changed, the name in remote replication is not updated in real time.
The name of the primary device in a remote replication task is obtained by invoking the interface of the system management module rather than using the remote replication module. Therefore, after the device name is changed, remote replication cannot detect the change. In this case, you can refresh the information manually or log in to the DeviceManager again. Then, the name of the primary device will be updated.
To obtain the latest information about the primary device and the secondary device in a timely manner, you can log in to the DeviceManager and click Refresh on the remote replication management page.