QuestionQ13

Replication

You configured SnapMirror relationships between two clusters. SnapMirror is shown as unhealthy and fails with this 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 checking the EMS logs, you find 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 &lt;count_set_by_policy&gt;.'. Relationship UUID 'ala620fc-a870-lle9-94ef-00a09893ee91'.  

What causes this condition, and how can it be prevented in the future?

Choose two
  • 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.
Explanation

A SnapMirror policy rule’s -keep setting defines how many Snapshot copies are retained on the destination. The combined retention count across all rules in a SnapMirror policy cannot exceed 1019, so a policy that reaches this limit causes further transfers to fail. Adjusting the policy’s -keep retention values prevents the limit from being exceeded.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!