manually updating the sqlite database to resolve issues such as database version errorsĪlso, be aware the if you are planning a temporary downgrade only (such as to resolve orphaned setting warnings) it’s probably best if you edit your jobs to disable any automatic scheduling.Generally this can be address by re-updating to the previous version or doing additional downgrade steps such as: Occasionally there are database or other changes that may cause a downgraded installation to not work correctly. Some reasons you might NOT want to downgrade orphaned (no longer supported in the GUI) old feature needs to be removed.Some of the reasons you might want to downgrade to an earlier version then you’ll have to put the newer version folder back (or see “How to add versions…” block below).Īlternatively, you could revert to the backup automatically during the upgrade (usually named something like backup 20181026082938.sqlite) HOWEVER this won’t include anything you did SINCE the upgrade so a database REPAIR (not Recreate) will likely be necessary. If you get a database version error such as A serious error occurred in Duplicati: System.Exception: Failed to create, open or upgrade the database. If you do and notice your server not starting, try running from the command line. 2.0.4.13 (unconfined move to version 7 - see *broken* Release: 2.0.4.13 (canary) ). 2.0.1.7 (using version 3 - 0 & 2 usage in preview releases only).WARNING! Due to changes in database versions it is not possible (well, very hands-on) to downgrade ACROSS these versions (as of ):
0 Comments
Leave a Reply. |