Veeam Backup & Replication v9 with NetApp

With Veeam Backup & Replication v8 the datacenter availability reached a new level as NetApp integration was added to improve the RPO and RTO requirements in the modern data center. With version 9 (GA since today, 12/01/2016) the integration will become even bigger. In this blog post you will see the major new features v9 delivers regarding the integration with NetApp.

Use of Storage Snapshots for Better RPO
Typically administrators schedule consistent backups not more often than 1 to 4 times a day. To achieve a better RPO, backup administrators can integrate Veeam Backup & Replication with NetApp storage systems and take storage snapshots together with Veeam backups. Storage snapshots produce little impact on storage systems and can be created in seconds. Because of that, backup administrators can schedule them as often as they want, maybe once per hour — or even more frequently.


Veeam Backup & Replication offers three technologies that leverage NetApp storage snapshots: Backup from Storage Snapshots, Veeam Explorer for Storage Snapshots and OnDemand SandBox for Storage SnapShots.

Backup from Storage Snapshots
To capture the VM state at a specific point in time, Veeam Backup & Replication leverages VMware vSphere snapshots. However, VMware vSphere snapshots can impact the VM performance while they are in an open state. At the end of the backup operation, the snapshot must be committed and this process can produce a serious burden on the storage and can take much time — sometimes hours or even days.

To reduce the impact of the snapshot commit on the production environment, Veeam Backup & Replication offers Backup from Storage Snapshots. With NetApp snapshots integration Veeam Backup & Replication leverages the performance and efficiency benefits of NetApp snapshots by creating an application consistent VM snapshot in VMware followed by a snapshot in the volume level. Right after that the VMware snapshot will be deleted as a consistent state is now present on the NetApp volume snapshot. Since the VM runs on the VMware snapshot only for a short moment of time, VMware vSphere needs to commit less data, and the commit process is nearly instant. The NetApp snapshot is now the source for Veeam Backup & Replication to back up the data from.


NEW in v9: In version 8 Backup from Storage Snapshots was announced with capabilities to back up from the primary NetApp ONTAP system. With version 9 you will have the possibility to backup either from primary or secondary NetApp ONTAP systems. This will allow you to reduce the load and performance overhead in the primary NetApp ONTAP system by leveraging a secondary with active SnapVault or SnapMirror relationship.

Veeam Explorer for Storage Snapshots
If a disaster strikes, the administrators can leverage Veeam Explorer for Storage Snapshots to restore VM data directly from NetApp storage snapshots. It does not matter if the snapshot is created by Veeam, NetApp or a 3rd party software. The snapshot can reside on the NetApp primary or secondary ONTAP system by leveraging SnapVault or SnapMirror, can be crash-consistent or application-consistent.


Veeam Explorer for Storage Snapshots comes with all editions of Veeam Backup & Replication, including Veeam Backup Free Edition, and provides the following restore options:

  • Instant VM Recover
  • File-level recovery (Microsoft Windows/Linux/Unix)
  • Application items recovery (Note that features may vary in the different editions)

NEW in v9: For v9 a Veeam Explorer for Oracle will be available. The Oracle integration provides you with the capability to use Veeam Backup & Replication for creating agentless, application-consistent NetApp storage snapshots for both Microsoft and Linux Oracle VMs. The new explorer can be used to restore Oracle databases directly out of NetApp storage Snapshots.

NEW in v9: OnDemand Sandbox for Storage Snapshots
Versions ago we added the features SureBackup and Virtual Lab to Veeam Backup & Replication. With these two you are able to verify and leverage your backup data within your environment by using the Veeam Backup & Replication repository as a source for booting up a dedicated lab in within your hypervisor. With version 9 the feature OnDemand Sandbox for Storage Snapshots will provide you the capability to easily boot up a Virtual Lab directly from the NetApp storage snapshot. This Virtual Lab can be used for Test and Development or even to verify if the data is restorable in case of a disaster.

OnDemand Sandbox

By using NetApp storage snapshot there is no real limitation in the amount of VMs you can boot up and you can leverage the full performance of the NetApp ONTAP system. And as the NetApp snapshots are very efficient and not influencing the storage performance you won’t run into these kind of problems.

Veeam + NetApp = An Enterprise ready combination
Using both Veeam & NetApp in your modern data center will give you the maximum on flexibility, availability and efficiency. The combination of NetApp efficient and performant Snapshot technology and advanced Backup & Restore capabilities of Veeam will get you a solution which fits in almost every requirements today. As data loss and downtime is today no more an , it is required to think about the new way right now.


Combining primary and secondary NetApp ONTAP systems with Veeam Backup & Replication as the centralized orchestration tool will let you flexible react on changed requirements. And using the Backup from Storage Snapshots in combination with tape-out or Veeam Cloud Connect will let you cover the 3-2-1 Data Protection rule in a very easy way.

6 thoughts on “Veeam Backup & Replication v9 with NetApp

  1. Hi Stefan. Nice blog! I’ve been setting up exactly the scenario you show in the last image on this post in my lab, using a QuadStorVTL emulated tape library as my offsite copy. The only thing I can’t figure out is how to do an Instant VM Recovery from SnapVault. Whenever I try I get an error message saying “One or more VMs cannot be restored to the original location, because it is no longer available, or the host has outdated integration components. Please choose different restore mode”. I’ve presented the NFS SnapVault volume to the same host as the source volume and everything else seems to be working. Any ideas what I might be doing wrong?



    • Solved my problem. Firstly, I had to apply Update 2 to fix a known bug. Then, I chose the option to restore to a different location. That allowed me to specify a host when restoring from SnapVault (the option was greyed out before I applied the update.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s