[dnanian]

Hi, dirt farmer.

The backup drive naming issue has to do with Aliases. Aliases contain the name of the volume, as well as the path and name of the file. So, when one is used (resolved), it first tries to find the volume it "points to", then the path, then the file.

If the backup drive is named differently than the source, and is available when the alias is resolved, it will point to the file on the original drive instead of the equivalent file on the backup.

If, however, it's named the same, the alias will preferentially resolve to the first volume with the name -- the boot volume.

So, it's not so much a problem when you're backing up, but when you decide you want to boot from the backup.

Regarding copying Disk Warrior: we've never seen a case, in all the time SuperDuper! has been out, where a file that should have been copied wasn't copied. I can't explain what you've seen, but if you'll send your SuperDuper!.log to support, I'll try to see if there's a a potential explanation in there.