Skip to main content
Solved

VBO365 Catch-All Job Warning "Nothing to process"


Dynamic
Forum|alt.badge.img+10

Hi all,

i have currently an environment with multiple jobs in VBO365 (latest version).
All regular jobs are running fine.

As a fallback, we have defined a catch-all job. Under normal circumstances, there shouldn’t be an object in it…
And that’s our case - if the job has nothing to backup (as it’s processed in other jobs), the state will trigger a warning message → this will create an alert in the customers Monitoring Solution.

 


Is there any option to disable it? Or do you have some suggestions for me?

Thanks and best regards, Markus

 
 

 

 

Best answer by regnor

The easiest solution which comes to my mind is adding an object to that job 😉 The job would run without the warning and still work as a catch all job.

View original
Did this topic help you find an answer to your question?

6 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8528 comments
  • February 15, 2025

I don't think there is unless support has some registry keys or XML config changes would be the only way.  May need to contact support.


Dynamic
Forum|alt.badge.img+10
  • Author
  • Veeam Vanguard
  • 395 comments
  • February 15, 2025

Thanks Chris, i thought it would end up with a case 😅
Just created one, will keep you posted...


lukas.k
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 211 comments
  • February 16, 2025

Would it be an option to try the monitoring solution’s approach and customize it to ignore warnings from exactly that job? Don’t know how deep the integration goes on that...


Dynamic
Forum|alt.badge.img+10
  • Author
  • Veeam Vanguard
  • 395 comments
  • February 16, 2025

Thanks Lukas, but unfortunately it’s not possible on this environment and monitoring solution. 


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • 1354 comments
  • Answer
  • February 16, 2025

The easiest solution which comes to my mind is adding an object to that job 😉 The job would run without the warning and still work as a catch all job.


Dynamic
Forum|alt.badge.img+10
  • Author
  • Veeam Vanguard
  • 395 comments
  • February 17, 2025

Thanks Max, sometimes the simplest solution is the best solution. Didn’t even think about it 😂

 

Edit: i will exclude an Exchange Online User within the regular Exchange job - to process him within the Catch-All. Because adding additional ressources isn’t possible when “entire organization” is selected.

 

 
 

 

 


Comment