yes pcloud have a sync for his own backup system but he isn’t crypted so i don’t use him
generally i avoid to put uncrypted files on web, mostly if personal.
That should hide it, so now when you list-broken-files, Duplicati should notice it’s gone and tell you what source files have some damage. Those files then get purged when you run purge-broken-files.
Yes, as you have lots of files with bits in that bad dblock.
EDIT: Some might be repeats, as it’s naming versions…
The next backup will grab a current version. Old get lost
when you purge-broken-files. This just predicts the loss.
I’m not sure why that would be. Is it still actually going?
If you mean delete and start again, you lose all history.
If you mean recreate the database, dblock’s still bad…
EDIT:
It looks like all that option does is stop an earlier cutoff:
Help text:
--full-result (Boolean): Output full results
Use this option to increase the amount of output generated as the result
of the operation, including all filenames.
* default value: false
If you mean won’t it be faster to delete the destination files and database compared to a full verification (using test with all), and possibly fixing newfound issues, it’s more possible, but still isn’t guaranteed. Usually people like to have backup history, so starting fresh isn’t usually the first thing that’s suggested.
If you start fresh, use Advanced optionblocksize of 500 KB or 1 MB and operations should run faster. You’ve currently got about 5 million 100 KB blocks being tracked, and 1 million would be a better count.
There’s no guarantee that pCloud will work better than before, so plan on some verification in any case.
If you mean that’s what you want (lose all history, restart fresh, it finishes when it finishes), feel free.
Yes.
That’s weird. It was faster first run. Did it start giving output?
Make sure nothing else is running. Only one thing at a time.
EDIT:
My list-broken-files on an intact smaller backup took 12 seconds with full-result set.
The main reason I even tested was to confirm that the status bar mis-announces it as backup.
This makes it harder to know what’s really running, but when it starts it should say something:
See wrong operation announced at top. Running … stop now came pretty fast. Listing paused after.
yes that’s finish yesterday but friends coming so i can’t reply and like i forgot to save the result i need restart the command to show you XD
i remember there are many files in my download folder but that don’t give me any duplicati…aes
if i do purge-broken-files, that remove theses files in the duplicati db to allow me continue the backup but theses files will be added too in next backup job ?
I think it’s just a command change with same changes you did for list-broken-files. Recovering by purging files in the Disaster recovery manual I linked to has example.