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

Hi ​@chateichon7 

Happy  to help review your design decision based on veeam best practices architecture. 

High recommendation you check out Veeam Architects Site

https://www.veeambp.com/ 

there is  great guideness in there. 

Thank you for your response; however, I don't see much information on this backup copy topic. Could you please share a direct link with me?

Sure here you go 

https://bp.veeam.com/vbr/4_Operations/O_Veeam_Jobs/O_backup_copy_jobs/backup_copy_job.html

there also good information here

https://www.veeam.com/blog/321-backup-rule.html

​@chateichon7 , 

It’s a reasonable setup.

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?

Yes

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

Veeam’s scheduler will handle the resource contention as gracefully as it can. You might sometimes see the Backup Copy Jobs (BCJs) in a waiting phase as one BCJ is processing the source files, but you can likely avoid this with judicious use of Backup Copy Windows (configure in the BCJ job, let’s you set when the BCJ will try to do its thing)

Would it be better to run:

Dealer’s choice. I would go with 2x Backup Copy Jobs as this means less pressure on your production machines due to snapshots / backup processing

For this type of design, would you recommend:

Dealer’s choice. Immediate Copy and Periodic copy have different purposes. 

Immediate: Copies new restore points from the source backups as soon as they appear

Periodic: Perform a periodic copy of the most recent restore point at a scheduled time

So you will need to discuss with your client the type of protection they want. Both Copy Jobs can use a different method, so you have a lot of flexibility here.

​@ddomask already clarified most of your questions I guess.

Just to give maybe a recommendation on top:

• go for only a single primary job and do the 2 backup copies to reduce load to the production
• you might consider using a SOBR + capacity tier approach for one of your copies if you would like to avoid having too much jobs and S3 is one of your approaches for the secondary repo. https://helpcenter.veeam.com/docs/vbr/userguide/capacity_tier.html?ver=13
• Usually, to fulfill the 3-2-1 rule, it is sufficient to copy your data once every day, even if the primary job runs more often. So, I personally prefer the “periodic” mode for backup copies as it gives better control on the schedule for the copy. Keep in mind though, that this mode cannot copy transaction protocol backups (log-shipping).
• Bandwidth control doesn’t depend on the job mode. This can be done system wide in the network options of VBR. It’s merely the different approach in the scheduling that decides between “immediate” and “periodic” here.