NetApp Certified Implementation Engineer – NFS, ONTAP — Question 7

You have set up SnapMirror relationships between two clusters. SnapMirror shows as unhealthy and fails with the following error:
Reason: 'Transfer failed'. Last Transfer Error Was 'The number of Snapshot copies on destination volume "volume_name" has reached the maximum supported count of <count_set_by_policy>.
When you check the EMS logs, you notice the following:
[NetAppProdVault-01: worker_thread_342: sm.xfer.fail.maxlim.snap:alert]: The number of Snapshot copies on destination volume 'SVM_filer02:vflsystems_sm_4' of the relationship with relationship UUID 'ala620fc-a870-lle9-94ef-00a09893ee91' and policy 'filer02_vault_daily_policy' has reached the maximum supported.
[NetAppProdVault-01: sm_logger_main: smc.snapmir.update.fail:error]: Snapmirror update from source volume 'vol1' to destination volume 'vol2' failed with error 'The number of Snapshot copies on destination volume "vol2" has reached the maximum supported count of <count_set_by_policy>.'. Relationship UUID 'ala620fc-a870-lle9-94ef-00a09893ee91'.
What is the cause of this situation, and how can you avoid this in the future? (Choose two.)

Answer options

• A. Modify the SnapMirror policy's -keep parameter.
• B. The SnapMirror relationship has reached its maximum number of snapshots, which is 1019.
• C. Modify the SnapMirror policy's -snapmirror-label parameter.
• D. The SnapMirror relationship has reached its maximum number of snapshots, which is 255.

Correct answer: A, D

Explanation

The correct answer A suggests modifying the -keep parameter, which controls the number of Snapshot copies retained, thereby preventing reaching the maximum limit. Answer D is also correct as it states that the maximum number of snapshots is 255, which aligns with the reported error. Answers B and C are incorrect because B mentions an incorrect limit of 1019, and C does not address the actual issue of the Snapshot copy limit.