It is one of the most popular backup and sync tool among Mac users, even if it is paid software. Just be sure you set up the Synchronizer docs properly so you're not overwriting.As it states in official website, ChronoSync is a complete and all-in-one solution for file synchronization, backups, bootable backups and cloud storage. I also assigned a keyboard shortcut (on Mac) via Sys Prefs > Keyboard > Shortcuts > App Shortcuts for ChronoSync to run the sync (menu item Actions > Synchronize) so I wouldn't even have to cmd+tab over to ChronoSync, then cmd+right to start the sync. Disable Summary under the Container Options section because I only care if it fails and don't want to interact with the UI if I don't need to. I'd disable the "secondary" backup if it wasn't connected, but it's not necessary since it'll error out if it fails anyway. This is basically a list of Synchronizer files to run, sequentially ("hot" drive always takes precedence). Then, create a new container document and place both ChronoSync Synchronizer documents into a Container document. Save both documents to my session folder (for no particular reason other than to prove that I set them up correctly) Options > Automatic Retry before Handling Errors checked.
Chronosync prune archives archive#
Both are mirror left to right, archive deletions checked. One to the "secondary" external drive or server (depending if I was on location or in studio)īoth have the source as the shooting/internal/"master" folder. I'd always set up two Synchronizer documents- since I would be leaving set with three copies of the job. (Another reason why I don't constantly sync, and only a few key times a day.Īlso bio-directional is just asking for trouble IMO. If this happens, then you Sync left>to>right, poof- files gone. And so your files are on the backup drive and not the computer. incorrectly dragged to your Session Favourites. Although hard to do, the last thing you want to do is mindlessly change direction of the sync, and KEEP SYNCING multiple times the wrong way.īeware also of accidentally starting to write information straight onto the backup drive (for e.g., a misplaced New Shot Folder quickly made on the backup session, and not the original copy on the computer. The biggest thing I guess to note is to allow time to visually make sure you've looked at what you're syncing, where it's going, and what Chronosync has done after syncing. I'll maybe do a backup at around 10am (once we've done a shot or 3).definitely one during lunch, then maybe one again at around 3pm and obviously once at the end of day. 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.
Chronosync prune archives manual#
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.
0 kommentar(er)
