[dnanian]

I don't think that has anything to do with it. If a drive fails while we're copying to it, some system calls will convert its mount point to a folder. The drive *did* mount, otherwise SuperDuper! wouldn't find it at all when it tried to run the schedule and wouldn't even start.

What really happened is that, during the copy, the drive ejected itself. Why that happened is hard to say, but it could be a flaky drive, bad cables, compatibility issues with OSX, etc.

Recreating the schedule would have no effect on this at all (if you *didn't* recreate the schedule it would work if the drive was reliable, etc).