Closed FredericMa closed 5 years ago
Probably it is Duplicati itself that is returning old data?
Hmm, it is parsed directly from the data output by API. The client is too dumb to do any caching.
Out of curiosity could you try using duc describe backup <id>
instead of get? That method has no logic applied to the output so it will show if there is some fault in the filter that is used by the get command.
I found something similar on my installation actually. When describing the metadata is all wrong.
LastFinished: 20180712T174016Z
LastStarted: 20180712T173218Z
It claims my backup was performed tomorrow. I went into the Duplicati database and it's actually showing tomorrow as well... I'm wondering how that is happening.
I must admit I started pulling that data out in the client without vetting if it was true.
Never mind. I found the issue. I was using LastStarted
instead of LastBackupStarted
. After changing to the last backup specific values it makes more sense.
It's fixed in fd61f6c050c7b3ba5e8f98d9c7ec8109a3b10f9a, so I'm pushing out a new binary release that's also got some other stuff I haven't released yet. https://github.com/Pectojin/duplicati-client/releases/tag/0.4.9_beta
Thanks! Works like a charm now
Hi,
I just started using duplicati-client today but I noticed that it returns old data. My backups started failing on November 19th so I upgraded to the latest beta. Now everything is working again but I noticed that the client still returns data from the last failure while all backups have ran successfully today. The data size locally and remote are correct. Also the version count is correct but the timestamps are not correct.
The web interface does display the correct data and I also tried to restart duplicati but no difference: