Discussion Locked

Client backups at over 50 locations

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Our company has about 50+ locations around the country. We currently use a zip drive shared on one workstation at each location, and we use some proprietary software we wrote to write the files to the disks.

This is not by any means a very reliable system.

My question for discussion is, how do the big boys do it? How does a large organization do backups of each client. The bandwidth limitations of our WAN (64k frame relay) limits us from using a central server, and we make users keep all their data in the \data folder on the individual machine. We do not have a server at each location, but we could consider a product like the snap drive at each location, but the problem there is how do you back that up in case that goes down. (putting all your eggs in one basket...)

I'd just like to start some ideas flowing about how bigger companies (we have about 800+ employees) do this, because we will certainly grow in the next few years.

Any suggestions will be appreciated.

3 replies

by rzan

By no means rely on snap servers for backups. Even though they are easy to set up and administer, they are not 100% reliable. We purchased one to replace a CDROM server that crashed on us, but the snap server itself had to be sent back because it failed in 2 days of use. What I suggest doing since you have such a large environment is to get you company to shell out the bucks and start setting up dedicated servers at each facility. If you don't have the IT resources to manage those remote servers, then your only solution would be to replace those old 64K switched dinosaur lines with high bandwidth T-1 or T-3 lines. If your company can afford it, have them go to fiber lines like ATM or OC3. That way, you have enough bandwidth to backup from a central location over the WAN. We do not backup each client on our network anyway, we backup servers and encourage all users to use their home directory to store critical files. I am a systems admin work for a state agency (MTA Bridges & Tunnels) responsible for managing the major bridges and tunnels in New York City and the EZ Pass toll system. We have about 800+ employees and we have dedicated backup servers at only two locations..Broadway and Randall's Island under the Triborough Briddge. The other facilites( like Marine Park, Verazzano, etc)are connected by routers over a frame relay link, no servers at all. Everyone there is connected through a hub to a router, to our frame relay WAN. You have to convince your company to upgrade its WAN infrastructure or hire staff at every location to manage a dedicated backup server. If they won't shell out the $$$$, then I suggest you start looking for a job in a company that knows the value of data and importance of a solid networkdesign, because a company like that is bound towards bankruptcy if they suffer a catastophic systems crash and you will be the one blamed.

by blair.mcfarlain

I appreciate your comments. I'd LOVE to have a dedicated T-1 to each location. We only have one location that has that (and it isn't even set up yet) and that is here in houston. I will certainly make use of your suggestions.

I'd like to alsohave a servers at each location, but i've been trying to get that for a long time now to no avail. They just don't want to shell out the $$ for them.

Anyway, thanks for your comments, they are very much appreciated!

by brainiac

One way to do this is to setup a linux server @ each location. this will be alot cheaper than T-1 or T-3 lines. Hard drives are cheap. What I've done is setup a linux box with raid 5 and also a tape drive. The users save their data to home directories on the linux box which has the redundant hard drive in case on failure. I also do backups to tape in case the entire box is damaged.
These boxes cost me around $1500 each, about the same as a good pc. I manage them using secure shell and a web based program called Webmin.

This discussion is closed to new replies.