Please don’t get me wrong: both of these are superior products, and I have and use and love both.

That said, SuperDuper (SD) offers a “clone-on-mount” (auto-clone) option that can wreak havoc when and if you decide you want to run Diskwarror (DW) on the destination drive.

That is, if you mount the destination drive, and SD starts cloning something to it, you may have problems if you try to run DW on that drive to repair it.

Here’s the issue:

Source drive S, and Destination drive D

User wants to have DW repair drive D.
Drive D is also the target of an automount which clones S to D.

Drive S has files A, B, C, D and E.
Destination drive D has files A, B, F and Q.

User inserts D
SD clone starts and User cancels clone.

DW looks at drive D, and sees A, B, F and Q.
DW unmounts the drive to work on it.
DW creates a replacement directory listing A, B, F and Q… remounts drive D, and then pauses. DW does NOT write the directory, because it’s waiting for the user to OK it.
Seeing that D has remounted,  the auto-clone kicks in and SD copies drive S to drive D.

here’s the crux of it:

after the SD clone, D now has files A, B, C, D and E. (not A, B, F and Q, which is what DW thinks it has)
User says to DW, “Yep, install the new directory.” and DW dutifully replaces the directory to say that D has files A, B, F and Q.

Drive D directory is now totally hosed.

 
There is basically no way around this except to start up SD and turn off all the auto-clone scripts and then quit SD before you run DW.. Now you can run DW without issues… just remember to re-enable the scripts in SD after DW is done.