Syncing remote servers

Enigma42

n00b
Joined
Aug 26, 2008
Messages
6
We have a file server in our office with about 35 users on a gigabit LAN. Performance is fine within this office, but the team has expanded into two other offices as well. Bandwidth between offices is pretty low though, so users in the other offices have very slow access to the server. We're overdue for a new server anyway, so the question has been raised as to what we can do to make things workable for the remote users.

I know there's nothing to be done about network bandwidth between offices, so we're wondering about having a server in each office and synchronizing them each night. Once the files are loaded, incremental changes won't be that extensive. But we'd need some sort of check-in/out system, maybe some way to 'push' syncs manually, and overall the system would need to be pretty much automatic and seamless from the user POV.

Now, I'm not a network guy and not really a server guy either. I built the server, but beyond the normal/enthusiast PC hardware and technologies, I'm in the dark. I've got the task to research the plausibility of all this stuff and report back though. I'm not really sure where to begin and we won't be able to get some real experts in here to help until I can at least give a general idea of whether the idea is workable and how it would work at a broad level.

So, is this a reasonable idea? If so, what would we need to make it work? If not, is ther an alternative we've overlooked? If anyone know about this stuff, I would appreciate any help you can give! Thanks. . .
 
Use DFS namespace replication between the two srevers.

Point the users at the DFS share and let AD sites and services decide where they go.

*Active directory Sites and services must be setup properly for users to be directed to the server in their location*
 
File versioning could be tough if two people modify the same file at different sites. I will be interested to read the suggestions.
 
SharePoint server at main office.

My dept's Sharepoint server is on the other side of the country and I hit the web interface over an IPSEC VPN. I don't have any complaints about the speed really, which is going to be limited by the WAN connection not the server for the most part.

Doing SMB file shares over WAN is always going to suck regardless of pipe speed. Nightly DFS replication is a decent idea as well. Depends on how many files and who needs access to them and how often.
 
Another option is if you're going to be using Server 2008/Win 7 is to use branch cache, basically caches a local copy at each remote site then writes incremental changes back. As others have said, you need to be careful about multiple people having the same file open.

Beyond what's already been mentioned you could look at a terminal server and have people remote to that to work.
 
Until I have time to set up a domain on our network and switch over to DFS this summer, I'm using Micosoft SyncToy 2.1 over a VPN to sync our office's file server with the file server in our other office 20 miles away. It runs each night and we have it set to just copy the newest version to each machine. We very rarely (never, so far) have files that are incrementally edited throughout the day in both offices, though, so I don't know if it would work so well if that was an issue for you.
 
Beyond what's already been mentioned you could look at a terminal server and have people remote to that to work.

That's actually a really good idea if it is an option, go for the virtual desktops at the remote site, and make sure to have redundant internet connections.
 
DFS-r...we've been using it for years..its solid...it only replicates the changes made to the files down to the bit level...also...it has no problem when i push out 500 meg files. do it

also keep in mind each site has their own copy of the shared drive at each location. they just work off of their 'copy' so to speak.

genius
 
Thanks for the ideas folks!

DFS really sounds like it might be the way to go with this. After the comments here I did a little bit of reading on it and it all seems pretty promising.

My only lingering concern is file version control. I can easily imagine plenty of scenarios where these users will be attempting to edit the same files on the same day. Right now, it's no problem since everyone is working from the same drive and you just get a notice that you are in 'read-only' mode. Any recommendations on a check-in/out system to use with all this?

BTW, since I didn't mention it previously (oops!), the servers would be 2008 machines, but the users will be on XP. Unfortunately, I can't do anything about that. The company sat out the Vista upgrade (maybe with good reason) and they are now talking about waiting until 'Windows 8' to upgrade! I think that's insane, but I don't have any influence on that decision.
 
BTW, since I didn't mention it previously (oops!), the servers would be 2008 machines, but the users will be on XP. Unfortunately, I can't do anything about that. The company sat out the Vista upgrade (maybe with good reason) and they are now talking about waiting until 'Windows 8' to upgrade! I think that's insane, but I don't have any influence on that decision.

server 2008 and XP is fine. If you want to fully use the new GPO options for 2008 you can install the Client side extensions on the xp machines.

Sitting out till win 8 may be a long time lol. Good luck with that. You will be buying new machines before then for a hardware refresh
 
Server 2008 R2 is fine, '08 has memory bugs but if you are not virtual probably not an issue.
Win 7 has gained traction at my org, and we are deploying it for everything starting in July.
 
Globalscape's Avail WAFS is your answer. This is exactly what the product does.

http://www.globalscape.com/wafs/index.aspx

We've been using this at a client site for almost 4 years. Rock solid, never, ever an issue. Great support. This product replicates shares across multisite networks, like DFS does- but much much better. It does support Windows file-locking, so there's your answer for version control. Uses bit-level-differential to sync shares, so bandwidth requirements are very low. It also scales the traffic when necessary, to minimize the effect on the network. You set up VPN tunnels between the site; set up replication; and away it goes.

Windows file locking support is a huge plus for this product. In my client's case, they need to sync CAD files. It does this seamlessly. It can also provide remote backups for you if you'd like. It also provides versioning, which you can set the limits/parameters- no of days; no of versions/revisions; also provides complete deleted file protection. I can't say enough about this product. It is NOT an accelerator/cache device like a RiverBed- it is a software solution that installs on your Windows servers. One server is the master- then you install agents on as many other servers as you like.

Its only caveat is you need to set up the primary master with enough storage space to accomodate about double your data needs. Not a big deal- but something to be aware of.
 
NetApp snapmirror! lol (if you've got money to burn), but seriously, DFS should do.
 
Back
Top