from Storage Snapshots
|Backup from Storage Snapshots
with Snapshot Retention
|Veeam Explorer for
for Storage Snapshots
|primary Snapshot Orchestration||secondary SNAPSHOT ORCHESTRATION
|Cisco||HyperFlex||Learn more about: Backup from Cisco HyperFlex Snapshots|
||Unity, VNX, VNXe|
|Fujitsu||ETERNUS DX and AF Series*|
|ETERNUS HX and AX Series||***|
|Hewlett Packard Enterprise
||Spectrum Virtualize, IBM FlashSystem Family, SVC
||FAS and AFF Series||***|
|HCI and SolidFire*
|Nutanix||AHV||Learn more about: Nutanix AHV Snapshots|
* Requires a separate plug-in download
** Snapshot creation on peer persistent target
*** Snapshot replication
Note: Any converged infrastructure platform that uses the integrated storage solutions listed above is supported.
Taking VMware vSphere snapshots can significantly slow virtual machine (VM) performance and require considerable effort to meet SLAs.
Veeam improves this process by providing built-in integration with your production storage and leveraging storage snapshot functionality to reduce the impact on the environment from vSphere snapshot removal during backup and replication.
Don’t be stuck with once-a-day backups for I/O intensive workloads—make backups and replicas as often as every 15 minutes!
Storage snapshots can be taken frequently with minimal impact to the production environment, but this can’t be your only backup solution. What if storage itself goes down or gets corrupted? Even with storage-based replication, you need to take your data out of the single-fault domain. This is why many customers prefer to also make true backups stored on different storage.
Veeam combines the best of both worlds with vSphere snapshots for application-consistent backups and storage snapshots for fast RPOs. Now you can:
Read more about our storage snapshot support from the Veeam blog:
Veeam Backup & Replication works with storage providers and VMware to create backups and replicas from storage snapshots. The backup/replica job:
As a result, VMs run off snapshots for the shortest possible time, while jobs obtain data from VM snapshot files preserved in the storage snapshot. Because of this, VM snapshots do not get a chance to grow and can be committed very quickly without overloading production storage with extended merge procedures, as is the case with classic techniques for backing up from VM snapshots.