9.5U2
In my configuration, I have one Hyper-V proxy defined (the backup server) which is set for a max of 20 concurrent tasks (and it has a green checkmark next to the "20" indicating there are sufficient server resources).
There are 2 health check jobs running, and a third backup is "Waiting for backup infrastructure resources availability" with detail information of "Resource not ready: Hyper-V backup proxy" on the first pending VM.
With the proxy able to support 20 concurrent tasks, why is the backup job waiting?
-
- Enthusiast
- Posts: 37
- Liked: 8 times
- Joined: Sep 27, 2016 6:59 pm
- Contact:
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Resource not ready: Hyper-V backup proxy
Hello, I would recommend to contact Veeam support. Once you do, please post your support case number here. Thanks!
-
- Product Manager
- Posts: 20415
- Liked: 2302 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
- Contact:
Re: Resource not ready: Hyper-V backup proxy
Just out of curiosity - how many virtual disks those VMs have (the ones for which health check is currently running)? Are there any task limits set on repository server? Thanks.
-
- Enthusiast
- Posts: 37
- Liked: 8 times
- Joined: Sep 27, 2016 6:59 pm
- Contact:
Re: Resource not ready: Hyper-V backup proxy
Sorry for the delay in responding.
The jobs on which the health checks were occurring may have cumulatively had more than 20 virtual disks. So if each virtual disk is considered a 'task' as far as the proxy is concerned, then may be that would explain it?
The jobs on which the health checks were occurring may have cumulatively had more than 20 virtual disks. So if each virtual disk is considered a 'task' as far as the proxy is concerned, then may be that would explain it?
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Resource not ready: Hyper-V backup proxy
One task = one virtual disk. So yes, that may be the reason.
Who is online
Users browsing this forum: No registered users and 16 guests