This is my strategy. I have a separate strategy for each disk.
/dev/sda1 mounted as /
/dev/sdb1 mounted as /home
I use Clonezilla http://clonezilla.org/ to backup bit for bit /dev/sda. This makes and easy restore of all the mostly static applications. Cloning /dev/sda gets the boot sector along with everything else making a restore easy peasy. I redo this weekly or if I do a big update to the system.
To backup /home, I use rdiff-backup http://www.gnu.org/savannah-checkouts/n … ff-backup/ and backup to a NFS share. This application has all the benefits of mirroring with the added benefit of multiple incrementals. It can resort to any point in the past. It allows you to specify exactly which directories and files to backup and acts like rsync which is very frugal with bandwidth. After the initial backup, subsequent backups are real quick.
What is your strategy?
What is your strategy?
I do not have one yet, at least not for my new Eee PC. Thank you for sharing your backup strategy, it has prompted me to think about my own. I will probably end up using my own antiquated bash script, which is basically just a wrapper for tar. I have used it for years and it works well for me.
Until now I've just done a simple copy/paste backup of my home directory every now and then (when the inspiration takes me). I like the look of rdiff though
Backing up eh?? Seems a bit last year to me!
I'm trying to keep my Eee as mobile as possible.. So I'm attempting to keep pretty much all my data in the "cloud" as they call it.
Using a combination of Google Reader / Calendar / Docs and so on I've got no real reason to keep any files on the Eee at all, so there's no real need to bother with backing up.
I have never managed to get Clonezilla to work backing stuff up over the network. I use partimage on the System Rescue CD to make images via nfs to an external hard disk on my server.
For general backup I use backuppc. This automatically slurps stuff off my eeePC to the server. You can configure exactly what gets backed up and what gets ignored.
All my important day to day stuff is in text files, so I use git for them. If I am using my laptop away from the network I just do a git pull before I leave, which gets all my stuff onto the laptop. When I get back I just do a git push, which merges all my changes back to the server. I also keep a copy of my git repo on an Internet accessible server, so I can update via the Internet using the phone, if I forget before I leave home.
At home I keep almost everything important on my server and access it via nfs shares. The stuff I really care about is backed up to an external usb drive using Duplicity. This creates encrypted tar volumes. I do daily incrementals and full new backups weekly. The duplicity files are rsynced to my iBackup account. Duplicity is great for storing stuff off site. Everything is encrypted via gpg and it requires no special software on the destination server. You can send your changes via ssh, ftp and various other protocols.
Last edited by geekinthesticks (2009-03-17 08:34:28)