Question 590
At the Highbridge consumer platforms infrastructure team, a newly created SnapMirror relationship remains uninitialized and no recoverable baseline copy exists. Which issue should the team identify as the primary cause?
Explanation
Correct Answer
This identifies the root issue: configuring peer metadata alone does not transfer the initial volume dataset to the destination. At the Highbridge consumer platforms infrastructure team, the team should therefore perform the supported baseline initialization of the source-to-destination relationship.
Incorrect Answers
“Replication optimized for recent DR does not automatically retain the full audit history” is not the controlling explanation for at the Highbridge consumer platforms infrastructure team, a newly created SnapMirror relationship remains uninitialized and no recoverable baseline copy exists. The cited causal relationship is configuring peer metadata alone does not transfer the initial volume dataset to the destination; a passing acceptance check would show that the destination contains an initialized baseline and subsequent updates can run. The matching answer is “Configuring peer metadata alone does not transfer the initial volume dataset to the destination”.
The proposed cause is relevant to high availability versus disaster recovery, but it does not explain why configuring peer metadata alone does not transfer the initial volume dataset to the destination in the reported case. For the Highbridge consumer platforms infrastructure team, the direct corrective action is to perform the supported baseline initialization of the source-to-destination relationship.
After a failover the active data copy and replication direction may differ from the original relationship. That is not the mechanism that accounts for the stated failure at the Highbridge consumer platforms infrastructure team.