SuperDuper dev : Apple blocks 3rd party creating bootable MacOS

Topic

New Reply

https://www.shirtpocket.com/blog/index.php/shadedgrey/youre_a_mean_one/

macOS 15.2 was released a few days ago, with a surprise. A terrible, awful surprise.
Apple broke the replicator. Towards the end of replicating the Data volume, seemingly when it’s about to copy either Preboot or Recovery, it fails with a Resource Busy error.

In the past, Resource Busy could be worked around by ensuring the system was kept awake. But this new bug means, on most systems, there’s no fix. It just fails…

To put it bluntly, this sucks…

1 user thanked author for this post.

BobbyB

Reply | Quote

Replies

macOS 15.2 Sequoia backup bug(s) affecting Time Machine, CCC, and more

One or more backup bugs in macOS 15.2 Sequoia is affecting Apple’s own Time Machine utility, as well as third-party apps SuperDuper and CarbonCopyCloner.

Initially the problem appeared to affect bootable backups only, but it now appears that it is either more general than this, or there is more than one bug affecting Mac backups …..MacOS 15.2 breaks Time Machine backups. A friend had his entire backup history blown away by Time Machine….

* If not using Time Machine, SuperDuper or CarbonCopyCloner, what’s left ?

Reply | Quote

macOS 15.3 fixes backup bugs affecting multiple apps

One or more backup bugs in macOS 15.2 Sequoia is affecting Apple’s own Time Machine utility, as well as third-party apps SuperDuper and CarbonCopyCloner…

Synology said that the same issue is impacting bootable backups to its NAS systems..

https://www.askwoody.com/forums/topic/superduper-dev-apple-blocks-3rd-party-creating-bootable-macos/#post-2744959

Reply | Quote

https://www.shirt-pocket.com/blog/

Happy New Fix!

Just a quick post: macOS 15.3 is now out, and with it, a fix for the broken replicator.

As such, macOS copying will work again with Erase, then copy backups. No update to SuperDuper is necessary (but feel free to install our v3.10 Beta 2, below).

Note that this does not mean boot from the copy will work in all situations (but, again, we have no control over that). But at least the copy can be made without (this) failure occurring.

Thanks for your patience as we waited for the fix from Apple. I know I’m relieved that I (hopefully) will no longer be bombarded with support because of it!

Reply | Quote