Nimble Storage Array Replication across WAN
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?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
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.
Nimble is definitely the one to answer the specifics for replication.
There may be some folks here that have worked directly with their products but...
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
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.