|Created on||2019-05-28 03:28:15|
|Files||ChronoSync.4.9.3.zip (89.24 MB)|
ChronoSync is an application for Mac, which can be used to synchronize or backup files and folders. Allows you to make a backup of the entire system as well, to create a bootable backup
With ChronoSync can sync or do a backup for most devices and directories, and all that can be connected to the Mac, including a folder on your Mac, other Macs, PCs and external drives.
- Fully customizable toolbar
- All settings are stored in separate files that can be edited at any time
- Synchronization in two directions
- drafting rules to filter the files by various attributes
- Compare files before sync
- Run a test to verify the results of synchronization before performing operations
- history of synchronization, which can be printed or saved to a file
- Automatic synchronization on a schedule
- Use AppleScripts to automate synchronization.
Intel, 64-bit processor OS X 10.8 or later
What’s New in ChronoSync 4.9.3 & ChronoAgent 1.9.2
Enhancements and Changes:
- Changed the algorithm for determining temporary file names to be less prone to natural filename collisions during concurrent copying tasks.
- Now handles any exceptions when obtaining attributes from an SFTP directory entry and treats this condition as a nondirectory entry (i.e. it just skips it).
- When a comparison helper is called, the sync target’s file manager is now used to obtain information about the files being compared.
- Now validates any relative alias object created and compares it against the original item to catch potential mismatches.
- Now only replacing the reference to the task document when modifying a scheduled item if it has actually changed.
- Improved memory management in the Backblaze B2 storage provider.
- Added logic to the sync task document loader so that it can better deal with potentially damaged task documents.
- Significantly reduced the size of the scheduler database and the overhead of loading/saving it.
- More efficiently instantiate scheduled items from the scheduled items database to handle potentially corrupt elements.
- Modified how the scheduled item database gets saved so that multiple changes made in quick succession are coalesced before saving.
- Reduced app activation overhead by no longer reconstructing the Templates contextual menu on every activation of the app.
- Updated the Trial Sync results window to clean up a path to an item before passing that off to a helper tool or external service such a ‘Get Info in Finder’ to ensure that the path represents the file object on the real target and not a snapshotted version of it.
- Now performs a sync history reset (retaining exclusions) after changing Package Handling, Sync Operation, and Sync Triggers on a previously synchronized task document to ensure all appropriate information gets collected and items are handled correctly on the next run.
- Changed the terminology used to identify Backblaze B2 application keys & account IDs to match the latest B2 terminology and to be consistent (i.e. English) across all languages.
- All the cloud service connection profile editors have had their authentication’s credential fields set to characterwrap instead of wordwrap.
- Added logic that ensures any excluded filepair does not have any other status set.
- Fixed a bug whereby the predefined AWS S3 endpoint strings were inadvertently translated in nonEnglish languages.
- The ChronoAgentLocalConsole.log file is now being rolledover automatically.
- Fixed some autolayout problems in the AWS and Backblaze B2 connection profile editors.
- Fixed some bugs whereby many commands were not properly setting the threadspecific error property when they completed.
- Fixed a bug that occurs when launching comparison helper applications in a manner that was incompatible with files residing on an APFS snapshot volume.
- Fixed a bug whereby an alias located in the immediate descendant of a resolved folder alias would not be resolved correctly.
- Fixed a bug that was affecting the synchronizer’s ability to identify selfreferencing aliases when ‘resolve aliases’ was in effect and the target currently referred to an APFS snapshot volume.
- Fixed a (harmless) bug that could result in wasted time and a guaranteed lowlevel error (and console messages) when trying to do Trial Sync or Sync Selection on an APFS snapshot.
- Fixed a bug in resolving an alias on an APFS snapshot.
- Fixed a bug whereby it was possible to convert an existing object that was marked as a symbolic link or directory to a regular file when updating attributes on Backblaze B2.
- Fixed a bug in the Backblaze B2 storage provider whereby it wasn’t always correctly identifying package files.
- Fixed a bug resolving an alias file where it was possible that it would resolve to a URL but a file pathname could not be extracted from the URL causing an exception.
- Fixed a bug whereby when presenting an error caused by enumerating folders in the file system, the object used to contain information about the error was volatile and could be corrupted by another thread that was preparing to present a different error likely resulting in a crash.
- Fixed a bug whereby marking a folder node for exclusion would release all children and setup a potential crash for any other code that has retained a direct reference to one of those children. This is possible in Trial Sync and syncselection scenarios.
- Added logic to the outermost node processing loop that checks each node’s exclusion state before attempting to process it to prevent unwanted operations and/or potential crashes.
- Fixed a bug whereby attempting to retry a failed deletion of a file on the destination would trigger an unrecoverable, infinite loop and potentially cause a crash or memory consumption.
- Fixed a bug whereby retry attempts would be performed on failed processing of nodes even if an abort condition were signaled.
- Fixed a bug whereby when editing a previously created “When independent volume mounts” scheduled item, a “Connect” message was not being sent to the independent volume specifier. Thus the volume would always appear as “Not available” in the user interface even though it was.
- Fixed a bug in the file system notification trigger that would not reliably start a live filesystem trigger after it was created.
- Fixed a bug in the file system notification trigger that would not reliably remove a live filesystem trigger after it was disabled or deleted.
- Fixed a bug whereby package merging between a source file system that supports millisecond timestamps (APFS) and a destination that doesn’t could result in failure to efficiently merge.