Microsoft Hyper-V provides the ability to store VM files on SMB3 file shares. Veeam Backup & Replication works with both standalone and clustered SMB3 servers. It supports VMs whose VM disks are located on SMB3 shares and lets you perform backup, replication and file copy operations for such VMs without taking VMs offline.
The procedure of backup depends on the Microsoft Hyper-V Server version:
In general, VM quiescence and backup or replication of VMs on SMB3 shares is similar to backup or replication of VMs hosted on local storage and CSV. However, SMB3 brings in some specifics.
If you want to work with SMB3 shares in Veeam Backup & Replication, the backup infrastructure must meet the following requirements:
- SMB3 shares must be properly configured. For a full list of requirements for SMB3 shares, see the Requirements and supported configurations section at http://technet.microsoft.com/en-us/library/jj612865.aspx.
- An SMB3 server or SMB3 cluster hosting the necessary file shares must be added to the backup infrastructure. Otherwise Veeam Backup & Replication will not be able to use changed block tracking for VMs residing on SMB3 shares.
- VMs must not be located on hidden shares or default shares like C$ or D$. When re-scanning SMB v3 file shares, Veeam Backup & Replication skips these types of shares.
For backup of VMs registered on Microsoft Hyper-V Server 2016, Veeam Backup & Replication uses a new mechanism based on production checkpoints. For more information, see Backup of VMs on Microsoft Hyper-V Server 2016.
If you plan to process VMs whose disks reside on SMB3 shared folders are registered on Microsoft Hyper-V Server 2016, you do not obligatory need to add the Microsoft SMB3 server to the backup infrastructure. Note, however, that if you do not add the Microsoft SMB3 server, you will not be able to specify the Max snapshots and latency control settings for SMB3 shared folders. For more information, see Adding Microsoft SMB3 Servers.