Sanity check for replication and Linux repo

[dhayes16]

Hello all. So we have a client with 2 sites connected with a high speed VPN connection. Each site has a hyperv host with several vms. Instead of using a cloud connect partner we were thinking of replicating the vms from one site to the other and visa versa. We are going to propose a couple sister dell 7545 boxes stuffed with disks and use them as local backup targets as well as replication targets for the other site. Does this sound reasonable?

Also we would like to inject some immutablity and we are super impressed with the Linux hardened repo. But we would like to have it at the main site. What would be the best way to get the backups from the remote site to the Linux repo at the primary site.? Backup copy job? I do not think we can backup the replicas to the Linux repo.

Or perhaps we scrap the Linux repo and just go with Wasabi since it now supports s3 object lock now.

Thanks for any feedback.
Dave

[HannesK]

Hello,
dell 7545 looks like laptops to me. Not sure whether that's intended.

Replicating vice versa is a common design, yes. Backups on the same box are a hardware risk.

Backup copy jobs are the best way, yes. Technically you can back up replicas, but there are some downsides:
- no file-indexing possible
- No SQL Point in Time recovery
- No CBT
- More complex restore mechanisms
- Additional license usage

Sure, object lock is also an option.

Best regards,
Hannes

[dhayes16]

Thanks for the reply. Sorry for the typo. I actually meant dell R7515 servers.