Snapshot-based backups use storage-array snapshots to capture point-in-time copies of VM data with minimal impact on production workloads. In Commvault, this capability is provided through IntelliSnap, which coordinates hypervisors and storage arrays so you can manage snapshot-based protection and restores from a single place.
How snapshot-based backups work
Snapshot-based backups typically follow this flow:
-
A snapshot is created on the storage array for the volume or datastore that hosts the VM data.
-
Commvault catalogs the snapshot so it can be used for restores and for creating backup copies.
-
Optional: A backup copy is created by moving data from the snapshot to backup storage for longer retention, immutability, or air-gapped storage.
Depending on your backup plan configuration, snapshots and backup copies can run independently or as part of the same protection workflow.
When to use snapshot-based backups
Snapshot-based backups are most useful when one or more of the following apply:
-
You need shorter backup windows for large VM environments.
-
You want frequent recovery points without running frequent full data movement backups.
-
You want faster operational recovery for common restore scenarios.
-
You want to layer cyber resilience controls by creating backup copies from snapshots into immutable or isolated storage.
Supported workloads
-
Amazon EC2
-
Azure Virtual Machines
-
Google Compute Engine
-
Microsoft Hyper-V
-
Nutanix AHV
-
VMware vSphere
Requirements
Snapshot-based backups depend on storage and hypervisor capabilities.
Common requirements include:
-
A supported storage array with snapshot capability.
-
Network connectivity and credentials for the storage array and the hypervisor.
-
An access node that can coordinate snapshot operations and, if configured, move data to backup storage.
To configure snapshot-based backups, you typically:
-
Configure storage by adding the array.
-
Add your hypervisor.
-
Create a backup plan.
-
Create a VM group, and enable snap-based backups (which might be labeled IntelliSnap).
-
Associate the backup plan with the VM group.
What to expect
Recovery points
Snapshot-based backups create recovery points on the storage array. Retention is managed by your backup plan settings.
Backup copies and retention
If your backup plan includes backup copies, Commvault creates schedules for snapshot (primary) and backup copies.
When you enable IntelliSnap on a VM group, the associated backup plan is enabled for IntelliSnap and is set to retain eight snap recovery points by default.
You can modify the backup plan to change the number of snapshots retained.
Performance and cost considerations
Snapshot operations are typically fast, but backup copies can still generate network and storage load.
If you protect workloads across multiple regions, plan for egress and placement considerations. See Configure multi-region backups for VMs.
Troubleshooting basics
If snapshot-based backups fail, common causes include:
-
Missing permissions or credentials for the storage array or hypervisor.
-
Unsupported storage array or misconfigured snapshot configuration.
-
Access node connectivity issues to the hypervisor, array, or backup storage.
Start by confirming connectivity and credentials, then review the job details for the component that failed (array operation, hypervisor operation, or backup copy operation).