-----Original Message----- From: Thompson, Arnold [SMTP:arnold.thompson@netapp.com] Sent: Monday, March 22, 1999 1:04 PM To: Mohler, Jeff; toasters@mathworks.com Subject: RE: NetApp/Auspex killer?
You're gonna *love* SnapMirror & SnapRestore!
---
Already seen it, it does -not- match up to what EMC can do for us for remote DR service.
A possible 2 minute outage in data-flow is a literal million dollar question for us.
Your DR solution should PUSH data out constantly, not request it remotely every 60 seconds, then if a snapcopy fails for that period, it gets thrown away on the remote side...two lost minutes of data.
Thats is at a minimum FOUR lost billing cycles on our ATM/IP/Voice network...and in our environment an incomplete billing cycle is non-billable.
I belive the continuous real-time transfer of data from the main site to the remote site would be a solution that we could live with in the future.
On Mon, 22 Mar 1999, Mohler, Jeff wrote:
Your DR solution should PUSH data out constantly, not request it remotely every 60 seconds, then if a snapcopy fails for that period, it gets thrown away on the remote side...two lost minutes of data.
That's true for your application, but I don't want to mirror my disks across the country even every 60 seconds. Once every couple of minutes or hours is perfect for me. If you truly mirror your disks the latency associated with data propagation will kill the performance.
Tom
In message Pine.LNX.4.04.9903221842050.789-100000@gryf.gryf.net, tkaczma@g ryf.net writes:
On Mon, 22 Mar 1999, Mohler, Jeff wrote:
Your DR solution should PUSH data out constantly, not request it remotely every 60 seconds, then if a snapcopy fails for that period, it gets thrown away on the remote side...two lost minutes of data.
That's true for your application, but I don't want to mirror my disks across the country even every 60 seconds. Once every couple of minutes or hours is perfect for me. If you truly mirror your disks the latency associated with data propagation will kill the performance.
Tom
It all boils down to the words "disaster" and "recovery" being subjective....
And the "official" meanings change between the time you show management a price tag and when the data center catches on fire. :)
jason
-
Jason D. Kelleher -
Mohler, Jeff -
tkaczma＠gryf.net