You know it's been a while since you last released a Beta when you don't quite remember the rhythms of the process.
But, it doesn't take long for muscle memory to kick in... and I'm happy to say that it's going really well. A lot of that is due to you: thanks for your support, encouragement and reports of both success and, occasionally, failure.
To deal with the latter (and celebrate the former), here's v3.5 B2.
A few things to mention as we continue this process:
- Make sure you have "Check for Updates" turned on in our Preferences. You may have turned it off if you were using the v3.2.5 workaround: it's time to turn it on again, since that's how you'll get Beta updates.
- Some users were confused by the macOS 11.4 Beta requirements. 11.4 is only required for M1 Macs. Intel Macs work fine with SuperDuper under all versions of Big Sur.
- Startup volumes will often not show up in the Startup Disk Preference Pane in System Preferences under Big Sur. This does not mean the drive isn't bootable—it's a weird bug in Big Sur.
To start up from the backup, use
Option+Power On
on an Intel Mac, or hold down thePower
button when powering on with an M1 Mac.If you do this, you'll note that the Mac's regular drive doesn't appear in the startup disk preference pane...but the backup drive does! It's weird. But the backup is OK! You can breathe!
- If you only made a Smart Update, and didn't start with an Erase, then copy backup, you'll note that your backup drive seems "empty". That's because you're looking at the "empty" System volume...and the Data volume is mounted by the OS as "no browse"—basically, it doesn't show up readily in Finder.
It's still there, though. Use Finder's Go To Folder, in the Go Menu, to open /Volumes and you'll see your Data volume.
For less stress—and who doesn't want less stress?—start with an Erase, then copy backup.
- We've actually figured out how to get at least a little useful information out of the weird errors system tools produce:
EILSEQ -> "Illegal Byte Sequence"
— Dave Nanian (@dnanian) May 3, 2021
That, generally, means "APFS Container Corruption".
Easy as pie. All errors should be decimal numbers that need to be converted to hex and byte stripped, then looked up in a file, to be useful.
For Beta 2 we've addressed a few things and polished some others: it's a relatively minor update. Details are in the Revision History, but to highlight a few things:
- Backup on Connect no longer runs over and over if you use Erase, then copy on Big Sur. This had to do with some very low-level changes to some Big Sur APIs that messed with our code that detected whether we were already running a copy for that volume.
The bug was useful for testing a zillion back-to-back Erase, then copies, though, so there's that. Yeah! We meant to do that! Sure!
- Erase, then copy was using
asr
to copy Catalina, which was unintentional. It now does the same thing v3.3.1 did. - Send to Shirt Pocket was failing for users in all versions of SuperDuper due to an locally cached response of a value that had been updated on our server. This turned out to be rather interesting, and frustrating, because we don't have a way of "fixing" old copies...although they will "fix themselves" over time...anyway, it won't happen any more in v3.5 B2 and later.
That'll about do it. Enjoy the new version, and thanks for the emails and tweets!
Thanks, again, for using SuperDuper...we look forward to your comments.