Separate SOBRs for local and remote backups

[wntech]

I am putting together a new Veeam infrastructure for 2 sites, Site A and Site B. Both sites will backup locally and use backup copy jobs to the other site. All will be managed by a single VBR server at the head office, site A

We intend to make use of a SOBR at each site for the backup repositories each made of 4 extents. The SOBR at each site will be the target for local backup jobs and remote backup copy jobs

My question is, is there any benefit in having 2 SOBRs at each site using the same extents but a different path , one for local jobs and one for remote copy jobs ?

My current thoughts are :

In a single SOBR scenario, backup and backup copy jobs will be split by folders under the same path on each extent e.g. E:\Backups\Job-Name

Repository - Path
SOBR-SITEA - E:\Backups
SOBR-SITEB - E:\Backups

However, I can provide more segregation between storage for backup and remote backup copy jobs by creating 2 SOBRs each targeting a different path

Site A:
Repository - Path
SOBR-SITEA-LOCAL - E:\Backups\Local - Target for Local Backups at Site A
SOBR-SITEA-REMOTE - E:\Backups\Remote - Target for Backup Copy Jobs from Site B

Site B:
Repository - Path
SOBR-SITEB-LOCAL - E:\Backups\Local - Target for Local Backups at Site B
SOBR-SITEB-REMOTE - E:\Backups\Remote - Target for Backup Copy Jobs from Site A

The main advantage I can see is the additional segregation of local and remote backups in the directory structure which I do like but would like to check if there are any issues with this design ?

[foggy]

The only other benefits I see are the ability to control concurrent tasks/ingestion rate separately and specify different mount servers.

[wntech]

Thanks Foggy, so there nothing specifically wrong with doing it like this ?

I think the fact that VBR config lets me do it anyway is a good start

[foggy]

Nothing specifically wrong.