Data Protection
Snapshot Policy Strategy for Pure FlashArray
Start With Recovery Objectives
Snapshot schedules should be driven by recovery objectives, not by habit. Before creating or changing a FlashArray protection group, define how much data the workload can lose and how quickly the team must recover it.
The most common mistake is applying one aggressive schedule to every workload. That creates capacity pressure and noisy operations without improving recovery for systems that do not need it.
Use Service Tiers
| Tier | Workload Example | Local Snapshot Frequency | Local Retention | Replication |
|---|---|---|---|---|
| Critical | Database, ERP | 15 minutes | 24-48 hours | Yes |
| Standard | App servers | Hourly | 2-7 days | Maybe |
| Low | Dev/test | Daily | 3-7 days | No |
| Archive | Monthly reference | Monthly | 12 months | Optional |
This matrix gives application owners something concrete to approve. It also prevents the storage team from making business decisions alone.
Watch Capacity Behavior
Snapshots are space-efficient, but they are not free. High-change databases, batch loads, encryption changes, and file churn can all increase retained snapshot data.
Track these signals:
- Volume or protection group data reduction trends.
- Snapshot space growth after large application changes.
- Retention periods that outlive the stated recovery objective.
- Replicated snapshot lag or transfer failures.
Test From Snapshots
A snapshot policy is incomplete until it has been used in a restore test. At minimum, clone a representative volume, mount it in an isolated location, validate permissions or application startup, and record the elapsed recovery time.
Common Mistakes
- Keeping too many short-interval snapshots after the useful rollback window has passed.
- Replicating every workload without a business-approved DR objective.
- Forgetting to monitor snapshot growth during application migrations.
- Assuming snapshots replace backups. They are fast rollback points, not a full backup strategy by themselves.
Operational Standard
Review snapshot policies quarterly. Confirm that each protection group still has a current owner, stated recovery objective, retention period, and restore test date.