Importing json: DB changed

[TowerBR]

I’m having a problem importing json files.

I’m re-ordering the backup jobs in the interface, and someone suggested in a topic here (sorry, I can’t remember who it was) that one way would be to export jobs to json files and reimport them in the desired order, and so I did.

The problem is that when re-importing the json file the database is changed! See:

• DB before export:

• The same DB in explorer (ok!):

• The DB in the exported json file (ok!):

• So I deleted the job:
  

  

• And the (new?!) DB after the re-import of the json file:

What am I doing wrong?

[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!

[TowerBR]

@JonMikelV

Hmm…that might have been me

Yes, it was exactly this topic!

@JonMikelV

This is done on purpose to help avoid accidentally having two jobs pointing to the same database.

Ok, so it’s that way by design. I understood why.

@JonMikelV

To resolve this you could do one of these:

Yes I had used the third option, I changed the DB name manually in the “local database” field of the interface. Worked perfectly.

Thanks for the clarifications!

@kees-z , it may be good to put this clarification (about creating a new DB when importing configuration files) in item 3.3 of the manual.

[kees-z]

@TowerBR

@kees-z , it may be good to put this clarification (about creating a new DB when importing configuration files) in item 3.3 of the manual.

This text is added to the end of section 3.3 in the manual:

[TowerBR]

Oh, ok! I had looked at version 0.5 and in it the text was different:

This new text you posted is clearer.

[kees-z]

The text above cannot be found yet, I just added it in an unreleased version of the documentation.