Resource not ready: VM is being prepared for storage snapsho

[marius roma]

I can't start a backup because I see in statistics that "Resource not ready: VM is being prepared for storage snapshot by another job".
A previous replica job for the same VMs was killed "Gracefully".
How can I forche the backup job to start?
Regards
Marius

[foggy]

Marius, logs review is required, please contact support for assistance.

[powersjo]

For anyone else running into this issue: "Resource not ready: VM is being prepared for storage snapshot" here was my troubleshooting:

I had a vm where storage snapshots was not an option. The backup proxy should be doing vmware snapshots with hot add disks or network transport level backups.
I checked there were no snapshots on that vm through vcenter or the esxi host. I consolidated anyways, still same error.

i checked the logs for the job: C:\ProgramData\Veeam\Backup\"Job name" but it did not show much, it basically went straight into a resource not ready, waiting line.

I ended up powering off the vm > remove from inventory at the vmware level > re-scanned and refreshed vcenter in veeam under inventory (so the vm was gone from the veeam database) > re-add the vm to vmware vcenter > re-scan vcenter in veeam again (new database entry) > remove old vm (with specific DB ID from the job and add the same vm, that has a new DB entry, to the job) > ran the job and it worked fine.

My hunch was this was a veeam database or registry type issue so creating a new entry that way fixed my problem with this error.

[Andreas Neufert]

Thanks Powersjo,
this should not be needed. Do you have a support number with logs that we can research this issue?

[powersjo]

Unfortunately no, I just did this troubleshooting on my own. I can give you logs though if you want me to upload them somewhere.

[Andreas Neufert]

I guess this was an isolated case. For any new trouble or other customers facing same issues, please open a support case and upload logs, to avoid the above.

[jarce]

I'm having the same problem.
Case # 03995277

[jarce]

Quick follow-up in case anyone else have this problem.

A reboot of the Veeam server solved this for us.