

- Chronosync bootable backup update#
- Chronosync bootable backup archive#
- Chronosync bootable backup full#
Added logic to detect certain types of fsEvent database problems associated with updating fsEvents on the same volume from different OS versions Modified the Bootable Backup and Data Volume backup list of automatically excluded items Added the assertion that SmartScan on macOS 12, Montery, requires admin access
Chronosync bootable backup full#
This supports full backup of just the 'Data' portion of macOS 11, Big Sur, and newer versions of macOS. Added Data Volume backup Operation and Setup Assistant. Fixed a bug whereby changing target options would not necessarily force the readiness state of the synchronizer to be recalculated Fixed a bug whereby a copy task invoked by the synchronizer could conceivably report the wrong error message when an error was reported to the user Fixed a bug whereby the target’s allowSmartScan property was not factored in when determining if a specific target should be checked when testing for admin access
Chronosync bootable backup update#
The bug was introduced after the first update to v10. Fixed a bug in the volume info cache whereby it wasn’t really collecting information about local volumes. Fixed a bug whereby the Data Volume Assistant would not set the destination target properly if it were erased & renamed as per user settings We now force-unmount it prior to invoking ASR Fixed a bug whereby running ASR with the destination volume mounted would sometimes cause ASR to fail because it couldn’t unmount the volume. The Amazon S3 connection profile editor now allows larger part sizes to be specified a bug whereby a Sync Task would not properly disconnect from targets upon close in certain instances

Chronosync bootable backup archive#
a bug whereby changing the location of the Archive was not properly recognized a bug whereby permissions were incorrectly set for parent folders of the Archive Modified how the Readiness Manager recalculates the readiness state to fix several erroneous readiness messages Disabled caching when using non-Carbon APIs Added the ability to alter API behavior when accessing AFP, SMB and HFS targets via plist settings Fixed a crash that could potentially occur when creating a New Sync Task Document Fixed a bug in the Backup Multiple Folders assistant that could lead to a crash if the assistant failed to create any destination folders that it was asked to create

Fixed some cosmetic problems on the last panel of several Assistants when running on macOS Ventura Fixed some UI problems on the Options/Archive Settings panel whereby some custom archive location controls weren’t being disabled when archiving was disabled Fixed a bug whereby a Readiness Error would prevent synchronization if a previously established custom archive location was not available, even if sync settings had been changed so that no archiving was being performed Fixed some localization problems in the Bootable and Data Volume assistants that were claiming volumes need to be HFS+ formatted Fixed a problem that could could cause changes to a volume’s “Ignore Ownership” setting to fail Fixed a bug that could cause unreported failures when attempting to change an archive’s location to a volume with a different “Ignore Ownership” state Hardened the AWS S3 Storage Provider to better deal with lost connections in the middle of a file transfer Added logic to ensure that some maintenance on a remote sync target connection is only performed in the main thread, in an attempt to eliminate an obscure crash Changed the way lost agent connections are dealt with when multiple copy threads are active, in an effort to increase stability Added a Readiness Error to prevent bootable synchronizations over ChronoAgent connections when running macOS 11 or later on the destination Added a separator to the sync task log when relocating an archive
