Before that I tried Mozy, iDrive, and a straight Time Machine backup. After multiple external HD failures and frustrating experiences with Mozy and iDrive (100% CPU for multiple weeks on end, extremely slow upload), I've been quite pleased with Arq.
On my non-Mac machines I just use s3cmd sync: http://s3tools.org/s3cmd-sync. I guess I could use JungleDisk, but why layer abstraction on something as simple as a file copy? :)
Off-site (everything): Backblaze
Off-site (small dataset immediate): Dropbox
On-site (everything): TimeMachine
I'm always kind of surprised at the number of people who have issues with TimeMachine. I've been using it since it came out, and have used it through two machine migrations and one failed hard drive. It's worked flawlessly every time.
Backblaze is configured to back up the same data as TimeMachine. I move important projects (current work) in to a Dropbox folder so that items sync there as well. Having this small, focused dataset means that I don't have to wait on a more general dataset backup to finish before my current work gets synced somewhere off-site.
Personal: I use macs - so I have time machine running to a Time Capsule all the time. On top of htat, my photos, documents, and music folders are rsync'd from my main machine through manual scripts to a modest homebuilt fileserver on a fairly regular basis - usually whenever I dump a bunch of new photos in (because in the end, the photos are the really valuable part, and the rest just goes along conveniently) On top of that, about once a month I plug in an external drive and the same scripts back up the same stuff to a single drive, and keep it elsewhere.
THe laptop, which I use more often, but try not to keep critical data on for any longer than I have to: - Photos get moved to the main photo library on the main mac desktop (where normal backup takes over) - A bootable clone of the laptop using SuperDuper to a pocket drive. Usually ever few weekends, at least once a month - also triggerred if I dump some new valuable data on to the machine and/or am planning to put the machine at higher risk (eg: travel). Pocket drive goes offsite. - Also, with about the same frequency, a second superduper clone to a container file on a storage drive at home.
Rationale: backups are good. The most important thing I have are my photos - they are priceless and irreplaceable. Everything else I could live with out.
- While I keep multiple copies, I need to work out some kind of better offsite solution as well.
- Photos (raw files), Music, old docs live on my Mac Mini "server" on an external drive, and get backed up via Time Machine to a 2nd external drive (to guard against single drive failure). I also use Backblaze as an off-site backup on my laptop + mini.
I was using Mozy as offsite backup, but since they recently changed their pricing, the cost went from $50/year to about $800/year so I switched to backblaze. We'll see how long they last at their lower prices...
For my personal stuff, I have a mixture of a large media library, and my wife's business files. The entire system gets backed up nightly (via rsync) to a primary terabyte USB drive. And then I back it up again to a different secondary terabyte USB drive. The business files (her accounting data, website source code, etc.) are additionally backed up to an offsite cloud backup service.
Every year I buy a new terabyte drive and make it the new primary backup drive. The old primary backup drive becomes the new secondary backup drive. The old secondary backup drive gets DBAN'd and sold on ebay. That way my primary backup drive hardware is never more than a year old, and secondary never more than 2.
My media library backups run the risk of a local disaster; fire, etc. But I can afford to lose all that and just be sad about it, but no big financial loss. My wife's business stuff is backed up locally + offsite for obvious reasons.
Movies, Music, eBooks live on a WD World Book and aren't backed up. (no real need since I can download them all again)
The few servers that I managed are backed up by http://sourceforge.net/projects/automysqlbackup/ and pushed to an s3 bucket. Code is always in a Git repo so no need. Images and other data from user uploads are backed up by http://s3tools.org/s3cmd
http://www.dokuwiki.org/dokuwiki is used to keep track of changes I make to my.conf, http.conf, php.ini, etc. Backup is done by s3cmd again.
Images of my son are saved using AeroFS since there's no size limit.
Business documents are stored using Dropbox and Google Docs (nothing too confidential)
For documents that are pretty important, they are stored off line on a printed piece of paper and stored in a filing cabinet. IRS documents, Business contracts, etc.
Otherwise I do a full-hard drive back up onto an external hard drive about once a week, so it makes an entire image.
For my windows machines I used to use Mozy but it does not stay out of the way as well as CrashPlan so if I cared at all about what was on my windows computers anymore I would probably use CrashPlan there as well.
BTW, don't forget that the wife wants the laundry done tonight.
I use DropBox too but I don't consider it as a backup solution rather a file sync solution.
The file server is 2 TB x2 RAID 1, so there's some protection there - one of the disks actually just failed, and I was able to successfully recover.
I only run hobby sites, so the databases on those I'm currently just backing up to AWS.
I use it to store my distant backups on http://rsync.net, which is most likely the best storage service I have ever used (simple, fast, reliable, relatively cheap and run by smart + nice people).
For off-site backups, I use the CrashPlan family plan on each of my machines.
This combination gives me the confidence that I'm covered in case of local machine failure, local drive failure and total loss of the local equipment.
I also mirror a few of the most important things such as photos and git repos between different computers, just so I have stuff taken care of in case of flood/fire/tape failure.
Some apps such as OneNote sync themselves between my laptop (Windows 7) and desktop PC (XP).
For others, such as Firefox Scrapbook, I run a manual rsync (on cygwin) running via an ssh tunnel. svn and remote desktop access, too, are via the ssh tunnel.
No DropBox, no Microsoft SkyDrive.
http://www.mikerubel.org/computers/rsync_snapshots/
The combination of cron, rsync and hardlinks, makes for incremental backups with versioning and minimal storage space, all over ssh.
SuperDuper is great. Having a bootable backup is awesome when things go wrong. The RAID gives me some peace since I can't afford to lose this data. Backing up the backup online somewhere is my next step, I think.
Independent of the tm backup, I also mirror my disk with carbon copy cloner every night.
Carbon Copy Cloner was one of the main reasons why I stayed with macs. A great software that is perfectly supplemented with Time Machine, IMHO.
I do incremental backups on demand with Time Machine.
A bunch of scripts run before the tarsnap to pull in external data such as offlineimap for all my IMAP accounts (including Gmail) and a database dump from my blog.
I run dirvish at my backup server and it fetches the data from other servers over ssh. So I have a central place to configure and monitor my backups.
(I guess that everyone at one point was about to restore some backup, only to find out that this specific server stopped pushing it's nightly backups ... somewhere last year)
All data for a finished project goes to /dev/null and as tarball on (several) DVDs.