disable synth full for backup copy

[FrankHa]

We use ReFS Repositories and thanks to Veeams use of block cloning we see very good performance on our synthetic full backups. Great. However, we tried adding a Backup Copy Job to a Versity HSM via NFS. This works great for differential backups, but poorly for full synthetics. How can I tell Veeam to skip full synthetics for backup copy jobs and just copy the VBK files from our ReFS to our Versity HSM instead?

[Mildur]

Hi Frank

A backup copy job does not "just copy the VBK files". The backup copy chains are independently from the source backup chains.

To disable synthetic Fulls in backup copy jobs, you have to use a periodic backup copy job. This job lets you create active fulls instead of synthetic fulls:


Thanks
Fabian

[FrankHa]

Hi Fabian,

thanks for this suggestion. This is something I would have tried already if "Period copy" wasn't grayed out (I don't know why). However, even if this would work, there is a high chance that this would cause an unacceptable high load on the source storage. This is part of the reasoning, why I would like Veeam to just copy the vbk from our ReFS Repository which has currently plenty of idle time it could use for this instead.

[Mildur]

In a backup copy job, the source storage will be the ReFS Repository. The production storage where the VMs are running will not be affected.

This is something I would have tried already if "Period copy" wasn't grayed out

Most likely you created a backup copy job from type immediate. You can‘t switch the job mode after the job was created.

Thanks
Fabian

[FrankHa]

OK, good to know.
Gives me plenty of options to play around with for now.

Thanks
Frank

[FrankHa]

Update on that issue: I now try periodic Backup Job this way and just use the ReFS repository as source for everything. Looks promising. Needs a lot more tests. Might be still too slow, but this would not be a Veeam issue. Just creating a new Backup Copy Job instead of editing the old one was the hint I needed.
Thanks!
Frank

[Mildur]

You're welcome. You can check the bottleneck statistics for the backup copy job session.
This gives you an idea which component was the bottleneck.

https://helpcenter.veeam.com/docs/backu ... ck&ver=110
veeam-backup-replication-f2/read-this-f ... tml#p95291