Alert for unattached disk?

[Forcery]

Hey,

I bought SuperDuper! a couple of weeks ago, and it seems to be working fine.

The problem I have is that I'm using it on my MacBook Pro, and I don't have the backup disk attached except when I'm writing the backup to it. I've setup a schedule so that it backups 3 times a week, but I'm not always at home when the backup is scheduled to run. What happens is that SuperDuper informs me that the backup failed, and I have to close the log window, select the disks and then click copy now (and one more click to confirm the smart copy).

So what I'm wondering is: Is there any way that SuperDuper! can ask me to insert the disk if it's not available, so that I can backup or cancel backup with just one click? You may say that I'm lazy, but I'm pretty sure that I'll stop backuping regularily after a while ("once a week should be ok..") if I have to run through hoops each time it's scheduled to backup..

I suppose this is more of a feature request than a question, unless it's solvable in some other way!

Thanks in advance!

[dnanian]

At present, sorry, no. We consciously don't prompt for the drive, because we're running "automated", and that means "no interaction". We don't want to block when another backup, or other automated action, is stacked up and waiting...

[Forcery]

Ok, I see. But what about some sort of "retry" button in the log window that appears when the volume is not mounted? Could that work?

And I can't be the only one who's having this problem?

[dnanian]

We're looking at various options to help with this kind of thing, but don't have anything coming in the immediate future...

[Forcery]

Ok, a followup question:

I've set up iCal to remind me that I need to attach the backup disk 5 minutes prior to backup. So I attach it, wait 5 minutes and see SuperDuper! open up and complain that it cannot find the drive that I attached 5 minutes earlier!

I've verified that the backup disk is mounted in the Finder twice now - but it doesn't backup..

What is going on, and what can I do to solve it?

[dnanian]

Sounds like the schedule was created and then the drive was either erased or manipulated by some low-level tool that changed its UUID.

Please try recreating your schedule...