{"id":27529,"date":"2019-12-11T16:54:30","date_gmt":"2019-12-11T21:54:30","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=27529"},"modified":"2020-07-03T16:50:47","modified_gmt":"2020-07-03T20:50:47","slug":"superduper-3-3-for-catalina","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/12\/11\/superduper-3-3-for-catalina\/","title":{"rendered":"SuperDuper 3.3 for Catalina"},"content":{"rendered":"

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

\n

In order to replicate this new volume setup, system backups of APFS volumes must be to APFS formatted volumes. SuperDuper automatically converts any HFS+ destinations to APFS volumes for you (after prompting), so you won’t have to do anything manually in most cases.<\/p>\n<\/blockquote>\n

That’s too bad given APFS’s poor performance on spinning disks, which is what I mostly use for backups.<\/p>\n

Those two volumes are further linked together with “firmlinks”, which tunnel folders from one volume to the other in a way that should be transparent to the user. But they can’t be transparent to us, so we had to figure out how to recreate them on the copy, even though there’s no documented API.<\/p>\n

[…]<\/p>\n

You can’t turn an already encrypted APFS volume into a volume group. As such, you’ll have to decrypt any existing bootable volumes.<\/p><\/blockquote>\n\n

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

\n

On some user systems, Full Disk Access doesn’t take after install, and they have to restart after installing the new version. This is because our bundle ID has changed due to notarization and the OS doesn’t handle it well.<\/p>\n

[…]<\/p>\n

In some circumstances, ownership wouldn’t be properly enabled for the system volume of an external Catalina volume group, which made the backup not boot. […] I could go into detail on the latter problem, but rather than bore you, I’ll refer you instead to this old post from 2005<\/a>[…]<\/p>\n<\/blockquote>\n\n

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

\n

We’ve got a few users whose systems are in a bizarre state where the loader is outputting […] when we run certain system command-line tools.<\/p>\n

[…]<\/p>\n

We also added a diagnostic that detects a rare situation where a user’s system has broken scripting tools (like a bad Perl install), which can cause problems.<\/p>\n<\/blockquote>\n\n

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

The unexpected part is that just before the beta, we made a change to the installer to try to improve our workaround for systems that required rebooting post-install to make Full Disk Access work. After we made the change, we didn’t re-run the full suite of tests because we (incorrectly) thought the change was isolated to the install process.<\/p>

However, it was made in a runtime element that was shared with the way we executed bless<\/code>.<\/p><\/blockquote>\n\n

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

\n

With volume groups, though, there are two potential volumes to mount...but keychain passwords might be under either the Data<\/strong> volume or the System<\/strong> volume, depending on what the user does.<\/p>\n<\/blockquote>\n\n

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

\n

Eject would sometimes not eject both volumes of a volume group.<\/p>\n

[…]<\/p>\n

Some people were impatient and didn’t realize HFS+ to APFS conversion might take a while! We now tell them to get a tasty beverage!<\/p>\n<\/blockquote>\n\n

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

\n

I’m happy to announce the release of v3.3 of SuperDuper, our fully Catalina-compatible version: happier, perhaps, then even you<\/strong> are in reading the news. It’s available via the normal update mechanism, or by downloading it from the web site<\/a>.<\/p>\n

[…]<\/p>\n

The whole idea of the new version is, if we did our job right (and I think we did), things should just work the way you expect them to. […] But despite that, SuperDuper is doing a lot more things.<\/p>\n<\/blockquote>\n\n

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

There’s one remaining issue for 10.10 and 10.11 users: Erase, then copy<\/strong> backups are failing due to some unexpected “volume transformation” events that are occurring. When we validate the result, we’re being quite cautious, and we’re not seeing what we expect, so we fail the copy.<\/p><\/blockquote>\n\n

Previously:<\/p>\n