I find it tedious to do all this in the GUI. The default setting for maximum concurrent snapshots is 4 In a simple example with nothing else in play, this means that 16 tasks can be 4 VMs if those VMs all happen to have 4 disks, etc. By the way, remember that a task does not equal a VM but a disk per VM / backup file per VM. No matter how many concurrent tasks you set on your Hyper-Hosts and repositories. This means that for an S2D or Azure Stack HCI solution for example you will need to increase this value if you want to have more than 4 VM backed up simultaneously on that volume.

That only happens when the Hyper-V recovery checkpoints are the only thing in play. It will not limit the number of concurrent VM backup jobs. When you still use host VSS provider in your backup process (with a SAN hardware VSS provider, combined with off-host Hyper-V proxies) this acts like before. Note that this limitation works only for (recovery) checkpoints created during Veeam Backup & Replication data protection tasks. To change this number, specify the Max snapshots value. You can simultaneously store 4 VM checkpoints on one volume. For Microsoft Hyper-V Server 2016 and later.Many snapshots existing at the same time may cause VM processing failures. It is not recommended that you increase the number of snapshots for slow storage. For Microsoft Hyper-V 2012 R2 and earlier, the default is set to simultaneously store 4 snapshots of one volume.below you will find an excerpt with my annotations.įollow the link for each option to learn more in the on line Veeam documentation. I invite you to read the Veeam documentation on this subject. You see the value of the maximum number of concurrent snapshots doesn’t always result in the same behavior you might expect. The second option’s meaning depends on the version of Windows and also on whether you leverage a hardware VSS provider or not. It does so based on the type of volume and the availability of a hardware VSS provider or not. If you don’t set them manual Veeams scans your host en picks the best option. Hardware VSS providers are only available for volumes that are provided by that storage array. These come from your storage array vendor. You will use the Windows native VSS unless you have a hardware VSS provider installed and configured. But first, let’s remind our selves of what it is used for. I will show how to Set the Hyper-V volume-specific settings in Veeam with PowerShell. Configure the maximum number of concurrent snapshots to allow for the volume.Select what VSS provider to use (Windows native VSS or a Hardware VSS provider).When adding and configuring Hyper-V servers to Veeam you can set the Hyper-V volume-specific settings in Veeam with PowerShell or in the GUI. Set the Hyper-V volume-specific settings in Veeam with PowerShell

W2k19 get back up