We have several staggered snap policies that have a daily and weekly schedule. The policies are set to different times throughout the day and weekly job is set to Fridays at that time. See example below:
Have seen a similiar case recently, where the cascaded snapmirror->snampvalut setup was retaining 2 snapshot instead of defined "1". The root cause of the issue was that the snapvault was sceduled at the primary, instead of the mirror. Moving the snapvault schedule to the snapmirror destination made the relation like this; primary filer->snapmirrored to ->mirror filer(dest)->snapvault->vault filer(dest), and the problem was resolved. Do you have a similiar environment?
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO. Cannot find the answer you need? No need to open a support case - just CHAT and we’ll handle it for you.
Thanks for the reply. Snapmirror show on the source returns "This table is currently empty" and the destination returns something like this:
Progress Source Destination Mirror Relationship Total Last Path Type Path State Status Progress Healthy Updated ----------- ---- ------------ ------- -------------- --------- ------- -------- SOURCE_FILER:source_volume XDP DEST_FILER:vault_volume Snapmirrored Idle - true -
The protection polciies were created in System Manager at the destination. So the transfers are set to kick off via the destination. All that is configured at the source is the snapshot policy itself. I am wondering if this has to do with us having a snapvault license on the source but no mirror license and both on the destination. Our third party vendor assured us we did not need the mirror license and only the snapvault license even though snapvault technically went away. Let me know if there are any outputs I can share that can help you determine what you are looking for.