Lori,
Local initial snapmirror is a good idea whenever it's an option.
I've setup DR to St. Louis first and now Plano, Texas and it's been very reliable. Snapmirroring is also pretty good at setting up a checkpoint re-start if it has problem getting through. I am also pretty confident that it knows how to handle overlapping snapmirror. I've seen it happen to us when there is networking problem. If it detects that a snapmirroring is still in progress it will not kick off the same snapmirror.
Snapmirror has been really reliable. I've had lots more problem with the WAN. The only problem I've seen with Snapmirror is when you run out of disk space (We are using mostly qtree snapmirror).
Derek
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Lori Barfield Sent: Thursday, November 10, 2005 9:30 AM To: toasters@mathworks.com Subject: Re: snapmirroring over WAN
On 11/10/05, Brian Parent bparent@calvin.ucsd.edu wrote:
If I recall correctly, snapmirror uses very little bandwidth, and shouldn't be a problem on any modern network. It only copies the blocks which were changed, rather than entire files.
ah yes, sorry that i didn't mention this point...we're doing an initial ndmpcopy over a little gig switch here at the office before moving the filer to the colo.
some of our data is going to be large image files, so we aren't sure yet how much bandwidth the syncs are going to want. i was more concerned about the jerks and jolts and irregular paths you get when you fling data out into the wild...not sure how well netapps handle hiccups in the middle of snapping.
...lori