How to run existing backup task after manual deletion of destination backup set outside of Duplicati

How does one perform a backup after the destination backup set has been manually deleted outside of Duplicati’s purview?

Scenario:

  1. Successful backup, destination is an smb share.
  2. Outside of Duplicati’s purview, manually delete entire destination backup set (but not the destination folder itself).
  3. Attempt to run the original backup task, which fails.

What’s the preferred method to recover from this situation?

No combination of gui actions I tried would allow running the backup task. Result was Duplicati thinking the destination url had changed, with no way to indicate it hadn’t. Tried Deleting and Repairing local database. Tried running Verify Files, that seemed to hang. Eventually gave up, exported the local configuration, deleted the backup task, and created a new backup task with imported configuration.

What’s the right method to have properly recovered from this scenario?

Thanks

Hi @duck, welcome to the forum :waving_hand:

If you delete the remote storage fully, then it is sufficient to delete the local database.
This is the same scenario that is before you make the first backup (no db, no remote files).

I think Duplicati gets confused if you do repair (or recreate) because it tries to recreate the database from the remote data, and then finds there is nothing to build the database from.
The resulting database is then in an invalid state (existing, but not recreated).

Understood, thanks. I had tried Repair, and Recreate (delete and repair), but not Delete.