Looking for some information as to how MirrorVault works. Running a lab with source running 9.2 and destination running 9.5. What we are trying to find is a way around the 1019 max snapshots. The source is snapping every 5 mins. The policy is MirrorandVault with 2 rules setup. Rule one is sm_created with options to keep 1 and preserve false. Rule 2 is called Test and is set to every 5 mins. Keep is 300 and preserve is True. The intent of this is to try to keep all the snapshots sent to the destination. The first test we ran, we kept 1019 with preserve true. Once we hit 1020 snapshots, snapmirror failed but kept all the snapshots from before. We changed the test to the current 1 and 300 but the results were confusing. Snapshots at the destination stopped at 360 snapshots and stopped updating (last snapshot recorded was 2301 on 28 Feb. On the source, .snapshot folder showed 254 (limits of 9.2) snapshots but had all of todays snapshots (4 Mar) with snapmirror showing all transferred successful. Just trying to figure out how preserve is supposed to work and find out if even with snapvault, we are limited to 1019 total snapshots. How do you do long term vaulting or indefinite vaulting if the snapshot count is limited. I know you can copy the snapshots to another directory, but looking for an automated process within Ontap that would do it for you. How would this work with fabric pools? Fabric pools would tier the cold snapshots to another storage source, but will you still be limited to 1019 (possibly 4k snapshots at 9.6/9.7)? Hoping to find an SME who can help out and would be willing to assist in the testing.
↧