On 6/30/2010 11:02 AM, Emmanuel Noobadmin wrote:
On 6/30/10, Les Mikeselllesmikesell@gmail.com wrote:
One thing you can do on the cheap is set up nightly backups with backuppc. It can run on a machine that does something else in the daytime if necessary and its pooling and compression scheme will store about 10x the history you would expect. You need backups anyway since even complex redundancy schemes have modes of failure that can lose things.
Or, I suppose you could roll your own with rsync to a zfs filesystem with du-dup, compression, and snapshots set up.
Thanks for that suggestion. Right now I have a script that I used on several machines that basically runs at around 5am (depending on what other cronjobs are scheduled) that tarzip the datafolders, then move the archives into a USB HDD. The clients swap out that drive every few days or weeks (depending on who) when the script sends an email alert that it's full.
But a proper software meant to do that sounds like a better idea :D
Not only a better idea, but easier as well. See the details at http://backuppc.sourceforge.net/ but you'd probably want to install from the epel package. A hint, though: the packaged version has already configured where the archive resides and because of the hardlinks it has to be a single filesystem. So, if you mount some big disk/raid as /var/lib/backuppc _before_ you install the rpm you'll avoid some messy contortions. And you'll likely accumulate so many files/links that it won't be practical to copy the filesystem except with image methods. You might want to make a 3-member RAID1 with one device 'missing'. Then you can periodically add a matching external disk (esata is fastest), let it sync, then fail and remove it for offsite storage.