You have created a SnapMirror relationship from your production volume serving SMB/CIFS data to your DR cluster. After two days of updates, you do not see any of the expected snapshots on the…

The correct answer is D. The SnapMirror label is missing from the snapshot policy on the secondary volume. SnapMirror replication is driven by labels that match between the snapshot policy on the source volume and the SnapMirror policy. If the snapshot policy on the source does not include the correct SnapMirror label, SnapMirror will not recognize which snapshots to replicate…

Data Protection Solutions Troubleshooting

Question

You have created a SnapMirror relationship from your production volume serving SMB/CIFS data to your DR cluster. After two days of updates, you do not see any of the expected snapshots on the secondary volume. Why is SnapMirror failing to replicate snapshots?

Options

AThe SnapMirror label is missing from the SnapMirror policy on the secondary volume.
BSnapMirror is not properly licensed.
CSVM peering is not properly configured.
DThe SnapMirror label is missing from the snapshot policy on the secondary volume.

How the community answered

(38 responses)

A
8% (3)
B
16% (6)
C
3% (1)
D
74% (28)

Explanation

SnapMirror replication is driven by labels that match between the snapshot policy on the source volume and the SnapMirror policy. If the snapshot policy on the source does not include the correct SnapMirror label, SnapMirror will not recognize which snapshots to replicate, resulting in

Topics

#SnapMirror replication#snapshot policy#SnapMirror label#SMB/CIFS

Community Discussion

No community discussion yet for this question.

Full NS0-528 Practice