Failed to obtain resource availability

VMware specific discussions

Re: Failed to obtain resource availability

Veeam Logoby Daveyd » Wed Nov 16, 2016 8:10 pm

My "solution" was to reboot the Proxy that went unavailable in the Veeam console. Once that Proxy became available in Veeam's eyes all the jobs started SLOWLY processing again, which most had been "running" for 15 hours. This makes no sense since I have multiple Proxies and most of the SAN based jobs that only use the Veeam server as a proxy were failing as well. So far Support has really been no help saying that I may need to up the concurrent tasks to the max that the Proxy will take and consider upping the RAM the Proxy that was having issues? Huh?
Daveyd
Expert
 
Posts: 272
Liked: 10 times
Joined: Thu May 20, 2010 4:17 pm
Full Name: Dave DeLollis

Re: Failed to obtain resource availability

Veeam Logoby foggy » Thu Nov 17, 2016 12:01 pm

I recommend escalating the case to investigate the actual reasons of the observed behavior.
foggy
Veeam Software
 
Posts: 15272
Liked: 1131 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Failed to obtain resource availability

Veeam Logoby masonit » Thu Dec 01, 2016 1:24 pm

We had the same problem. One of many proxy servers went offline during backup window. Left alot of jobs hanging. Cancelled all jobs and also rebooted vbr server. After that all jobs we tried said: Waiting for backup infrastructure resources availability. Even though none of the jobs are using the unavailalbe proxy. When proxy server was online again all jobs started working again..

Case: 01992017

\Masonit
masonit
Service Provider
 
Posts: 141
Liked: 10 times
Joined: Tue Oct 09, 2012 2:30 pm
Full Name: Magnus Andersson

[MERGED] Periodic Backup Fail

Veeam Logoby timgowen » Mon Oct 23, 2017 10:07 am

I'm testing Veeam and have noted that every few weeks I get a complete failure of my backups

Code: Select all
Extensis TestError7:00:14 PM8:30:35 PM0.0 B0.0 B0.0 B1:30:21 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park
LON-XIBO-HOSTError7:00:14 PM8:00:34 PM0.0 B0.0 B0.0 B1:00:20 Unable to allocate processing resources. Error: Failed to obtain resource availability: Dowding
L-VM-00002Error7:00:13 PM7:15:35 PM0.0 B0.0 B0.0 B0:15:22 Unable to allocate processing resources. Error: Failed to obtain resource availability: Dowding
New Virtual MachineError7:00:14 PM9:45:35 PM0.0 B0.0 B0.0 B2:45:21 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park
RAFM-DC-01Error7:00:14 PM8:15:32 PM0.0 B0.0 B0.0 B1:15:18 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park
RAFM-DC-02Error7:00:14 PM7:30:33 PM0.0 B0.0 B0.0 B0:30:19 Unable to allocate processing resources. Error: Failed to obtain resource availability: Dowding
TRAPS Virtual MachineError7:00:14 PM8:45:33 PM0.0 B0.0 B0.0 B1:45:19 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park
TucanoError7:00:14 PM9:00:31 PM0.0 B0.0 B0.0 B2:00:17 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park
VERNON-TESTError7:00:14 PM7:45:31 PM0.0 B0.0 B0.0 B0:45:17 Unable to allocate processing resources. Error: Failed to obtain resource availability: Dowding
Windows 10 Test ClientError7:00:14 PM9:30:32 PM0.0 B0.0 B0.0 B2:30:18 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park
Windows 7 Client for Vernon TestError7:00:14 PM9:15:34 PM0.0 B0.0 B0.0 B2:15:20 Unable to allocate processing resources. Error: Failed to obtain resource availability: Park


I reboot the server (Windows Server 2012 R2) that's running Veeam, and re-run the backup - successfully.

Veeam Agent 'Backup Job JAGUAR' finished with Error and will be retried. These errors are logged for every failed server:

Code: Select all
Job details: Creating VSS snapshot Error: Failed to create snapshot: Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{477becb1-5133-408a-ab54-3e23e3ee0106}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].
Error: Failed to create snapshot: Backup job failed.
Cannot create a shadow copy of the volumes containing writer's data.
A VSS critical writer has failed. Writer name: [SqlServerWriter]. Class ID: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{477becb1-5133-408a-ab54-3e23e3ee0106}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].

I've seen other issues similar to this, but the fact that it recurs on more or less a monthly basis seems weird to me.
timgowen
Novice
 
Posts: 3
Liked: never
Joined: Tue Aug 22, 2017 8:34 am
Full Name: Tim Gowen

Re: Failed to obtain resource availability

Veeam Logoby PTide » Mon Oct 23, 2017 10:59 am

Hi,

Have you contacted our support team on the issue? If not then please do and post your case ID.

Thank you
PTide
Veeam Software
 
Posts: 3230
Liked: 269 times
Joined: Tue May 19, 2015 1:46 pm

Previous

Return to VMware vSphere



Who is online

Users browsing this forum: wuerzburger and 3 guests