FAILED Nothing to process

[AlexLeadingEdge]

Hi guys,

Not sure if this is ticket worthy, perhaps just a suggestion. "Nothing to process" should be a warning or success, not an error.

We seem to see this between ~11pm and ~2am here in New Zealand for multiple clients, I suspect the Microsoft 365 servers are temporarily going offline for updates?

5/11/2025 1:00:01 am :: Job started at: 5/11/2025 1:00:01 am
5/11/2025 1:20:02 am :: Transferred: 0 B (0 items) at 0 B/s (0 items/s)
5/11/2025 1:20:02 am :: Nothing to process
5/11/2025 1:20:02 am :: Unable to cancel retention session for the repository (repository ID: REDACTED, retention session ID: REDACTED).
5/11/2025 1:20:02 am :: Job failed at: 5/11/2025 1:20:02 am

[mjr.epicfail]

hmm it looks like this is a retention job "Unable to cancel retention session", if that's the case, don't you want an error when this fails for some reason?

[AlexLeadingEdge]

I'm treating the "Nothing to process" as being a separate issue from "Unable to cancel retention session for the repository".

Am I wrong in thinking this is two different issues?

[mjr.epicfail]

I think those are related in this case, normally when a job hits nothing to process is a warning, at least that's my epxerience.

[Polina]

Hi All,

I see two issues here.
First, which I agree with, is that 'nothing to process' should not be an error indeed. No data - no backups, all fair. We'll consider updating this logic.

Second, a backup task has a priority over rentention. When a backup job starts while retention is running, retention gets canceled. From this piece of log, I'd assume that for some reason retention could not be stopped which in turn prevented backup from running - they cannot run simultaneously. If this reoccurs, I'd bring it to the attention of our support team.

Thanks!

[AlexLeadingEdge]

It is recurring repeatedly most nights, but never during the day. I will open a ticket with Veeam Support.