SD no longer honouring backup-on-mounting-drive

[Manu Chao]

Even deleting all files with the word Superduper in their name (incl. the application) did not fix the problem (ok, I kept the files in /private/var/root and /private/var/log).

Deleting the two files:
~/Library/LaunchAgents/com.shirtpocket.backuponmount.plist and
~/Library/LaunchAgents/com.shirtpocket.backuponmount-login.plist

however, fixed it. Which is probably not completely surprising. And since the problem re-occurred within about three months (it re-occurred two months ago, I only now got around to fix it) maybe there is a pattern as to what triggers the failure.

[dnanian]

What's weird is that simply turning off the backups (or removing them), and quitting SD, will remove those agents...

[Manu Chao]

What do you mean with 'turning off the backups'? Unchecking both checkboxes in the dialogue box showing up when clicking Edit in the 'Scheduled Copies' window?

And it now does so, ie, deleting the scheduled copies removes those two plist files. I only had discovered these two files relatively late in my debugging process (I was first only looking out for files with 'superduper' in their name). It is thus possible that I had set up a new scheduled copy (which didn't work), then deleted all files with 'superduper' in their name without first deleting the scheduled copies from within SuperDuper with therefore these two files remaining.

In short, I cannot say for sure that deleting the scheduled copies from within SD did not delete these two plist files. I only know that a new 'installation' of SD, encountering these two files failed to start upon mounting a destination volume (of a newly scheduled copy). And I know that only deleting the scheduled copies from within SD followed by deleting their folder in Application Support did not solve the problem.

But the next time this occurs, I will first check whether deleting the scheduled copies from within SD actually removes those two files or if them getting stuck might have caused that problem. (I might even be able to test this by booting of a clone from a few days ago.)

[dnanian]

I mean deleting the scheduled copies, or unchecking the checkboxes, will delete those files. Since I originally told you to delete them, they were removed already, and are only back because you recreated the schedules. Why deleting them manually worked I don't know, since - again - they had already been removed.