Bacula-users

Re: [Bacula-users] Bacula Setup for 300 clients & 20 Servers

2009-04-23 07:52:54
Subject: Re: [Bacula-users] Bacula Setup for 300 clients & 20 Servers
From: Justin Williams <rjustinwilliams AT gmail DOT com>
To: Bacula-users AT lists.sourceforge DOT net
Date: Thu, 23 Apr 2009 07:48:34 -0400
Oops; forgot to reply all...

I set up, for my web server, after a pretty disastrous outage a couple months ago, a bacula system where, from home, I have a mac laptop open up a vpn tunnel to the server, and then use that tunnel to back up the entire server. Not as big a job as it sounds, as it's pretty small time, but, the tunnel works very well for me. Matter of fact, given the way I have things set up at home, between firewalls and other fun things, tunneling (either by ssh or by vpn) was the only way I had to be able to get my backups easily.

My setup is exceptionally bush league, at the moment:
Virtual private server running vpn and bacula-fd
mac laptop (old g3 pismo) running vpn client and bacula-dir/sd/fd
External USB hard drive (20G).

That said, it works, and it works well, even with that low level of equipment. Every night, I get an incremental backup., and I am comfortable that I can, even if something happened to my fruitbook, take the hard drive and recover my data at any time. The initial backup was a couple of gigs; after that, a couple of megs a night comes across. At this point, I'm now even considering offering that solution to some folks in my neighborhood who worry about data loss, too. Eventually, upgrading it to a solution for schools, etc. in the area seems like a really good idea. The really nice thing being, once you set it up right, you pretty well can just let it run and let it notify you of problems that you'll need to fix.

Put a real server-class system together, on a network with real bandwidth, and you have an exceptionally powerful system.

The inital backup is going to suck up a lot of time and bandwidth. I'd recommend, while you're doing your planning, that you back up in groups, to get things started. I.e. get all your local users, first. Then, once their full backup is done, start the remote users, etc. I suspect, if you're going to be dealing with that many, you might even break it down into sectors (local accounting, local graphics guys, local web guys, etc.).

If you're going to be tweaking the user filesets a lot, initially, I'd make a suggestion. I recently learned about the IgnoreFilesetChanges notion, which might come in really handy for you as you tweak different users' backup filesets - that way, you don't automatically perform a full backup every time you tweak (you can still perform that, if you want, but it isn't automatic).



------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and 
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users