Host-based backup of VMware vSphere VMs.
Post Reply
mdiver
Veeam Legend
Posts: 230
Liked: 37 times
Joined: Nov 04, 2009 2:08 pm
Contact:

Could not perform threshold check for backup location (WAN)

Post by mdiver »

I get this error on a backup copy job to a remote repository on a windows machine (not CIFS) using WAN accelerator:

Could not perform threshold check for backup location "D:\Veeam-Backups" due to space info retrievement fail!

All VMs are though processed correctly. It happens most of the time, but not in any case. When the job was orinially set up (under 8.0.0.817) it ran flawlessly for some time. Could it be a timeout issue?
Version now is 8.0.0.917.

Regards,
Mike
Shestakov
Veteran
Posts: 7328
Liked: 781 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Could not perform threshold check for backup location (W

Post by Shestakov »

Hello Mike, please provide support case ID when posting about errors or technical issues, as requested when you click "New Topic".
Have you tried to run the job not using WAN acceleration?
Thanks!
mdiver
Veeam Legend
Posts: 230
Liked: 37 times
Joined: Nov 04, 2009 2:08 pm
Contact:

Re: Could not perform threshold check for backup location (W

Post by mdiver »

As the backup itself worked and I was just wondering about the message I did not file a case.
But I will do that if it helps.
Without WAN acceleration is not an option here as we have a slow 16Mbit connection in our scenario here. I already found related posts in the forum found it helpful to disable WAN accel.
I will follow up with a case ID.
mdiver
Veeam Legend
Posts: 230
Liked: 37 times
Joined: Nov 04, 2009 2:08 pm
Contact:

Re: Could not perform threshold check for backup location (W

Post by mdiver » 1 person likes this post

Case #00821302
Vitaliy S.
VP, Product Management
Posts: 27377
Liked: 2800 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Could not perform threshold check for backup location (W

Post by Vitaliy S. »

Seems like the mechanism of checking free space cannot get any data from your repository, which should not affect the entire job run. Thanks for posting your case ID, and please update this topic with a resolution for future readers. Thanks!
fcocquyt16
Influencer
Posts: 13
Liked: 3 times
Joined: May 05, 2016 6:17 am
Full Name: Fletcher Cocquyt
Contact:

Re: Could not perform threshold check for backup location (W

Post by fcocquyt16 »

I am seeing the same - opened case 01804059

The VMs seem to backup OK, but at the end the warning (yellow triangle) "5/19/2016 6:15:49 AM :: Could not perform threshold check for backup location "/mnt/veeam/" due to space info retrievement fail!"

and the whole job gets marked as FAILED (big red X)

Please advise on any solution?
foggy
Veeam Software
Posts: 21139
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Could not perform threshold check for backup location (W

Post by foggy »

Hi Fletcher, in the OP's case the reason was in a daily repository IP change. I recommend you to continue looking into your particular case with your engineer. Thanks.
Shestakov
Veteran
Posts: 7328
Liked: 781 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Could not perform threshold check for backup location (W

Post by Shestakov »

Looks like Fletcher`s case is resolved already by rescanning the target Linux repository.
Thanks!
fcocquyt16
Influencer
Posts: 13
Liked: 3 times
Joined: May 05, 2016 6:17 am
Full Name: Fletcher Cocquyt
Contact:

Re: Could not perform threshold check for backup location (W

Post by fcocquyt16 »

No, unfortunately it was not resolved - we have a fresh batch of 40+ errors again this morning with:

5/20/2016 6:21:08 AM :: Could not perform threshold check for backup location "/mnt/veeam/" due to space info retrievement fail!

I had asked the engineer to keep case 01804059 open since I suspected the issue could be related to load and the free space retrieval timing out.

I updated the case with a few questions:
1 - is there a free space retrieval timeout we can tweak to have it wait longer for the free space to be returned?
2 - when we did the rescan yesterday for one mount it took almost 3 minutes to return OK - why so long?
3 - the rescan reported "0 added, 0 encrypted, 0 updated, 0 removed, 196 skipped" - what are the 196 skipped items ?

Thanks for any tips/info!
foggy
Veeam Software
Posts: 21139
Liked: 2141 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Could not perform threshold check for backup location (W

Post by foggy »

2. It needs to check metadata for all stored backups (those 196).
3. Existing backups that do not require any actions, since information about them in database is up-to-date.
fcocquyt16
Influencer
Posts: 13
Liked: 3 times
Joined: May 05, 2016 6:17 am
Full Name: Fletcher Cocquyt
Contact:

Re: Could not perform threshold check for backup location (W

Post by fcocquyt16 »

There are actually 15 jobs with the same error between 5am and 6:30 am (I inherited this config where all jobs kick off at 5am)

Even if Veeam 9.0.0.902 is smart about limiting the number of simultaneous jobs (the VMs are getting backed up)
its this free space retrieval at the end of the jobs is failing and marking the whole job as failed and since we might
have 1-2 real failed jobs that require action we need to eliminate this noise.

Is there a timeout setting we can tune to allow more time for the free space check to return?

Would staggering the start times of the jobs help avoid the timeout errors?

thanks!
Post Reply

Who is online

Users browsing this forum: No registered users and 25 guests