|
Ok, that is a valid point. So let me paint the picture a little differently: How often do you backup with SD!?
Here is how my life currently looks w/rt backups: TM backs up hourly. SD! backs up daily, in the middle of the night.
Two weeks ago, I had a drive failure at about 5pm. I had been working all day. I didn't particularly remember what I had touched that day. Here are the options I had for recovery:
1) swap in the SD! backup drive and be up and running immediately, but with the task of manually pulling from TM everything I could think of that had changed (time consuming), and living with an unknown amount of lost data (risky)
2) ignore the SD! backup drive, and restore from the TM backup being certain that everything I have is as fresh as possible (time consuming but not risky)
I took option 2. But in thinking it through, I realized that I can not think of a single situation in which I would take option 1 (well except for if I had an HD crash at 3am that I knew for sure happened after my SD! backup had completed, but before I had done any other work that TM! caught).
What I really want is an automated way to take an SD! backup and bring it up to date w/rt the latest TM backup. It just doesn't seem reasonable to run SD! hourly - if it takes 16 minutes to run, that means 25% of the time, your computer is running a process that is either pegging the CPU or the disk.
I guess another way to describe what I think needs to exist is an offline utility that can repeatedly update an offline backup based on the latest TM run. Not couple the logic of SD! & TM, just use the TM logic alone, but in a different way. It's reasonable to say that this would be an entirely different utility from SD! - but one that is sorely needed, IMHO.
|