Joe Shapiro wrote:Whatever solution is chosen, it'd be important that the system does it for you rather than you having to know and remember to do it yourself.
I have a long message elsewhere that details how to upgrade to a new version of Resolve. In the Top 3 things on that list, I included: "Back Up Your Project Database" and "Back Up Your Boot Drive" in case the user has to revert to the previous version of Resolve. I agree with Walter that making a duplicate of the Project Database is very helpful before an update.
There's at least 50 or 60 things where you basically have to use your brain and think before jumping off the cliff, to avoid disaster. I try not to expect that the software will protect me -- I try to take responsibility for myself and just know going in I have to make it work. That's pretty much my job.
I think there's been at least 3 database changes from 17 to 18, so it's not a simple process. We do routinely export the last 10-12 projects we worked on as DRPs so we have a fallback in the unlikely event anything fails, but we haven't had to use them (yet).