No Daily or Weekly snapshots availabe on the destination

[Besi]

I recently created three Storage VMs for disaster recovery (DR) and applied the Asynchronous protection policy. On two of the SVM DRs, I can only see hourly snapshots, kept for 1 hour, but no daily or weekly snapshots. However, my test SVM DR shows hourly and daily snapshots retained for 7 days.

I'm unsure why the daily and weekly snapshots are not appearing for those two SVM DRs. Has anyone else encountered this issue? I’d appreciate any insights into what might be causing this.

[Sergey_Osipov]

check how the snapmirror policy attached to the relationship is configured

::>snapmirror show -destiantion-path "path" -fields policy
::>snapmirror policy show -policy <name from the previous output> -instance

[Besi]

Here’s how the SnapMirror policy relationship is configured. I changed the weekly retention to 4 weeks, as we don’t need to keep 52 weeks by default for this small environment.

cluster1::> snapmirror show -destination-path svm_cifs01_bk: -fields policy
source-path destination-path policy
----------- ---------------- ------------
svm_cifs01: svm_cifs01_bk: Asynchronous

luster1::> snapmirror policy show -policy Asynchronous -instance

Vserver: cluster1
SnapMirror Policy Name: Asynchronous
SnapMirror Policy Type: mirror-vault
Policy Owner: cluster-admin
Tries Limit: 8
Transfer Priority: normal
Ignore accesstime Enabled: false
Transfer Restartability: always
Network Compression Enabled: false
Create Snapshot: true
Comment: A unified Asynchronous SnapMirror and SnapVault policy for mirroring the latest active file system and daily and weekly Snapshot copies with an hourly transfer schedule.
Total Number of Rules: 3
Total Keep: 12
Transfer Schedule Name: hourly
Throttle: unlimited

Rules:
SnapMirror Label Keep Preserve Warn Schedule Prefix Retention Period
---------------------- ---- -------- ---- -------- ---------- ----------------
sm_created 1 false 0 - - -
daily 7 false 0 - - -
weekly 4 false 0 - - -

[Sergey_Osipov]

okay so now check on the source cluster

::>vol show -vserver <source SVM> -volume * -fields snapshot-policy
then check how snapshot policies are configured
::>volume snapshot policy <name of the snapshot poplicy> show -instance

the required snapshot policies should be in  charge of creating local snapshots with required snapmirror-labels
daily and weekly
please bear in mind these labels are case sensitive 

daily is NOT equal Daily

in general snapmirror vault or mirror-vault works in way of checking the new source volume's snapshots with required labels, if exists it replicates them
and attaching a snapmirror-label to a snapshot on a source side is part of snapshot policy job

[Besi]

Here are some of the volumes; there are quite a few, and some have different snapshot policies applied. I selected three volumes, each with a different snapshot policy. Just so you know, we created SVMDR, which automatically snapmirrors the volumes once you set it up.

cluster::> vol show -vserver svm_cifs01 -volume * -fields snapshot-policy
vserver volume snapshot-policy
----------             ------------------      ---------------
svm_cifs01      cifs_vol1               dept_shares_snapshot_policy
svm_cifs01     cifs_home             home_drive_snapshot_policy
svm_cifs01     cifs_vol3                daily_seven

cluster::> volume snapshot policy show -vserver svm_cifs01 -policy dept_shares_snapshot_policy

Vserver: svm_cifs01
Snapshot Policy Name: dept_shares_snapshot_policy
Snapshot Policy Enabled: true
Policy Owner: vserver-admin
Comment: -
Total Number of Schedules: 3
Schedule Count Prefix SnapMirror Label
---------------------- ----- --------------------- -------------------
weekly_25_past_1 26 weekly_25_past_1 dept_weekly
hourly_25_past_hour 130 hourly_25_past_hour dept_hourly
daily_25_past_1 90 daily_25_past_1 dept_daily

cluster::> volume snapshot policy show -vserver svm_cifs01 -policy daily_seven

Vserver: svm_cifs01
Snapshot Policy Name: daily_seven
Snapshot Policy Enabled: true
Policy Owner: vserver-admin
Comment: -
Total Number of Schedules: 1
Schedule Count Prefix SnapMirror Label
---------------------- ----- --------------------- -------------------
daily_seven 30 daily_seven daily

[Sergey_Osipov · Accepted solution]

as you can see

the local snapshot policy on a source from the example

cluster::> volume snapshot policy show -vserver svm_cifs01 -policy dept_shares_snapshot_policy

Vserver: svm_cifs01
Snapshot Policy Name: dept_shares_snapshot_policy
Snapshot Policy Enabled: true
Policy Owner: vserver-admin
Comment: -
Total Number of Schedules: 3
Schedule Count Prefix SnapMirror Label
---------------------- ----- --------------------- -------------------
weekly_25_past_1 26 weekly_25_past_1 dept_weekly
hourly_25_past_hour 130 hourly_25_past_hour dept_hourly
daily_25_past_1 90 daily_25_past_1 dept_daily

creates local snapshots with snapmirror labels

dept_weekly

dept_hourly

dept_daily

however your SVM DR snapmirror policy
is looking to replicate snapshots with labels

daily 
weekly 

As they don't match - there is nothing to replicate for the system 😃

Adjust either snapmirror policy on a destination to necessary labels
or snashot policies on a source
Please keep in mind that all volumes within the source SVM shall have matching labels to snapmirror policy on a destination as it is SVM DR

we have many KBs describing the same
https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/SnapMirror_updates_are_not_sending_snapshots_if_the_label_isn't_in_the_Policy

https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_create_a_Snapmirror_vault_with_monthly_snapshots

https://kb.netapp.com/on-prem/ontap/DP/SnapMirror/SnapMirror-KBs/How_to_configure_the_retention_of_Snapshots_on_SnapMirror_destination