Resource not ready: VSS snapshot - Server restart needed

[widmerkarl]

Hi folks!

CASE #: 01800880

Today i got this error again in VBR 9 U1.

When i look in the GUI i see different jobs running, all waiting for VSS snapshot with the message "Resource not ready: VSS snapshot".

Then i always have to gracefully stop the jobs, restart the backup server and check manually for existing or orphaned snapshots on vSphere client.

After that work the jobs are running fine, until after a not specified time frame (mostly about two or three weeks) then they fail again.

Did someone of you had this problem before? Did you find a solution?

Thanks!

[tellen]

We have the exact same problem:

VBR 9 U1.

One backup job that backups 6 VM's (vSphere ESXi 5.5) hangs on the same message: "Resource not ready: VSS snapshot".

The problem never occurred on VBR 8 or prior to deploying U1 on VBR9. The particular job has been running fine for years.

[foggy]

The OP's case is still under investigation, so I recommend you opening your own case to look into this issue. Thanks.

[widmerkarl]

Hi tellen, foggy

I worked around this issue. I connected the backup server directly to the NFS network where the NetApp resides and configured the proxy mode to "direct storage access".

This works like a charm.

I do storage snapshots every half hour, once a day a normal backup to disk and in the night a replication to another location.

I will revert it to act as before and will see what happens.

The Veeam support technician asked me to do a manual VM snapshot in vSphere client installed on backup server and delete it afterwards. That worked without a problem.

Thanks!

[plandata_at]

Have the same Problem, stoping the job and Server reboot didn't solve anything. Just opened case ID# 01821552
Using NetApp snapshots and VMware vsphere 6
Backup job worked fine with VBR 9 U1 toll now....

[doomi]

I have the same issue, but without U1. same symptoms, it runs for some weeks before it breaks again.
going to collect the logs now and open a case.

[doomi]

my case number is: 01843908

[veremin]

The first ticket is still open, the second one has been closed with VM VSS exclusion given as a workaround (which I personally I don't find as a applicable solution). So, kindly, keep working with our support engineer and update the topic, once the root cause is found. Thanks.

[doomi]

the VSS error happens very early in the job. I doubt the VMs have been contacted yet in this early stage, so I wonder where this VSS error comes from.
IMO it's either a VSS issue directly on the backup server itself or simply a false error...

what did they exclude int the "VM VSS exclusion"? the backup server itself?
we cannot exclude the VMs, because of MS SQL running on them. the transaction logs need to be truncated.

[veremin]

Based on the information that I got from our QA team, the issue seems to occur only on "backup from storage snapshots" job with AAIP enabled.

We've implemented a hot fix for this problem (should be installed on top of Update 1). So, you might want to refer to the tickets 01800880, 01835780 in order to get it.

Thanks.

[plandata_at]

Had another ticket with similar error: 01843938

In this case one VM got "stuck": I uninstalled Antivirus on the VM, rebooted VM and everything worked again.

In this case i would like to make following feature requests:

- Display problem VM in GUI instead of displaying message " Resource not ready: VSS snapshot" in complete job.
- Process the other (working) VMs and just fail problem VM. In this case job gut stuck at 0% without error, which is horrible when the cause of the problem is just one particular VM.

[doomi]

update:
I do have U1 too, as of the build number. I just didn't remember installing it

today, I've got a fix from the support, which I'll going to install soon.

[veremin]

Kindly, update the topic with the results of your findings - whether the provided hot fixes solves the issue for you or not. Thanks.

[veremin]

According to a plan, the hot fix solving the problem will be included in Update 2. Thanks.

[RubinCompServ]

I came here hoping to get some troubleshooting tips for this error in my v10 VBR, but it guess it's time to go straight to a ticket.

[Gostev]

Yeah, it's a pretty old thread in any case. There has been too many changes since then.