Quick blurb on backups and Amanda

I’ve mentioned AMANDA a couple of times, and I just wanted to give an update on where I stood.

I hate to say it, but I gave up. I didn’t have the time to work with the configurations and craft them into the backup plan I needed. On the other hand, I wasn’t willing to give up a vendor-neutral backup solution that used off-the-shelf tools like Amanda does.

So I bought support. For $100 per client, it was a net win when you consider the time I spent and would have continue to spend. Zmanda gave me the upgrade to the 3.0 code base, and using the web based GUI is a breeze. There were a couple of minor issues, since the interface code is new, but Zmanda has been very good about issuing me patches and making sure that the issues I experienced were taken care of.

I’ve been very happy. The only remaining issues I’ve got in my backup solution are very close to being taken care of, and even those are just issues of logistics on my end.

Overall, buying support from Zmanda has been a big win so far.

The Admin Arsenal blog is talking about backups today, too. May want to check that out.

  • I roll my own disk-to-disk backup (over the network) with rdiff-backup. It’s as simple as rsync (in fact, it uses librsync on the backend), but it keeps reverse differentials available so you can restore any previous backup state for files or directories.

    Duplicity is also a similar thing that’s entirely client-side, and as such it can encrypt the reverse diffs before sending them out to the server. This is useful if you don’t control the backup server, for instance with its Amazon S3 plugin.

  • I too gave up on Amanda. I use BackupPC on my home Ubuntu server and could not be happier. It backs up my wife’s any my Macbooks like a champ. I couldn’t recommend it more.