As mentioned here, this error is likely caused by something that happened earlier in the process but wasn’t correctly caught - that’s probably why you’re not seeing a “definitive” fix as there could be multiple error points that happen before Duplicati detects the issue as part of StartVolume:
It’s been suggested that the “Previous volume not finished” error is sometimes a red herring - something else is blowing up but not interrupting the job when it should thus allowing the previous volume error to happen.
If you don’t do a repair and re-run the backup does it work?
As a test only, does it work if you enable the --no-backend-verification parameter?
As far as the speed of the file counter, it’s possible you’re seeing the difference between new files / changes being backed up (slow…
Not that it’s a fix, but as a test, did you try changing your dblock / Upload Volume size? It seems to have worked here:
So — interestingly on this PARTICULAR backup that would never actually start shipping data to the remote Backblaze server, I made it START working by changing the upload volume size. I had it set at 500 Meg because I was a little concerned about creating such a large number of files remotely. I kicked it back down to 50 Meg and the backup ran overnight.
Otherwise, for some people it seems the issue is related to running out of temp space:
In pretty sure it will be the --dblock-size parameter, but you could double check by using the job Export link to export “As Command line…” and see what shows there.
I’ll have to get back to you on the default number of dblock (archive) files that are prepared while the “current” one is being uploaded. There’s a (poorly named?) parameter that let’s you change that count if you want.
If the tmp ramdrive is global (not just for Duplicati) then my guess is it’s getting other system filmed in th…
This issue does appear to be long standing so there must be some parameters or environment specifics causing it to happen otherwise I would expect it to have shown up way more than it already has (Search results for '"Previous volume not finished"' - Duplicati ):
opened 03:46PM - 06 Mar 17 UTC
bug
core logic
<!-- This is a bug report template. By following the instructions below and fill… ing out the sections with your information, you will help the developers to get all the necessary data to fix your issue.
You can also preview your report before submitting it. You may remove sections that aren't relevant to your particular case.
Let's begin with a checklist: replace the empty checkbox [ ] below with a checked one [x] if you already searched for duplicate bugs -->
I have:
- [ ] searched open and closed issues for duplicates
----------------------------------------
### Version info
**Duplicati Version:** 2.0.0.51
**Operating System:**Windows server 2008 r2
**Backend:**FTP
### Bug description
**Failed: Previous volume not finished, call FinishVolume before starting a new volume
Details: System.InvalidOperationException: Previous volume not finished, call FinishVolume before starting a new volume
at Duplicati.Library.Main.Volumes.IndexVolumeWriter.StartVolume(String filename)
at Duplicati.Library.Main.Operation.BackupHandler.UpdateIndexVolume()
at Duplicati.Library.Main.Operation.BackupHandler.FinalizeRemoteVolumes(BackendManager backend)
at Duplicati.Library.Main.Operation.BackupHandler.Run(String[] sources, IFilter filter)
at Duplicati.Library.Main.Controller.<Backup>c__AnonStorey0.<>m__0(BackupResults result)
at Duplicati.Library.Main.Controller.RunAction[T](T result, String[]& paths, IFilter& filter, Action`1 method)**
### Steps to reproduce
- Configure a new backup with FTP back end
**Actual result:**
Backup should run normal
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/42751975-previous-volume-not-finished?utm_campaign=plugin&utm_content=tracker%2F4870652&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F4870652&utm_medium=issues&utm_source=github).
</bountysource-plugin>