terse copper
I am sure I'm not the only one who would like the "Retention Count" on the Protection Policy to be replaced with "Snapshot Age" instead?
We do remote backup for customers, so we setup a Protection Policy like shown here... and this works just fine as long as you do not do too many manual started backupjobs, because if you are testing somthing on a datastore and run day 10 test snapshots with the daily snapmirror label, just just "cut off" 10 days wort of snapshots at the "far end"... which most likely isn't what you want... but was is even worse is if you have setup SMVI on a datastore with the daily snapmirror label... then "someone" sets up a SM for SQL up where the databases are located on the same datastore... and if your snapmirror label match the "daily" of the SMVI, just just cut your retention in half or worse of you also have logs there... As far as I know this problem has not yet been addressed ? One could set the rention count to 1024 and write some elaburate snapshot delete script, which just isn't fun to have running... or may you could setup the "SnapLock Rention Period" to 356 days... Which still leaves you with the deletion problem after the 365 days... this could be fixed if NetApp would just introduce an age based rention... But maybe I have missed some other possibilities ?
broken escarp
