I don't like to lean on ASR for general backups because it has some shortcomings and doesn't give any insight into its internal activity (e.g. Anticipating a world in which Apple continues to restrict access to APFS rather than grant it, though, we decided to invest a fair amount of time evaluating this functionality, and we've been beta testing it for the last 8 months.
#Chronosync definition full
Initially I dismissed this – I shouldn't have to use Apple's black-box utility to do my job, I prefer to take full responsibility for my backups. Last year at Apple's Developer Conference, Apple suggested that backup software could use Apple's "Apple Software Restore" (ASR) for cloning APFS volume groups. But hey, summer has arrived here in the northern hemisphere, so let's make some lemonade! Creating bootable backups on macOS 10.15.5 The impact of this bug is limited to the initial creation of a bootable backup. To be very clear – existing backups are unaffected, and this has no effect on CCC's ability to preserve your data, nor any effect on the integrity of the filesystems on your startup disk or your backup disk. The technical details of the bug are laid out below, but the short version is that we're no longer able to use our own file copier to establish an initial bootable backup of a macOS Catalina System volume. Special thanks to my team members for helping put this release together so quickly, the folks at Wordcrafts for a wicked-fast turnaround on these UI translations, and for several beta testers that helped us knock out some kinks along the way.Įarly last week we discovered an APFS filesystem bug in a beta of macOS 10.15.5. Choose "Check for Updates" from the Carbon Copy Cloner menu to get the latest version of CCC.
#Chronosync definition update
Update (May 29, 2020): This issue is now addressed in CCC 5.1.18, which is available for immediate download – CCC can make bootable backups of macOS 10.15.5. Rather than just hoping for a fix, we invested in a solution, and that solution puts us in a solid position for the next major OS. Every challenge opens up new opportunities, and that's actually how we're seeing this incident in retrospect. Update (July 16, 2020): Apple fixed the underlying OS issue described below in macOS 10.15.6, and the CCC 5.1.20 update puts our workaround on the back burner.
0 kommentar(er)
