from Storage Snapshots
|Backup from Storage Snapshots
with Snapshot Retention
|Veeam Explorer for
for Storage Snapshots
|primary Snapshot Orchestration||secondary SNAPSHOT ORCHESTRATION
||Unity, VNX, VNXe|
|Hewlett Packard Enterprise||3PAR StoreServ||**|
||Spectrum Virtualize, Storwize Family, SAN Volume Controller|
||FAS and AFF Series
* 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 produce a serious burden on virtual machine performance, and it can take considerable effort by administrators to overcome this technical challenge and meet the required SLAs.
Veeam dramatically improves this process, providing built-in integration with your production storage, 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 best of both worlds with vSphere snapshots for application-consistent backups and storage snapshots for fast recovery point objectives. Now you can:
Veeam Backup & Replication works in conjunction with leading storage providers and VMware to create backups and replicas from storage snapshots in the following way. 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 large and can be committed very quickly without overloading production storage with extended merge procedure, as is the case with classic techniques for backing up from VM snapshots.