Re-backing up a session as you edit a job
Shoot, return to studio, download cards, immediately backup the shoot so I have 3 backups.
Edit shoot - rate files and share FPO's with client.
Backup.
Tone/grade/process files.
Backup.
As the RAW files are already on the backup drives, I don't need to back those up, but exactly what files do I need to backup and what's the best way to do that?
Thanks!
-
I've moved this to the workflow forum as it's a bit better suited there.
Back to your question though. Presuming you're working in a session, and as you've made no mention of EIPs or XMPs we'll assume you have the "standard" session file hierarchy of raw image directory with CaptureOne sidecar-containing folder. Any work that you do in Capture One, from rating/tagging to tone/grade/etc, is written to the .cos files within that sidecar folder; in [raw image directory]/CaptureOne/Settings/Settings110 (or 100, or 90, based on Capture One version). So, in essence, those are the only files that you'd need to update if you want to back up "your work" outside of the raws.
If you're editing by moving files around in albums/smart albums, you'll need to back up the .cosessiondb as well.0 -
I either shoot directly into the laptop and make a periodic backup during the shoot (every 30 minutes or less, depending on the job) or if I'm shooting on cards I copy them on location to my laptop and also do backups there.
When I return to my office I copy the files to my desktop and make another copy to my network storage (which also does a backup of it own).
Then I edit the session on the desktop or laptop (depends on where I need to be) and make backups of the editing process to an external SSD (fast enough not to slow things down but secure enough not to endanger anything and yet mobile enough for any purpose).0 -
Why not use a program such as chronosync that mirrors the files from the source to the destination? When you make edits or move files and the .cos and/or.cosessiondb files change, re-syncing the drives after your initial sync will copy the updated .cos and/or.cosessiondb files as well as any variants or processed photos you've added. 0 -
Because then it's not a backup, then it's a mirror image.
A backup isn't just used to prevent data loss but also data corruption. If a files gets corrupted that will mirror over and the "backup" would be affected as well.0 -
Correct you are, but doesn't it seem like mirroring is the solution that the the OP is searching for? Mirroring will update only the .cos & .cosessiondb as he/she makes the edits in Capture One and the .cos & .cosessiondb files change. Staying within the Capture One workflow the RAW files themselves will not be mirrored after the initial sync seeings how they are not changing, unless they are moved. Please correct me if I am wrong about that.
In Chronosync if a file has been changed and re-synced the old version goes to the archive folder where it can be restored.0 -
OP here. Yes, the RAW files are already on the backups and shouldn't be altered. To prevent copying over any accidental corruption that may occur when working on the working files, it may be best NOT to include the RAW's in the session Capture folder in subsequent backups? I believe it's possible to set that in Chronosync, but wondering how complicated it is to do that (I'm a believer in keeping things as simple as possible - complexity gives more opportunities for mistakes to happen). 0 -
Just came across this post after thinking through some of my processes. I use Sessions but pack as EIP, recognizing that the nature of this means that I need to backup the actual images and not just the adjustments. I'm examining my approach. I will always stay in Sessions; Catalog is not ideal for me. Yet I am inclined to stay with EIP , since losing sidecar files can be a frustrating experience.
I'm wary of automated backups like Chronosync, admittedly primarily because of my unfamiliarity.
I am aware the thread is quite old now—any updates or input given more recent software developments?
0 -
Jim Tillman - the way that sessions work is basically the same it was when this thread started. The best backup of a session is a copy of the whole session folder (with its subfolders) somewhere else whether that is by just copying it, or by getting a backup program to do it for you. I take the view that it is essential to have regular system backups anyway, which backs up my sessions as well as my emails, Word documents, and everything else that is stored on my computer. So I am using Mac's Time Machine app daily, and also occasionally using Carbon Copy Cloner as a further safety net.
I see no particular advantage of using EIPs as a matter of course, though they are obviously extremely useful for transferring edited images between one Capture One user and another. But if you like using them, do so. The only downside I can immediately think of is that they are not readable by any other software.
Ian
0 -
Thanks for your reply, Ian. I've been a C1 user for a long time now for my commercial work, and remain a faithful user. Because I've upgraded many times along the way, I've been most comfortable with EIPs since they are backward compatible, easily imported into other C1 sessions, and, again, am wary of sidecars going... well, sideways :-) at times.
I'm not terribly concerned with the lack of readability although that is a good point to make—thank you. It's possible that there could be an instance where I'd need to do otherwise, although there's an actual benefit to having images be unreadable by others if you want to control your output more deliberately.
Re backup, I have mirrored copies that I verify (spot check) manually. My output hasn't been so large that I required automation, but now that I'm shooting and editing my kid's sports games I may have to rethink that, given the volume of images that sometimes result. I know a coupole sports shooters that use Photo Mechanic, but don't really want to start learning a whole new workflow.
Thanks again for your input!
0 -
ChronoSync is very good, relatively inexpensive, and is very good at logging everything it does. It can be run manually or on a schedule.
If you are courageous enough to learn terminal commands you can also look at rsync. It has been around for decades and is very reliable. The version that comes with macOS is pretty dated because later versions have a different open source license that Apple doesn't want to comply with. You can get the latest rsync using a tool called "homebrew" which is a sort of package manager for open source tools on your mac. That's how I get it.
0 -
I've been most comfortable with EIPs since they are backward compatible
... until you create an EIP for an image that has adjustments using a tool that didn't exist in an earlier version, I suppose.
Ian
0
Post is closed for comments.
Comments
11 comments