On Wed, 22 Sep 2010 18:03:01 -0500 "Dustin J. Mitchell" <[email protected]> wrote:
> - rsync the entire catalog to another machine nightly > > I just stuck that last one in because it was my technique back when I > managed a fleet of Amanda servers. Each would simply rsync its config > and catalog to the other servers. Since they were all backing up to > shared storage (a SAN), I could do a restore / amfetchdump / recovery > of any dump on any server without trouble. It's a very > non-Amanda-centric solution, but it's *very* effective. Uh, what's "amanda-centric" about using gnu tar or dump? Just because it's software that doesn't ship with amanda is no reason to avoid it. :-) As you say, it works. I do something similar. I started with a recent post on the Amanda fora, and now have a script that first runs the dumps for the day, then backs up the amanda metadata. These backups and the dumps are propagated to another machine and to offsite USB drives using rsync. The offsite capability I described at http://www.charlescurley.com/blog/articles/off_site_backups_for_amanda/index.html I haven't written up the metadata stuff yet. -- Charles Curley /"\ ASCII Ribbon Campaign Looking for fine software \ / Respect for open standards and/or writing? X No HTML/RTF in email http://www.charlescurley.com / \ No M$ Word docs in email Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
