Backup Strategies

[Jeremy Garchow]

[Brett Sherman] “So far I just let it pick which version it wants to open, because I do not want to eject the drive or since then I wouldn’t get automated backups. I don’t want to rename folders as that will just get messy. I don’t suppose there is a way to force X to open the project from the original drive is there. Or exclude certain drives from X.”

I wouldn’t let FCPX simply choose what it feels like using as that and and will cause issues at some point.

Instead of backing up to the root level of the drive, backup to a folder called “FCPX_backups”.

This will hide the Events and Projects on the backup drive from FCPX and not cause any confusion.

If you ever need the backup files, then you simply restore the proper folder to the normal FCPX project path.

The manual has a section about this that might be worth reading.

Have a read here: https://forums.creativecow.net/readpost/344/16936

Jeremy

[Brett Sherman]

The problem is that even though I call it a “backup” drive. It really is a secondary drive that is often utilized. So to move it into another folder I think would be problematic. I’d always have to remember to put it back before syncing the drives again. And a backup system isn’t a backup system if you have to remember to do something.

I’m currently running backups with Versioner Pro. That can be my stop gap if anything goes really haywire. So far I’ve only had minor annoyances.

But I wish I had some more control over where FCP X puts the project/event and render files. My problem would be solved if I could store project/event files on my Mac HD and store render files on the media drive. Then there would be a single project/event file and I’d never run into conflicts. Not to mention I’d have a viewable library of projects without having to insert drives to figure out where I put something.

[Jeremy Garchow]

[Brett Sherman] “And a backup system isn’t a backup system if you have to remember to do something.”

Instead of pointing your backup to a root level, you point it to a folder. It’s not that hard and has the potential of saving your ass instead of playing with fire. If you read that other thread, the user lost an Event doing something very similar to what you’re doing.

[Brett Sherman] “But I wish I had some more control over where FCP X puts the project/event and render files. My problem would be solved if I could store project/event files on my Mac HD and store render files on the media drive. Then there would be a single project/event file and I’d never run into conflicts. Not to mention I’d have a viewable library of projects without having to insert drives to figure out where I put something.”

Yep.

But this would not backup the actual Event or Project files.

Make a feature request to Apple. It would be nice to split the render files out to a separate location.

[Oliver Peters]

You might look into this:

https://www.fcp.co/final-cut-pro/news/1041-backing-up-final-cut-pro-x-automatically-with-backups

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Bob Woodhead]

Chronosync will do TimeMachine-like backups of specific folders INTO specific folders. Have cake / eat too.

“Constituo, ergo sum”

Bob Woodhead / Atlanta
CMX-Quantel-Avid-FCP-Premiere-3D-AFX-Crayola
“What a long strange trip it’s been….”

[Brett Sherman]

[Jeremy Garchow] The thing is backing up to a separate folder doesn’t allow me to work with the backup drive which I do all the time. Now it might sound like a simple thing to just move the content out of the backup folder, but in reality what is going to happen is once in awhile I will forget to move it back. Then when I run my sync, it’s not going to backup any changes I’ve made on the Backup drive. I will not realize it until I don’t have both drives with me. And then I’ll be SOL. Not to mention it’s then going to have to copy duplicate versions of everything from the original drive to the backup drive.

Maybe I am playing with fire, but I don’t really see how I could lose everything because I’m running backups with Pro Versioner to a Dropbox account (basically similar to the Backups program Oliver Peters mentioned) Is there something other than the .fcpevent or .fcpproject file that can get messed up that I’m not aware of?

I also have a tertiary backup of events and projects using Synk 7 Pro that does exactly what Bob is suggesting.

[Jeremy Garchow]

[Brett Sherman] “The thing is backing up to a separate folder doesn’t allow me to work with the backup drive which I do all the time. “

I don’t want to tell you what to do, so I’ll tell you what I do.

A backup is just that, a backup. For me, it is not a working copy, it is not a check copy, it is a fail safe.

If the main system goes, the backup becomes essential. I do not use the backup as a main system.

[Brett Sherman] “Maybe I am playing with fire, but I don’t really see how I could lose everything because I’m running backups with Pro Versioner to a Dropbox account (basically similar to the Backups program Oliver Peters mentioned) Is there something other than the .fcpevent or .fcpproject file that can get messed up that I’m not aware of? “

There is a possibility that FCPX will get confused as to which group to use (the main or the backup). It is possible that something will get overwritten that you don’t want to get overwritten. Or you mistakenly made a change that isn’t recoverable.

FCPX is a completely different structure, and it has rules. As I mention, the manual pretty clearly lays it out:

https://help.apple.com/finalcutpro/mac/10.0.6/#verb6acb2fb

[Brett Sherman] “I also have a tertiary backup of events and projects using Synk 7 Pro that does exactly what Bob is suggesting.”

I am all for backups to the backups, but I don’t see how working from a backup as a main system, and copying the backup to the main system helps to keep everything straight.

[Brett Sherman]

[Jeremy Garchow] “A backup is just that, a backup. For me, it is not a working copy, it is not a check copy, it is a fail safe.”

I wish I had that luxury. Many times I need to have two editors utilizing the same drive at the same time. It’s not the same FCP X Project but some other media on the same drive. Or transferring cards for project B while working on a project A for a deadline. Or making a DVD of raw footage while editing the program at the same time. There many advantages to this system that I’m not willing to give up at this point.

The idea of the additional backups is to be able to go back in time to an earlier version if something does go haywire or goes missing because there are multiple versions of the fcpproject and fcpevent files stored.

We’ll see, maybe disaster will strike at some point and I’ll have to change my ways, but right now it has worked well and I’d lose too much efficiency by doing it Apple’s way.

[Jeremy Garchow]

Hi, Brett.

Using two drives is one thing, having two identical copies of FCPX databases is another.

I think you have workflow issues to solve, not a backup issue. if I were you, I’d look in to using sparse disk images. Watch here:

https://blogs.creativecow.net/blog/12309/1-setup-fcpx-on-air

Jeremy

[Brett Sherman]

My solution so far, is that I found an AppleScript to automatically mount a specific volume that is ejected. I have it scheduled to do that at night. Then the backup will run. Then in the morning I’ll eject the backup drive.

Messy. But it works.