Best practice for 1 primary backup + 2 immutable Backup Copy targets

Hello everyone,

I would like to validate a design scenario in Veeam Backup & Replication.

The customer wants the following backup architecture:

• A primary backup repository without immutability

• A secondary immutable repository in the same datacenter

• A third immutable repository in the DR site

My first thought is to use:

• 1 primary backup job to the non-immutable repository

• 2 Backup Copy Jobs using that same primary backup as source:

  • one Backup Copy Job to the local immutable repository

  • one Backup Copy Job to the DR immutable repository

My main question is whether this is the right and recommended approach in Veeam.

More specifically, I would like to confirm:

1. Is it supported and considered best practice to have one primary backup job and then two separate Backup Copy Jobs pointing to two different immutable targets?

2. If both Backup Copy Jobs use the same source backup chain, could there be any issue with concurrency, locking, or file handling?

3. Would it be better to run:

   • one single primary backup job with two associated Backup Copy Jobs, or

   • two separate primary backup jobs followed by their own Backup Copy Jobs?

4. For this type of design, would you recommend:

   • Immediate Copy for the local immutable repository, and

   • Periodic Copy for the DR immutable repository
     to better control bandwidth and job overlap?

The goal is to keep:

• an operational primary backup,

• a local immutable copy for cyber resilience,

• and a second immutable copy in DR for site-level disaster recovery.

I would appreciate any guidance on whether this design is technically correct, supported, and aligned with Veeam best practices.

Thank you.