Since the v10 upgrade, one of my backup copy jobs keeps sending a warning e-mail each night. There are no errors or warnings and all VM's are successful. The only odd thing is that these messages are at the top of the e-mail beside the stats:
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Waiting for the next task
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Waiting for the next task
Waiting for backup infrastructure resources availability
Waiting for backup infrastructure resources availability
Support had me remove that copy job's files from the configuration so it would start a new chain last night. We again got the warning e-mail and messages like those above. We have multiple jobs all using the same repositories and proxies, but that's never been an issue before and I thought it was even the recommendation and just let Veeam use them as they become available rather than trying to schedule them at different times. With multiple jobs all running, there will always be some waiting for resources and should be expected. There's still plenty of time in the schedule to complete everything.
Support is now saying to run an Active Full on the backup copy, but didn't removing the config do that already and why would that fix the problem?
We're not technical support team, so, cannot comment on the recommendations without seeing your environment and debug logs.
That's said I cannot see how running active full backup should solve the problem with backup resource availability. So, you might ask your support engineer to clarify it.
Anyway, keep us posted and ask for additional help (if any is needed).
Jason (from another Jason), you should include your case number when you post then Veeam staff can review you question in more detail.
Also, remember you can always escalate your case if you aren't happy with the support you are getting by selecting the "Talk to a Manager" button below your support case.
I was mainly just wondering if I'm correct that contention for resources shouldn't cause a warning error as long as the jobs all complete?
Generally, yes, the job should just stay in idle state and wait, till resources are available. So, the described case looks a bit strange, especially, since current configuration has not caused any errors prior to upgrade.
Anyway, please, keep working with our support engineer and let us know about the results of your findings.
I am also getting the same warning emails since upgrading to v10.
Was there a fix for this? A simple registry key to "Ignore Resource Availability Warnings" would be appreciated.
The way we have designed our multi-tenant hosted VM backups is that each customer has multiple jobs, and all jobs start at the same time each day. Before v10 they would all happily queue for the available resources without reporting any warnings. Now, they still queue and wait for resources as expected, all jobs complete successfully as expected, however with v10 I am bombarded with hundreds of these email messages.
This looks like a bug to be honest. If support confirms the issue, they will escalate to R&D for fixing in the next update, and they are usually able to provide a hotfix for the current version too. Thanks!
Hi Scott, according to the OP's case notes, the messages went away on their own and no further investigation has been performed. I recommend contacting support for a closer look at what happens in your environment.
Gostev wrote: ↑Mar 24, 2020 11:43 pm
This looks like a bug to be honest. If support confirms the issue, they will escalate to R&D for fixing in the next update, and they are usually able to provide a hotfix for the current version too. Thanks!
Hi Gostev,
Any update on this "might-be-bug"? Is there a hotfix yet?
We started using v10 and also get these warnings now. 3 times in the last 2 weeks on several backup copy jobs. All VM's are processed successful.
There are no known bugs with this functionality currently. As stated above, OP asked to close the support case saying ''I haven't made any changes, but we've had no errors the last two nights on the copy jobs. I'm not sure what was causing it or why it went away, but things seem fine for now."
We have the same issue, see case #04563282 from last December. We are also getting warning mails with only ‘Waiting for the next task’. Case was closed with status ‘known issue, will be fixed in upcoming versions with no ETA.
Did this ever get resolved/fixed? I've inherited a system that appears to be doing exactly this. Copy jobs complete successfully every night but almost all of them produce warnings about backup infrastructure resources.
The customer did not want or have time to update to version 11, so we could not confirm whether the update was a resolution to his particular issue. Instead he rescheduled the jobs so copy backup copy intervals start after the source has done its operations. This solved the issue and he closed the case.
Might be worth opening your own ticket, since root cause of the problem might vary.
Sorry for bumping an old thread, but with V12, this issue is back again. We get warning mails every now and then with just multiple lines of ‘waiting for next task’ in them. VM processing by itself is fine.
RnD confirmed this to be an issue with backup copy jobs. They look into it if they can resolve it in a future release. The workaround is to set a schedule exclusion during the timeperiod a synthetic full runs on the source backup job.
