Windows Failover Cluster Backup Split into Multiple Jobs

[telnetrix]

We have a windows failover cluster that has multiple disks. One volume represents 60% of the data, and is rarely changed. 2 Volumes are very active and considered high priority for retention and availability, and the remaining 4 volumes can be easily combined.

I have tested cloning the current 1 Job into another, and removing all but 1 volume, and that job works. I would like to have a total of 4 jobs on the same cluster

All Volume level backup.
Guest processing set to vss copy only.

1 - Archived data (60% size)
2 - User Share disks
3 - Other share Disks
4 - OS Only


No job would overlap on the same volume.

Questions:
Is this supported? I know it works in limited testing.
How are concurrent runs handled between 4 jobs?

[vnikiforov]

Hello,

Yes, this is supported. A failover cluster job is a regular agent backup job managed by the backup server, and the same Server-type protected computer can be included in more than one backup job managed by the backup server. Since your jobs don't share volumes, each keeps its own independent backup chain and retention; note that cluster jobs always create a single backup file per cluster rather than per-machine files.

Concurrent runs don't happen: Veeam Agent processes one job at a time, so whichever job starts second waits in the queue until the first completes, as confirmed in this thread. You can also tweak the job start times, if you don't want the high-priority jobs queuing behind the large archive job.