{"id":37926,"date":"2022-12-16T14:30:32","date_gmt":"2022-12-16T19:30:32","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=37926"},"modified":"2022-12-16T14:30:32","modified_gmt":"2022-12-16T19:30:32","slug":"superduper-3-7-1","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2022\/12\/16\/superduper-3-7-1\/","title":{"rendered":"SuperDuper 3.7.1"},"content":{"rendered":"

Dave Nanian<\/a>:<\/p>\n

In Ventura, on some systems, we’ve seen some cases where, post-replication (“Erase, then copy” in Big Sur and later), the destination volumes wouldn’t always re-mount. Sometimes an error would occur (referencing the ‘bsd’ info), sometimes not. When these failures occur, Apple’s replicator has also replicated the source volume name, and due to the error, we didn’t get a chance to rename it back to what’s expected.<\/p>

Anyway, it was annoying to you and (because we hate things like this) us. So we’ve been working for the last month or so to try to find a way to fix this…and I’m happy to say we have.<\/p>

[…]<\/p>

We’ve found the key needed to get the startup items to say something more sensible, and so now they’ll say “SuperDuper!”—please don’t turn them off! If you do, your schedules will not work.<\/p><\/blockquote>\n\n

Previously:<\/p>\n