Backup job finished - or not?

Support
16

Regarding the Azure EncryptionPolicy errors, not a clue.

For the “finished or not” issue, @warwickmm is correct that in 2.0.2.1 beta there was a database cleanup (I think) step that occurred AFTER the “Finished!” message was displayed.

The best way to tell what (if anything) is currently running and what’s queued up is probably to go to About → System Info then scroll down to “Server state properties”. In there you should see:

  • 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

My GUESS regarding the OP is that you were in the finished-but-not-really hole (which should have shown in the activeTask line) and when you tried to manually do things like run, verify, or compact they were being added to the queue (which should have shown on the schedulerQueueIds line).

Of course that’s assuming "Verify files" or "Compact now" are not available means you clicked on them and nothing seemed to happen…