Importing json: DB changed

[JonMikelV]

@TowerBR

I’m re-ordering the backup jobs in the interface, and someone suggested in a topic here

Hmm…that might have been me - sorry if I missed that the databases changed.

Re-ordering Backup Jobs on Duplicati Landing Page

I know this can be “painful” for those that have many backup jobs, but until the feature is added to the codebase this workaround might, um, work. Basically, you can export all your jobs to files, delete them (DO NOT “Delete local database” or “Delete remote files”), then re-import them in the desired order. To replicate what I did for testing this, you could: Export jobs Open up the job menu and select “Export…” (you can also export from the Delete page, if you prefer) Make sure “To File” …

This is done on purpose to help avoid accidentally having two jobs pointing to the same database. To resolve this you could do one of these:

• use the “Database…” menu “Repair” button to rebuild the database at the new location. This is the safest option, but also the slowest as it involves downloading index files (NOT full backups) from the destination
• in your file manager just rename the old .sqlite file to the appropriate new name. Be careful you’re renaming the correct file!
• use the “Database…” menu and manually paste the correct / original database path in the “Local database path” field then click the “Save” button (which becomes active after the field has changed). Note that you might be prompted about things including using an existing database. Be careful you’re selecting the correct file!