Any danger of corrupting Database or Projects with backup?

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

johngwheeler

  • Posts: 85
  • Joined: Sat Aug 03, 2019 11:00 pm
  • Location: Sydney, Australia
  • Real Name: John Wheeler

Any danger of corrupting Database or Projects with backup?

PostFri Apr 09, 2021 6:06 am

I'm just recoveringing some projects after a computer crash, and have been considering improvements to my backup workflow.

I use a combination of DropBox and Google Backup & Sync on a Mac and noticed a curious warning from the latter when trying to add the Davinci Resolve Disk Database folder as a backup source. It gives a warning:

'Syncing "Resolve Disk Database" isn't recommended

If you make changes to "<path to my Database folder>" while syncing, applications on your computer may stop working'

Is this because of some generic warning about updating what Google Backup thinks are "system files" (inside the user/Library/Application Support folder)?

Is there really any danger of the Google Backup sync process corrupting the Resolve database?

Thanks!
Offline

Jim Simon

  • Posts: 30221
  • Joined: Fri Dec 23, 2016 1:47 am

Re: Any danger of corrupting Database or Projects with backu

PostFri Apr 09, 2021 1:59 pm

I recommend using the Project Manager to Backup databases and export .drp's of active projects.
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

johngwheeler

  • Posts: 85
  • Joined: Sat Aug 03, 2019 11:00 pm
  • Location: Sydney, Australia
  • Real Name: John Wheeler

Re: Any danger of corrupting Database or Projects with backu

PostSat Apr 10, 2021 3:45 am

Jim Simon wrote:I recommend using the Project Manager to Backup databases and export .drp's of active projects.


Thanks for the suggestion. Both DB backups and project exports are manual tasks though, aren't they?

My interest in backing up to Google Drive is to avoid having to think about manual backups.

I do have automatic schedule project backups enabled though, and backup the whole "Resolve Project Backups" folder with Google Backup & Sync.

Out of interest, what is the difference between a project.db.<timestamp> backup and an exported .drp file?
Offline

Jim Simon

  • Posts: 30221
  • Joined: Fri Dec 23, 2016 1:47 am

Re: Any danger of corrupting Database or Projects with backu

PostSat Apr 10, 2021 1:43 pm

johngwheeler wrote:Both DB backups and project exports are manual tasks though, aren't they?
That is the recommendation.

Do it manually.
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline

Jim Simon

  • Posts: 30221
  • Joined: Fri Dec 23, 2016 1:47 am

Re: Any danger of corrupting Database or Projects with backu

PostSat Apr 10, 2021 1:45 pm

johngwheeler wrote:what is the difference between a project.db.<timestamp> backup and an exported .drp file?
The first is a backup version created by Resolve for use when the project is already open.

The latter is a stand alone project file which can be Imported into any database from the Project Manager.
My Biases:

You NEED training.
You NEED a desktop.
You NEED a calibrated (non-computer) display.
Offline
User avatar

Uli Plank

  • Posts: 21635
  • Joined: Fri Feb 08, 2013 2:48 am
  • Location: Germany and Indonesia

Re: Any danger of corrupting Database or Projects with backu

PostSun Apr 11, 2021 2:07 am

Now that the cat #19 is out of the bag, test it as much as you can and use the subforum.

Studio 18.6.6, MacOS 13.6.6, 2017 iMac, 32 GB, Radeon Pro 580
MacBook M1 Pro, 16 GPU cores, 32 GB RAM and iPhone 15 Pro
Speed Editor, UltraStudio Monitor 3G
Offline

johngwheeler

  • Posts: 85
  • Joined: Sat Aug 03, 2019 11:00 pm
  • Location: Sydney, Australia
  • Real Name: John Wheeler

Re: Any danger of corrupting Database or Projects with backu

PostSun Apr 11, 2021 9:28 am

Jim Simon wrote:
johngwheeler wrote:Both DB backups and project exports are manual tasks though, aren't they?
That is the recommendation.

Do it manually.


Thanks, will do!

Jim Simon wrote:
johngwheeler wrote:what is the difference between a project.db.<timestamp> backup and an exported .drp file?
The first is a backup version created by Resolve for use when the project is already open.

The latter is a stand alone project file which can be Imported into any database from the Project Manager.


That makes sense....thank you.
Offline

johngwheeler

  • Posts: 85
  • Joined: Sat Aug 03, 2019 11:00 pm
  • Location: Sydney, Australia
  • Real Name: John Wheeler

Re: Any danger of corrupting Database or Projects with backu

PostSun Apr 11, 2021 9:45 am

Jim Simon wrote:
johngwheeler wrote:Both DB backups and project exports are manual tasks though, aren't they?
That is the recommendation.

Do it manually.


I'm doing this as well, and it's good advice.

I'm still curious about the Google Backup warning.... I imagine the files in the database folders change any time a project is saved (because the project.db files are inside the "/Users/<user>/Library/Application Support/Blackmagic Design/DaVinci Resolve/Resolve Disk Database/Resolve Projects/Users/guest/Projects".

I can't really see why syncing the project.db to Google Drive would be any more at risk of corruption as any file that is changed during use.
Offline

johngwheeler

  • Posts: 85
  • Joined: Sat Aug 03, 2019 11:00 pm
  • Location: Sydney, Australia
  • Real Name: John Wheeler

Re: Any danger of corrupting Database or Projects with backu

PostSun Apr 11, 2021 9:46 am

Uli Plank wrote:This may be helpful:
https://www.dropbox.com/s/9i3x06004w0jp ... d.pdf?dl=0


Thank you; this is a good introductory guide to how it all works. Saved to my list of "how-to docs"!

Return to DaVinci Resolve

Who is online

Users browsing this forum: Google [Bot], Michachacha, panos_mts and 182 guests