Verifying backend data forever

[JonMikelV]

Thanks for sharing your experience. We know database stuff can get quite slow and while we’re working to improve it, it’s not happening very quickly.

We try to warn people it can take a long time, but “long time” means different things to different people.

I tested a forced recreate on a 5+ year old laptop and aborted it after 3 weeks (had to reboot for software install). Since it was a test I simply restored there backup copy I had made and everything was fine.

I documented a smaller test of recreating ok try different powered machines from the same destination here, if you’re curious:

Database recreate performance

I have an older machine where I’ve done a test database Recreate that took about 4.5 days (for a 335M sqlite file) - so I thought I’d take a look at why database recreates take so long. I started by copying the destination files to another folder pointed to by a test backup created on a faster machine, then running a Recreate there. This took 3.7 days - which I expected to be a lot shorter as this other machine is a lot more powerful and the destination files were local. Note that all numbers…

Note that while I did not test it, I suspect a recreate can be done anywhere and the resulting database copied to the ultimate Duplicati install machine.

This means that in theory, one could make a standalone database recreate script to run at the destination (assuming your destination can run things) then copy the recreated database to wire it’s needed.