# Catch up of multiple missed backups

**URL:** <https://forum.duplicati.com/t/catch-up-of-multiple-missed-backups/1738>\
**Category:** Support\
**Created:** [December 14, 2017, 7:07am UTC](https://forum.duplicati.com/t/catch-up-of-multiple-missed-backups/1738 "2017-12-14T07:07:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thommyX](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/e47774/32.png) [@thommyX](https://forum.duplicati.com/u/thommyX)\
**Post date:** [December 14, 2017, 7:07am UTC](https://forum.duplicati.com/t/catch-up-of-multiple-missed-backups/1738/1 "2017-12-14T07:07:55Z")

</div>

Is it possible that a missed backup that was missed multiple times is also catched up multiple times?

I have a job every 120 minutes. And I have a loooong running job. Last time about 28 hours.

After that I have seen (for the 120 minutes job)

Last successfull run: Today, about 5 minutes ago =\> this was the catch up  
Next scheduled run: in about 60 minutes

And then 2 minutes later this job is processed! But the “last successfull run” was the catch up for the missed backups while the 28 hours job was running.

So the question is: Is a job catched up multiple times when it was missed multiple times?

---

<div class="post-metadata">

**Author:** ![JonMikelV](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/j/439d5e/32.png) [@JonMikelV](https://forum.duplicati.com/u/JonMikelV)\
**Post date:** [December 14, 2017, 8:34pm UTC](https://forum.duplicati.com/t/catch-up-of-multiple-missed-backups/1738/2 "2017-12-14T20:34:41Z")

</div>

The way the queue works a single job is not supposed to appear more than once, so if you seem to be experiencing that then there’s a bug.

One way to check what’s in the queue is to use the main menu “About” item, then click on the “System info” button, then scroll down to the “Server state properties” section and find the following lines:

- `activeTask` is the ID of the currently running task (if any)
- `proposedSchedule` is the “not yet in queue, but expected to be put in queue at …” list
- `schedulerQueueIds` is the list of items CURRENTLY in the queue

(Thanks for kenkendk for the above descriptions!)

For a summary of how the scheduler is supposed to run, see here:

> [@Scheduling strategy for backups](https://forum.duplicati.com/t/scheduling-strategy-for-backups/1309/6):
>
> If I turn on my NAS (synology) it also immediately starts a backup if it missed one if I remember correctly.

---

<div class="post-metadata">

**Author:** ![thommyX](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/e47774/32.png) [@thommyX](https://forum.duplicati.com/u/thommyX)\
**Post date:** [December 14, 2017, 9:41pm UTC](https://forum.duplicati.com/t/catch-up-of-multiple-missed-backups/1738/3 "2017-12-14T21:41:49Z")

</div>

![image](https://forum.duplicati.com/uploads/default/original/1X/530e6de30613f941ecf0da63ec267f39842f749c.png)

As you can see in this screenshot I have it again! A long job run until about 10:25PM. Then the hubiC started and finished at 10:31 as you can see.

Then some other jobs where catched up and not hubiC is running. BUT you see: Next scheduled run is 11:19pm and as you can also see the current time is 22:38 (10:38pm).

About:

lastEventId : 4272  
lastDataUpdateId : 640  
lastNotificationUpdateId : 147  
estimatedPauseEnd : 0001-01-01T00:00:00  
activeTask : {“Item1”:202,“Item2”:“11”}  
programState : Running  
lastErrorMessage :  
connectionState : connected  
xsfrerror : false  
connectionAttemptTimer : 0  
failedConnectionAttempts : 0  
lastPgEvent : {“BackupID”:“11”,“TaskID”:202,“BackendAction”:“Get”,“BackendPath”:“duplicati-bc96c8d604a0d49748a38140622ea412f.dblock.zip.aes”,“BackendFileSize”:15655533,“BackendFileProgress”:0,“BackendSpeed”:-1,“CurrentFilename”:null,“CurrentFilesize”:0,“CurrentFileoffset”:0,“Phase”:“Verify\_Running”,“OverallProgress”:1,“ProcessedFileCount”:28770,“ProcessedFileSize”:22540734797,“TotalFileCount”:28770,“TotalFileSize”:22540734797,“StillCounting”:false}  
updaterState : Waiting  
updatedVersion :  
updateReady : false  
updateDownloadProgress : 0  
proposedSchedule : [{“Item1”:“10”,“Item2”:“2017-12-14T22:00:00Z”},{“Item1”:“2”,“Item2”:“2017-12-14T22:07:00Z”},{“Item1”:“11”,“Item2”:“2017-12-14T22:19:00Z”},{“Item1”:“1”,“Item2”:“2017-12-14T23:00:00Z”},{“Item1”:“9”,“Item2”:“2017-12-14T23:07:00Z”},{“Item1”:“6”,“Item2”:“2017-12-15T00:00:00Z”},{“Item1”:“7”,“Item2”:“2017-12-15T02:00:00Z”},{“Item1”:“8”,“Item2”:“2017-12-15T05:00:00Z”},{“Item1”:“3”,“Item2”:“2017-12-15T05:05:00Z”},{“Item1”:“5”,“Item2”:“2017-12-15T07:10:00Z”},{“Item1”:“4”,“Item2”:“2017-12-15T12:04:00Z”},{“Item1”:“12”,“Item2”:“2018-12-05T01:00:00Z”},{“Item1”:“13”,“Item2”:“2021-12-09T12:00:00Z”}]  
schedulerQueueIds : [{“Item1”:203,“Item2”:“6”},{“Item1”:204,“Item2”:“1”}]  
pauseTimeRemain : 0