resource not ready snapshot?

[daniflexx]

Hi,

I'm backing up a few hyper-v 2008R2 hyper-v servers (Veeam 7.0.0.771) and I can't go beyond 3 or 4 simulatenous VM taks per host.

I tried to increase the repository limits, increase the concurrent task at the host level and increase the snapshot limit in the datastore confiration for each host (all these changes in the backup infrastructure node)

I also increased the registry key introduced in R2 with no luck.

No matter what, I can't have more than 4 vms per hyper-v host backing up a the same time.

The queued machines says either "resource not ready snapshot" or "waiting hyper-v proxy"

Is any other limit I'm not aware of?

thanks,

dani

[Vitaliy S.]

Hello Dani,

What kind of VSS provider do you use? Software one? Do you use proxy servers installed on each host or you have an off-host proxy machine?

Thank you!

[daniflexx]

Hi,

I'm using Microsoft Software Shadow Copy Provider 1.0

I use proxy server in the same host (onhost)

thanks!

dani

[Vitaliy S.]

Dani, do you use Hyper-V Cluster and CSV or these are just standalone hosts?

[daniflexx]

Hi Vitaliy,

I am using standalone hosts.

[Vitaliy S.]

How many virtual disks do you have in your VMs? Be aware that each task on the repository/proxy is tracked per virtual disk and not per VM.

[foggy]

Also, do you have parallel processing enabled in the Veeam B&R properties?

[daniflexx]

Yes, I have the Parallel Processing enabled in the Veeam properties.

[daniflexx]

Ups, I'm afraid I missed one of your questions. I have two disks per VM. Knowing that each disk is an independent task I'll try to determine if concurrency is aligned with the limits. I'll let you know.

By the way, since the VMS are using local storage (not clustered, not CSV) is it possible to add off-host proxies? Will it help to increase concurrency?

thanks

[Vitaliy S.]

Off-host proxy server requires shared storage and hardware VSS provider, which is not possible with local storage.

[theJonson]

After recently updating a 2 node 2008 R2 Cluster with the latest windows updates (on 26th October 2014) all the Veeam backups hang on the section "Waiting for backup infrastructure resources avaliability" with the per VM message of "Resource not ready: Snapshot"

This is a new install of Veeam with the first backup running on October 1st 2014, and it has been fine until this week. There seems to be no reason for the problem, I've rebooted all the VMs and the Hosts and it has made no difference.

The vssadmin "list writers" command shows no errors on either server, and the VM fails to backup regardless of the host it is running on.

Any pointers before I raise a case direct with Veeam?

[Vitaliy S.]

Check proxy server states in the Veeam console and concurrent tasks limit, if all components look good, then debug logs review will be required here.

[StevenYong]

Hi,

I'm backing up hyper-V servers via (Veeam 9.0.0.1491) that has been running for over a year now without issue but now we have issue backup job keep hung on (Resource not ready snapshot).
I can't have more than 2 vms per hyper-v host backing up a the same time. We haven't changed anything, no other jobs are running on any other servers or this one.

I tried to below step but still no luck.
1) increase the repository concurrent limits.
2) increase the proxy concurrent task but still same.
3) Rescan repository.
4) Restart VEEAM backup services.

The queued machines says either "resource not ready snapshot" or "waiting hyper-v proxy".

Case openned: 02211331

Anyone know what happen? Thanks

Steven

[PTide]

Hi,

Do you have parallel processing enabled?

Thanks

[nmdange]

In 2012 R2, there is a limit of one active snapshot per CSV and 4 VMs backed up concurrently as part of that snapshot (assuming all 4 VMs are on the same physical Hyper-V host) or 8 VMs if it's using hardware VSS and not software VSS. This is an architectural limitation that is fixed in Windows Server 2016.

I have had to restart the Veeam server a handful of times over the last couple of years when a lot of VMs have snapshot issues. It seems like the locks in the Veeam database don't get cleaned up and restarting Veeam will clear them. This would be if every single VM being backed up is "Resource not ready: Snapshot" and nothing is actually running so it may not be the same problem for you.

[StevenYong]

Hi All,

Parallel processing are enabled and finally we find out this issue are cause by antivirus installed in Hyper-V host recently.
Antivirus live scan cause Hyper-V host take very long time to create snapshot end out all backup are queuing.
We have to disable antivirus live scan in all Hyper-V host as temporary solution.

Anyone know which VEEAM folder/file should exclude from antivirus live scan in Hyper-V host because VEEAM KB (https://www.veeam.com/kb1999) does not mention it. Or it same as Guess OS and Backup Proxies exclusion?

[veremin]

I'd check the following folders, as those are typical place where our components are stored:

Code: Select all

C:\Program Files(x86)\Veeam
C:\Windows\Veeam

Thanks.

[nmdange]

For Hyper-V hosts generally it's not recommended to have antivirus but here's the list of exclusions from Microsoft. Basically exclude any directory that has VM files in it. C:\ClusterStorage would be most important for a cluster with CSVs.
https://support.microsoft.com/en-us/hel ... er-v-hosts