View Single Post
  #15  
Old 07-11-2006, 05:13 AM
gryphonent gryphonent is offline
Registered User
 
Join Date: Mar 2006
Posts: 43
Send a message via ICQ to gryphonent Send a message via AIM to gryphonent
While I second all the above it would still be great to have some kind of notice to inform me that it’s about time to run a backup, because the last time the backup did complete successfully is a while back. It is probably common knowledge by now that this is THE feature I miss most in SuperDuper! Which makes it less super for me. So, here’s a suggestion: have a small app (VISIBLE to all) sitting somewhere and run independently from SuperDuper at startup. The app quickly checks for its internal modification date and depending on that notifies the user that a schedule didn’t run yesterday and whether it should run now. Or that the last backup was some four weeks ago. At each successful backup SuperDuper could notify this small app and update its timing table. It would not have to run all the time, but only at startup... and it would be free to users to decide whether they need that feature at all. I do for one, because SD’s scheduling reliability is the worst I ever encountered with any backup solution.
Reply With Quote