Copy job creates two copies from failover cluster backup

[zdenek.s]

Hello,

Briefly, my environment:
Veeam BR 9.5 u4
Repository on Windows Server for backups
Repository on CentOS 7 for copy jobs
Two Windows 2012R2 File servers in failover cluster (Veeam Agents managed by the backup server)

When I back up any File server role, the backup job recognizes which server is currently holding the role and backs up correctly the data.
But the subsequent Backup copy job will make a copy of not one copy, but two.

Example: The backup job starts, detects that server 1 is holding the role, creates a backup named "Server1-xxx.vbk" with a size of 1TB on Windows repository.
However, the backup copy job then creates "Server1-xxx.vbk" and also "Server2-yyy.vbk" on a Linux repository, each of 1TB. So the backups takes up twice the space on this repository.
It does not matter if the Object is added from backups or from jobs.

Other Copy jobs (vmware, agent backups files) works fine, the only problem is with the file server failover cluster.
What should I set up for a copy job to create only one copy of data?


Thanks for the help
Zdenek

[HannesK]

Hello,
and welcome to the forums.

I assume that you have "per-VM backup files" configured for your CentOS repository. In that case, the result of a backup copy job are two independent chains. That is expected behavior.

Best regards,
Hannes

[zdenek.s]

Hello HannesK,

You're right, it was really the per-VM settings.
I thought that this setting only applies to virtual servers, I would not have thought that it will make (for me a little pointlessly) two copies from one original backup in the case of a failover cluster.


Thank you for your help!
Zdenek