2007-06-14 23:45:01 UTC
We have a primary data storage location that will house roughly upto 80gig
of information at any one time. The majority of this information will remain
static as many active projects go on and off hold often.
The information contents will be primarily Autocad Files, Office Docs,
Photos - (JPG).
This active storage location will have through the course of one business
day have on avg 1-2 gig of information modified.
I am currently using Windows server 2003 SP1 on the primary master DFS loc I
am testing with. I am finding though that when you open a file it might not
be opening from that same storage location but referring to the secondary
link and actually opening that file.
I am planning to do the upgrade to R2 since were under SA and just awaiting
The 2 folder locations that are going to be linked togather actually reside
in 2 different sites that are tied togather via static encrypted VPN tunnel.
We currently have the VPN tunnel etc all in place but the users in offsite
location are too slow to access files from the central storage location.
On any given project - we may have users working on the Autocad files in
My questions are:
1. Is a secure Static VPN tunnel (1.5mb pipe) safe enough to consider DFS /
FRS replication of these files. By safe I am meaning from potential of
corruption etc considering the file sizes can get to be 1-2mb DWG files or
sometimes little larger.
2. Currently in SP1 my tests show this to be very slow cause it is referring
across the VPN instead of keeping user on their local side of the VPN and
only using VPN tunnel to sync the file. I am wondering or been reading it
seems R2 will allow me to control this which should eliminate this
performance issue per say right?
3. Are there any space / size limitiations that should be considered when
using this solution?
I am looking at this solutions to allow the following:
Users on both side of the VPN see a local copy of the files - they can open
and edit that will be fast and not be opening over the VPN, but whenchanges
made the file will be synced to both sides the vpn giving both sides
essentially a local copy.
This will also give us essentialy a active fail over of our current storage
incase one side has a server storage failure for whatever reason.
This also gives us offsite redundancy which is even better for a fail over.
Can anyone point to me reasons that maybe I should not be considering this a
solution or things to be aware of that maybe we have not seen yet of
potential problems. So far this solution we see assuming we can solve the
latency issues of opening files, copying etc... seems to be an ideal
Because this is a static VPN tunnel it still does rely on stable internet
connection, so biggest point of failure I see if the potential if you lose
your internet connection.
THANKS for any responce and advice :)