SnapCenter SQL Instance-Level Backups Trigger Unintended Storage Snapshots
Applies to
- NetApp SnapCenter Server (6.x and later)
- SnapCenter Plug-in for Microsoft SQL Server
- Virtualized SQL Server environments (VMware vSphere)
- SQL Server instances where:
- User databases reside on dedicated SAN/NAS data volumes (iSCSI / FC / NFS)
- System databases (master, model, msdb) reside on the OS drive (for example, C: or D:)
Issue
When SnapCenter is configured to protect SQL Server at the instance level, backup jobs may create storage snapshots not only on the intended database data volumes, but also on storage backing the virtual machine OS/system drive.
This behavior can result in:
- Duplicate backup snapshots
- Unintended snapshots on shared datastores
- Increased snapshot count and avoidable storage consumption
A single SnapCenter instance-level SQL backup may result in snapshots on ONTAP volumes:
- ✅ SQL user database volumes (expected)
- ✅ SQL log volumes (expected)
- ❌ Shared VM datastore hosting the OS/system drive (unexpected from a database-backup perspective)
Impact:
- Shared VMware datastores may experience rapid capacity utilization growth due to database-driven snapshots
- Risk of datastore capacity exhaustion affecting unrelated virtual machines
- Increased snapshot management and cleanup overhead
