Errors with ftp

Hi, I’m new to Duplicati after recommendation in the news.
I created my first backup, its more or less 27GB big and goes to my ftp-account. It ran for a couple of hours, ca. 16GB of zip.aes files were uploaded but now status is just “Stopping after current file…”, Last backup: never, no errors.
“Run now” is not doing anything.
How can I reset the status and try again?
Thanks
Tom

Welcome to the forum @Tom_qv

Presumably you tried the stop button in hope of something good happening?

It queued a backup (hard to spot though) to run after current backup finishes.

If you can’t end the backup any other way, you can end the Duplicati process.
For example, Windows has a Task Manager, and other systems have similar.

There’s not really any reset required. Next run should pick up where it left off.

You can start totally fresh by deleting destination files and Duplicati database.
This would lose backup history if you had any, but having none makes it nicer.

It would be good to look into what went wrong with your first try, if you care to.

Hi @Tom_qv , it could look like you have experienced a similar issue to this:

It seems that some cases of errors can cause a deadlock with 2.1.0.2.
I am investigating, but for now I do not know many details.

True, except for the very first backup, which I fear is the case here.

What happens? IIRC I don’t get a synthetic file list (although in theory it seems possible).
Anything worse than a full restart? Basically, is there any need for specific reset actions?

The way the interrupted continue works, is that it looks at the last successful backup, and then makes a “synthetic version”. The synthetic version is created from whatever completed, and then patching with the files from the previous version. Since there is no previous version the recovery gives up.

I think we should just allow that you can continue without a previous version (pretend it was empty), but that code is not implemented yet.

A silly workaround is the create the backup with just a single file, and then start the actual backup after this, so it can resume on crashes.

For the current code, yes, the situation where the initial backup did not succeed, you need to clean up the remote storage, local database, and start over.