{"id":30576,"date":"2020-11-03T20:02:45","date_gmt":"2020-11-04T01:02:45","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=30576"},"modified":"2020-11-03T20:02:45","modified_gmt":"2020-11-04T01:02:45","slug":"carbon-copy-cloner-5-1-22","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/11\/03\/carbon-copy-cloner-5-1-22\/","title":{"rendered":"Carbon Copy Cloner 5.1.22"},"content":{"rendered":"

Mike Bombich<\/a>:<\/p>\n

\n

CCC 5.1.22 is officially qualified for macOS Big Sur.<\/p>\n

[…]<\/p>\n

Thanks to these massive system changes and some bugs in the version of Big Sur that Apple intends to ship, nobody can make a proper copy<\/strong> of the System volume right now<\/em>, not even with Apple’s proprietary utilities.<\/p>\n

[…]<\/p>\n

The changes in Big Sur definitely present some new logistical challenges, but yes, you can have a bootable backup of macOS Big Sur. Right now you can install Big Sur onto your CCC backup to make it bootable, and in the future we’ll use Apple’s APFS replication utility (ASR) to clone the Big Sur System volume. Apple has assured us that they are working towards fixing the problems in ASR that prevent it from cloning the Big Sur System volume.<\/p>\n

[…]<\/p>\n

To put it plainly, we spend about a quarter to half of our year just making CCC work<\/em> with the next year’s OS.<\/p>\n<\/blockquote>\n\n

See also: the known<\/a> issues<\/a>.<\/p>\n\n

Previously:<\/p>\n