Hi
- What, if any, things do you try to accomplish when creating snapshot schedules and protection policies?
Depends on the application, business requirement, RPO, legal requirements etc.
- Is there any concerns with controller saturation when kicking off multiple volume snapshots at once? If so how do you combat this?
Yes, there can be a CPU impact so it's best to stagger snapshots and snapmirror/vault updates if possible. The general recommendation is to avoid taking snapshots on the hour, as DataONTAP does a lot of internal processing around that time. I try to schedule my daily snapshots to be 00:05 or 00:10. Also try to avoid de-duplication jobs, if any. It's best to schedule de-dupe jobs and then snapshot after they complete in my experience.
- Are there any best practice documents available?
The SnapVault best practice guide is pretty old (2012), I'm not aware of a newer one but the principles are similar: http://www.netapp.com/us/media/tr-3487.pdf .Also check out the DataONTAP documentation for the version you are running. This is the Data Protection Guide for cDOT 8.2.1 https://library.netapp.com/ecm/ecm_download_file/ECMP1366833
Cheers
G