Site-to-Site replication for DR

[Prophet]

One of our clients has asked for us to spec up Site-to-Site replication and DR. They currently have 3 Dell hosts with a SAN which is all due for replacement, so we will be it to replicate the new kit to, at another site.

It will be an Hyper-V environment so we're looking for a robust way to sync both sites, either on the fly or at timed intervals depending on network overheads.

Currently we've looked at using Veeam to act as the replication agent but I'm open to other ideas.

They have 20 servers and around 5TB of data to replicate over two 100/100 leased lines.

 

[Prophet]

Works absolutely fine for us. We use it to keep around 20 cold standby VMs ready at a 2nd site.

Are there any issues that you know of replicating onto different hardware? The new kit is iSCSI the old is SAS based..

 

[Prophet]

We have no issues with hardware and architectural differences in configuration of clusters at both ends, the only thing you might need to set is "migrate to a physical computer with a different processor version".

But by the sounds of it the hosts will be the same anyway?

Thanks for that. The hosts are all Dell kit but different revisions.

How behind are your cold VM's?

 

[Prophet]

According to our replication health, they were last synced 5 minutes ago (built in schedule frequency is 5 minute intervals)

Once the initial sync is done, the rest are incremental so shouldn't be massively taxing on bandwidth.

Excellent! I'll look further into this

 

[Prophet]

what's wrong with SAN replication?

iSCSI to SAS is a no go.

 

[Prophet]

ah ok, I was jumping to assumptions that you had two sans in a group

I wish, but no... The existing SAS will be relocated and used as the 'backup' for replicating the new iSCSI SAN.