Nimble Storage Array Replication across WAN
Hi,
Im new to Nimble Storage Arrays, my previous experiences have been with NetApp arrays.
Im looking at ways of using Storage level replication to move data across two widely separated Nimble CS Arrays.
The two devices are 1000 miles apart and have a mean latency of 90ms between them.
We are using VMWare as the hypervisor layer and Veeam as the backup solution. Veeam is also being used to replicate some key VMs across the two sites.
The RPO/RTO is very loose, with a days data loss and two days recovery of key services deemed acceptable by the business.
Obviously, I would like to be better than that.
As we have Nimble CS Arrays on both ends, it seems like we should be using the Storage Level replication to move the data we wish to protect, rather than using Veeam further up the stack.
There is a good, stable VPN tunnel between the two sites, but the tunnel needs to prioritise business application traffic during work hours.
After hours, there is little traffic across the tunnel so it can be used for replication.
The link speed is 12mbps, with a peak of 24mbps.
My questions is informational gathering.
Is it possible to use Storage Level replication across a 90ms latency WAN?
What are the advantages/disadvantages of using Storage Level replication instead of Veeam replication?
Does Storage level replication reduce the amount of traffic sent across the WAN as compared to Veeam replication?
Anything else I should know?
Im new to Nimble Storage Arrays, my previous experiences have been with NetApp arrays.
Im looking at ways of using Storage level replication to move data across two widely separated Nimble CS Arrays.
The two devices are 1000 miles apart and have a mean latency of 90ms between them.
We are using VMWare as the hypervisor layer and Veeam as the backup solution. Veeam is also being used to replicate some key VMs across the two sites.
The RPO/RTO is very loose, with a days data loss and two days recovery of key services deemed acceptable by the business.
Obviously, I would like to be better than that.
As we have Nimble CS Arrays on both ends, it seems like we should be using the Storage Level replication to move the data we wish to protect, rather than using Veeam further up the stack.
There is a good, stable VPN tunnel between the two sites, but the tunnel needs to prioritise business application traffic during work hours.
After hours, there is little traffic across the tunnel so it can be used for replication.
The link speed is 12mbps, with a peak of 24mbps.
My questions is informational gathering.
Is it possible to use Storage Level replication across a 90ms latency WAN?
What are the advantages/disadvantages of using Storage Level replication instead of Veeam replication?
Does Storage level replication reduce the amount of traffic sent across the WAN as compared to Veeam replication?
Anything else I should know?
Who is Participating?
In all of that, what level of protection is there against an encryption event with an inside perp? Is there an air-gap to protect the data?
For Storage Replica in Windows Server 2016 we need 5ms or less for synchronous replication. Anything higher than that then it's asynchronous with the acceptable data loss limit set by both latency and bandwidth available. Nimble would be the ones to ask about the specifics of their replication tech.
For Storage Replica in Windows Server 2016 we need 5ms or less for synchronous replication. Anything higher than that then it's asynchronous with the acceptable data loss limit set by both latency and bandwidth available. Nimble would be the ones to ask about the specifics of their replication tech.
Hi Phillip
This isn't for backup but for DR in case one data centre disappears.
We have a backup regime for randomware. But that's local. So won't help during a disaster event.
This isn't for backup but for DR in case one data centre disappears.
We have a backup regime for randomware. But that's local. So won't help during a disaster event.
Got it. The question was more of a what-if to stir up some thinking if it wasn't already in play. :)
Nimble is definitely the one to answer the specifics for replication.
Nimble is definitely the one to answer the specifics for replication.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
There may be some folks here that have worked directly with their products but...