-
Resolve DB best practices?
I’m a little late to the Resolve bandwagon, but now that my expansion chassis is in place and my first commercial project is out the door, I’m wondering about how to best organize my on-going workflow. Particularly in the area of DB management.
In Color (which I used for years), I had a practice of keeping all the folders and project files for a single project separate and unique. That helped with my backing up strategy (if you could call it that). I always knew that I could go to my NAS archive folder and retrieve 100% of a color project from one place for adjustments asked for 1 year after original delivery. And, I didn’t have to wade through a lot of projects I didn’t want to see in my day-to-day.
So now with DaVinci Resolve, its all in one DB, and I’m wondering what other people have decided makes sense over time.
DB – Project relationship
Do you keep all your projects in one mega-DB?
Or do you create a new DB for each new substantial project?It seems to me that one-large DB (as recommended in the manual) is highly risky. What if the DB gets corrupted and you put a years worth of work at risk. Yes, I know there can be backups to restore from too. But the -idea- scares me.
So for now, as I start my next large Resolve project (a feature), I’ve created a new DB. I’m wondering what the downside of this is.
Backups
Until I found Rohit’s PDF on backing up the DB, I had been using the project export function in the Browser at the end of each day to create a interim backup. As long as the exports are easy to import again, it should all be fine right? I haven’t tested that though, which makes me nervous.Now, I know how to backup the DB thanks to Rohit, but again, I haven’t tried to do a restore to verify it works as hoped. I’ll have to test this before I start the grade on my feature project.
The auto-save function in the setup window has not been very kind to me so far. I set it up, see it occasionally work while grading. But when I go to the setup window expecting a long list of backups, it is empty. seems like a DB bug of some kind. (maybe the new 7.1.1 patch fixes this). But I definitely do not trust this feature yet.
It would be very helpful to know what other “one-man-shops” are doing in the areas of DB management and backups, and what the track record of guaranteed recoverability is so far.
Cheers,
Paul_______________________
El Mundo Bueno Studios
Film * Audio
http://www.EMBstudios.com
Emeryville, CA
_______________________ -
11 Replies
-
I would just export this one project to all other project files and back up all stuff together.
I mean not just sequence but File > export
this has been talked about here in the forum.
—
Margus
-
Hi, one of the reasons Resolve is so powerful is the way we use the database. For many users, one DB could be used for many, many months, without issues. In fact some of our long serving customers make a point of creating a new one every six months, just to make finding older project quicker. I have seen others more than a year old.
Certainly having 10’s of feature films in one DB is going to make it a mighty big file and if you have half dozen commercials a week you are going to grow the DB pretty quickly too. Big DB’s are slower than smaller DB’s no matter who make, uses or maintains them so its logical to create new ones from time to time. But you don’t need to for every project, nor every month.
If you are about to start an epic feature film, sure make a new DB and keep it separate from your other work. Some of the larger facilities in Hollywood do just that. But even they also don’t make a new database for every job so don’t think this is necessary for smooth operation.
Peter -
Where can one find Rohit’s PDF on backing up the DB?
-
An Additional question to this,
Where the hell does Resolve keep the database files?
I’d like to simply add it to things to backup…
Joseph Mastantuono
Online Editor – Colorist – Post Consultant
917.969.1583 -
“Where does Resolve keep the database files?”
I would also like to know the answer to that.
Craig Harris
Colorist – Vancouver, BC -
-
https://f1.creativecow.net/1538/resolve-backup
Christian Berg-Nielsen
Sement&Betong
postproduction
Norway -
Hey guys,
Reviving an old thread here.
Are there any advantages to backing up a database (as outlined in Rohit’s doc) as opposed to just exporting a project? The exporting/importing project (File>Export) function seems simpler and more straightforward.
And I apologize if this has been discussed. I did try searching, but couldn’t find a straight answer on this.
-Dave
-
Database backups also retain user and other settings.
Colorist | Online Editor | Post Super | VFX Artist | BD Author
-
Brilliant, thank you!
-Dave
Reply to this Discussion! Login or Sign Up