SOBR and Affinity Rules

[t481]

Hello,
I've got 2 large servers which I've combined under one SOBR. Is there a way to set some sort of affinity rules so that if a server is being backed up to Extents on one server that the Copy of it would be placed on the other without creating 2 separate SOBRs?

[foggy]

Could you please clarify the scenario in question - under "copy", do you mean backup copy as a secondary destination for the backups?

[t481]

Yes. What I would like is to be able to combine the extents on both servers under one SOBR but for Veeam to ensure that backup copy jobs for VMs are stored on the other server in case one goes down. This would give the ability to use all the available space for backups while ensuring availability should one server go down.

[foggy]

Then why do you need SOBR? Make primary backup to one server and a copy to another.

[billcouper]

t481 what you describe isn't a scale-out repository, but rather two distinct and separate repositorys.

Scale-out repository combines multiple extents into a single repository, and jobs can only target repositorys, not an extent within one.

If you have 20 backup storage servers, each 10TB, and your primary backup job needs 100TB of storage you could create an SOBR using 10x 10TB storage servers (each server being an extent of the SOBR), then, you could combine the remaining 10 backup storage servers into a second 100TB SOBR, and create a Backup Copy job to duplicate primary backups to this additional completely separate SOBR.
Depending on the placement policy of the SOBR will determine which extent(s) VM backups land on, but you can't specify an extent manually, and there is no placement policy that maintains two backup chains on separate extents.


in your case, if each of your servers have enough capacity individually to store the entire backup, just create them as individual standalone repositorys. primary job to server1 repo, backup copy job to server2 repo.