We also had to back up our volumes to a remote site via snapmirror accross a T1 WAN. One of the vols was over 1TB and it would have taken days to create the initial baseline over the T1 so we snapped to SDLT tape, sent it down to CA and created the baseline in a "snap"!

Now our nightly VSMs take about 2 hours for 5 gigs (our average delta size).

Henry

-----Original Message----- From: owner-toasters@mathworks.com on behalf of Leeds, Daniel Sent: Thu 11/10/2005 9:21 AM To: Brian Parent; toasters@mathworks.com Cc: Subject: RE: snapmirroring over WAN

yeah but that initial transfer can be fun if you are mirroring a couple terabyte volumes or if the application is generating alot of changes. a DS3 wan link would be no problem but they may need to rate limit snapmirror on much smaller wan links. -----Original Message----- From: owner-toasters@mathworks.com on behalf of Brian Parent Sent: Thu 11/10/2005 9:08 AM To: toasters@mathworks.com Subject: Re: snapmirroring over WAN 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. Re: > Date: Thu, 10 Nov 2005 08:49:38 -0800 > From: Lori Barfield itdirector@gmail.com > To: toasters@mathworks.com > Subject: snapmirroring over WAN > > for offsite backups, we hope to snapmirror our new fas 3020 on a > regular schedule via vpn over the internet to an older filer at our colo. > obviously, intermittent latency is a concern since we don't have a > dedicated link. and so is the potential for overpowering the modest > firewall/network hardware currently in place. does anyone have a > suggestion for how we might throttle the snapmirrors to improve > reliability in the transmission? > > and how are you folks handling encryption for remote mirroring? > we have a small pix, sonicwall, or cisco to choose from...i'm > guessing we may have to try all three but i hope to pick the one > most likely to succeed the first time. > > > ...lori