| I will ignore what I do for server backups, and I will focus on my MacBook. I run my web development business and my personal life off of this system. The software I use: CrashPlan, Arq, DropBox, Carbon Copy Cloner. CrashPlan: I have backing up my data, configuration /Users, /Library. I have a bunch of regex restrictions to not backup various files such as caches, VMWare images, etc. Crashplan backups up to their cloud servers every 15 minutes. When I am at home (where I work from) it also backups to a local copy of CrashPlan on a server. Arq: I am doing daily backups to Arq. These are now being done to Glacier for long term / last resort backups. This only backups my /Users with heavy restrictions on which files. DropBox: I have many of my documents stored in Dropbox with the PackRat feature to keep copies of every version and deletion. I don't consider DropBox to be backup by itself, but I often find it is much faster to find and restore something via Dropbox than other methods. I also take care about the types of data I put on Dropbox. Carbon Copy Cloner: as I mentioned in another part of this thread, I think SuperDuper is better for most people. However, I do use CCC's ability to remotely do a boot able bare metal backup to my home office server. When I travel, I typically take an external backup drive with a current mirror of my system. I don't use Apple's Time Machine. I think it is a good choice for most home users. As Apple has added more features to Time Machine, I do think about adding it to my mix. That covers most things. I do have somethings under SVN or Git which could be considered another layer of backup. Currently, the biggest pain point for me in backups is VMWare images. I currently have 4 Linux and 3 Windows images on this system, and they can cause a huge amount of data needing to be backed up every time they are used. |
This is where a sector-by-sector backup program shines.
I don't know what to recommend on the Mac, but on Windows, ShadowProtect is pretty wonderful. It backs up only changed sectors - update 10MB in a 10GB file and it only copies that 10MB - and it's insanely fast.
Even with a file-by-file backup, one thing you can do for VMware images is to take a snapshot. After you take a snapshot, further changes to the VM don't go into the large .vmdk file you just snapshotted, they go into a new, potentially much smaller .vmdk file, so your next incremental backups may be much smaller.