I also believe strongly that backups shouldn't get in the way of productive work, which is why I decided against CDP (continuous data protection) and similarly automated tools. I've tried some of those applications and have concluded that the finer recovery granularity they offer doesn't compensate for how much they slow my system down. Besides, Laura had made it clear that daily backups were acceptable.

Laura already had recovery disks for both machines from the manufacturers, so I only had to make sure she created updated images of her boot drives should either one ever fail. To do that, I set her machines to run a scheduled DriveImage XML session every month, targeting the Rev drive, which is connected to the desktop and shared with the laptop. I suggested that she keep only the last two images of each drive; older copies would probably not prove useful.

To meet the requirements of forgiveness and ease of use, I scheduled two daily backups.

The first backup runs on the laptop with Microsoft SyncToy, a great, little-known tool with powerful options to keep two directories in sync. The target of that SyncToy run is a symmetrical shared folder on the desktop, which, if something goes wrong with the laptop, will give Laura a working machine, missing at worst only one day of data. Laura can live with that, but occasionally, when there are critical documents that can't be left as a single copy until the next backup, she can make ad hoc copies to the desktop share.

The third prong of my backup strategy for Laura is Windows Live OneCare, (yes, another Microsoft tool, but we are in Microsoft land, after all). OneCare does more than just backups, and it includes, for example, a firewall plus virus and spyware protection. Tune-up, a OneCare feature, can be set to automatically check for updates and run defrags.

I have scheduled OneCare to run daily backups on the laptop only, close to the wee hours of the morning, again targeting the same Rev drive used by DriveImage. OneCare will manage updates on both machines and defrag the drives once a week.

It may seem odd to run a backup to the Rev drive over the network, but OneCare treats the Rev drive as a local device, and "to protect the user," it refuses to consider that drive as a backup target. However, OneCare will blindly accept any network share as a backup device. To work around that bug, I left the Rev drive connected to the desktop and created a shared folder for consumption by the laptop and the OneCare backups.

So there you have it. Laura spent about $800 to purchase the Rev drive and cartridges, plus $50 for the annual subscription to OneCare. In my estimate, this setup should serve her well for at least three years, making her data protection cost less than $30 per month. Three years from now, who knows? Windows OneCare may have learned that the Iomega Rev is an "external" drive.

I explained to Laura that she should leave her machines on at night so that the scheduled backups -- spaced across the night to avoid conflicts -- can run. She also has two daily chores: Swap the latest Rev cartridge with the oldest copy in her bank vault, and check the OneCare status report for errors.

Does my backup strategy have weak points? Of course; any backup strategy does. The human factor is always a weak point. For example, if Laura forgets to rotate the cartridges, her data protection shield will weaken sensibly. Still she will have at least two up-to-date copies of her data, plus a relatively old one at the bank, to fall back on.