![]() By rule, I maybe do a quick test-back up at the start of day (of an empty session) then check the copy. I find the more you 'move files', the more likely somethings going to go wrong. I wouldn't exactly run the sync after every shot though. been assisting and DT'ing for about 6 years. I've never had any problems with Chronosync since I first moved my backup workflow to there (from manual drag and drop backups) a couple of years ago. If you accidentally delete files, it gets moved to the trash anyway, and needs another step of emptying trash to properly lose the files. You can then do a visual check-sum of your data at the end of day, and make sure it all adds up and is copied the same. This way, my backup drive is an exact copy of the session as on the master/computer. I also Synchronize deletions, with the "when Deleting files" set to Trash. Thank you for simplifying the process of backing up my iMac.I too Mirror Left-To-Right. I truly appreciate all of the hard work you've put into developing this valuable utility. I had my backup setup and scheduled in about 15 minutes and I didn't even need the Help file.Ĭan you do it on a Mac? Yeah, but how? Install third party apps to work with Time Machine? Or run scripts using Terminal? Uuuuuuhhh. It's a piece of cake to do that on a Windows PC using a batch file and the Task Scheduler, but even that is not as simple as the ChronoSync process. I just wanted to be able to select the files I want to back up and then schedule the process at a time of my choosing, which can't easily be done on a Mac. I've only been using it for a few days and feel I've got my money's worth out of it already. This software is awesome easy to use, doesn't bog down my iMac (like Time Machine used to), it's just a rock solid product in my opinion. I downloaded the trial version of ChronoSync a couple of days ago and I didn't need the 15 day evaluation period to make my decision. Fixed a bug that could cause a crash on application launch if a file helper’s associated application was removed from the system.Fixed a bug whereby the bootable blacklist was being applied to a target that mreferenced the root level of any volume.Fixed a bug whereby an Archive could not be relocated to a folder on the active Data volume.Fixed a bug whereby removing a rule from an expanded rule group could cause a crash.Added the ability to alter iCloud application container collection behavior via plist msettings.Fixed a problem that could cause -2070 errors when copying files with no creation dates between HFS+ and APFS filesystems.Updated/added a variety of readiness warnings to deal with Data Volume Backup and.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.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.
0 Comments
Leave a Reply. |