Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

best practices with chronosync

NN103450
Hi just wondering what the best practices with chronosync are / or backing up a session in general.

is it as simple as just selecting backup left to right and just synchronising after every shot?

Im not sure if its even possible but what if i accidentally downsized the files or they got corrupted would chronosync then overwrite the 'good' backup with the corrupted files. thanks for any help!
0

Comments

6 comments

Date Votes
  • Ken Bates
    I do a bi-directional sync since I sometimes work on the laptop and sometimes on the desktop. I also sync both the folder containing the catalog and the C1 applications settings (~/Library/Application Support/Capture One/). This not only ensures that your work environment is (mostly) the same on the two systems, but also backs up the backups you do in C1.

    That said, if you modify/corrupt/change a file on one system, ChronoSync will faithfully back it up to the other system. If you catch the corrupt/changed file in time, you can always force ChronoSync to copy the other direction or simply copy the file over yourself. Failing that, you can always go to the C1 backup in the above mentioned folder and at least restore the catalog.

    - Ken
    0
  • Corey Riggle
    I use Mirror left to right, seams to work best on macs, and connected servers.
    I also check synchronize deletions, you might experiment with archive replaced files, but I've never felt the need.
    I also check basic copy with verification under options.

    I've been working this way for a very long time and had many people under me using this method, we probably backed up a petabyte by now, never any problems.
    0
  • Daryl Orillaza
    Agree with Corey ^.

    I too Mirror Left-To-Right. I also Synchronize deletions, with the "when Deleting files" set to Trash.

    This way, my backup drive is an exact copy of the session as on the master/computer. 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.... If you accidentally delete files, it gets moved to the trash anyway, and needs another step of emptying trash to properly lose the files.

    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... been assisting and DT'ing for about 6 years.

    I wouldn't exactly run the sync after every shot though. I find the more you 'move files', the more likely somethings going to go wrong.... By rule, I maybe do a quick test-back up at the start of day (of an empty session) then check the copy... 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.

    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. 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.

    Beware 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... incorrectly dragged to your Session Favourites... I've done this before....). And so your files are on the backup drive and not the computer. If this happens, then you Sync left>to>right, poof- files gone. (Another reason why I don't constantly sync, and only a few key times a day.

    Also bio-directional is just asking for trouble IMO.
    0
  • NN103450
    thanks! will you leave the set with just one backup ? or copy it to photographers drive at end of day as well ? Ive just been using one backup drive but have heard some techs say common practice is to leave with 3 copies.

    also is standard lacie rugged good as a backup drive or do you use external ssd?
    0
  • Corey Riggle
    Setup chronosync with my advice from above, then go to File... Save as Default, then everytime you open chronosync it will be set with mirror left to right and verify....

    I like to backup very frequently. And I'll use chronosync to manage multiple backups throughout they day if I know someone is going to want to leave with a drive at the end of the day. That way it's a quick update instead of waiting for an entire backup so the AD or photographer can leave.

    I think 2 copies is fine, only 3 if someone else wants one. Also If it's a multiple day shoot, I'll take a backup home with me in case the place burns to the ground.
    0
  • Benjamin Liddle
    I'd always set up two Synchronizer documents- since I would be leaving set with three copies of the job.
    One to the "hot" external drive
    One to the "secondary" external drive or server (depending if I was on location or in studio)

    Both have the source as the shooting/internal/"master" folder. Both are mirror left to right, archive deletions checked. Options > Automatic Retry before Handling Errors checked.

    Save both documents to my session folder (for no particular reason other than to prove that I set them up correctly)

    Then, create a new container document and place both ChronoSync Synchronizer documents into a Container document. This is basically a list of Synchronizer files to run, sequentially ("hot" drive always takes precedence). 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. 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 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.

    Hope that helps. Just be sure you set up the Synchronizer docs properly so you're not overwriting.
    0

Post is closed for comments.