after completion of a file restore, the Duplicati home page shows under the backup name:
Last successful run: Yesterday at 9:22 PM (took 00:13:58) Run now
The last successful run time (9:22 pm) refers to the last backup time and not restore time.
The run duration of 13:58 however refers to how long the restore took and not the last backup.
What version of Duplicati are you using?
I just happened to have finished some restore tests and I can confirm this happened to me with 2.0.3.6. Flagging this topic as a #bug .
I have slightly older 2.0.3.3_beta_2018-04-02.
Thanks for confirming the bug
Monstergerm:
Last successful run
You’re welcome - thanks for bringing it up!
I’ve added an issue over a GitHub so hopefully it will get addressed sooner than later.
opened 10:02PM - 14 Jun 18 UTC
closed 04:25AM - 16 Nov 18 UTC
bug
- [x ] I have searched open and closed issues for duplicates.
---------------… -------------------------
## Environment info
- **Duplicati version**: 2.0.3.3, 2.0.3.6
- **Operating system**: Any
- **Backend**: Any
## Description
The GUI job summary "Last successful run" information seems to have a date associated with the most recent BACKUP but the "took" duration seems to be the most recent duration of a backup OR a restore.
This issue was created based on a user reported problem:
https://forum.duplicati.com/t/interface-issue-after-restore-is-completed/3807
## Steps to reproduce
1. Have a job with at least one backup (so the "Last successful run" text has a date and duration)
2. Make note of the duration (the "(took 00:11:43)" text)
3. Perform a restore
4. Look at the GUI job summary and you'll see the duration has changed to how long the restore took
- **Actual result**:
The GUI job summary "Last successful run" line "took" duration will report duration of a restore run if it happened more recently than a backup run
- **Expected result**:
The "took" duration should always align with the run date. Note that the current "Last successful run" text doesn't really specify that the "run" is a backup, so it's possible the real bug is that the date isn't changing to the restore date.
If this line is supposed to be for backups only, consider changing "Last successful run" to "Last successful backup finished".
## Screenshots
## Debug log