Shrinivas Ramani wrote:The way I understand it, This trade-off is up to the user, but making a backup and testing it before upgrading is a good recommendation for safety. Yet others backup DRP projects and preset/config files that they later restore on a different machine. Others may skip the separate backup-and-restore in favor of a literal folder copy for a disk database. Invoking the restore as part of this copy gives you that additional piece of mind on the integrity of the backup.īased on workflow, people may approach the first two steps (backup and restore) differently, using Resolve's tools, using postegreSQL or a clone-and-check process away from their main machine. The exact procedure depends on your workflow, but the main take-away is that if you have three copies of your data at the time of upgrade - one for upgrading to v17, one still compatible with v16 in the off chance you need to fall back to a v16 build, and a separate distinct backup file in case you end up upgrading both or rendering one corrupt on one of those rare occasions. Upgrade one of the two copies on the first startup of v17.back up > restore a copy of the v16 database.
0 kommentar(er)
