Hey Tom -
If you propate over an IP network on the front end of the head, then yes
there is a performance penalty. If you have the disk shelves handle the
propagation, then you can do some interesting things which do not create a
performance penalty. But then you're talking about putting intelligence
down into the disk shelves themselves.
/Christian Adams
> -----Original Message-----
> From: tkaczma(a)gryf.net [SMTP:tkaczma@gryf.net]
> Sent: Monday, March 22, 1999 4:47 PM
> To: toasters(a)mathworks.com
> Subject: RE: NetApp/Auspex killer?
>
>
>
> 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