Feature Request - Allow to Process one by one

[TobiasF]

Hi,

It would be usefull to have an option to process only one VM at once.

Why? We backup our Exchange DAG Cluster with veeam B&R and we have huge problems with Failover Clustering if we process 2 VMs of the cluster simultaneously.
A backup job, which processed all 3 DAG Nodes has crashed our Exchange DAG, it was heavy to repair all the databases...

The best way is to process them one by one.
It would be possible to create different Jobs, but that would destroy the benefit of deduplication.

Greetings
Tobias

[Dima P.]

Hello Tobias.

It's possible to setup DAG processing with job chaining: you create a dedicated backup job for every DAG node, schedule first node backup at desired time and for the rest nodes you select 'After this job schedule' option. Take a look at this blog post for more details. Thanks!

[TobiasF]

Hi,

yes I know I can do that, but different backup jobs => no deduplication

[Regnor]

Are there any further VMs in this job? If so, you could change the processing order so that the Exchange VMs don't get processed in order.

There are also some settings which can be adjusted so that the failover cluster is more "snapshot tolerant":
veeam-backup-replication-f2/exchange-20 ... tml#p93106
https://www.veeam.com/kb1744

As a workaround use a proxy or repository which only allows a limited number of parallel tasks.

[TobiasF]

Hi,

no it's just a job for our 3 DAG nodes.
The Workaround with an Backupproxy would be possible, but it's just a workaround.

I think it's not hard to implement a one by one option inside the Backup job configuration for the veeam dev's and in some situations (for all clusterd infrastructures) it's very usefull to prevent failover actions.
Thats why I opened this thread