Backup Job Failing due to Unable to release guest.

One of backup jobs are failing with the following error:

"Processing SEVER1 Error: Unfreeze error: [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: [{a65f4462-5ea8-4ebc-9dbd-a0465426912a}]. Instance ID: [{54654edf-a345-470b-9bcf-214245bf339b}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_SNAPSHOT]. Error code: [0x800423f4].]"

I use Veeam Backup and Replication 9.5 and I am on VMware version 6.5.
NJ-EWhiteAsked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Common Issue, Disable Application Aware processing on the Job! (as a workaround, the issue is because of the Quicesing of the VM disk, which fails because of VSS).

Many issues reported here on EE, if you search VSS and Veeam, not many fixes! if at all!

see here, what is common, Windows,  Veeam 9.5, VSS and SQL Writer....

Search here

all seems to resolve around third party VSS writers or the SqlServerWriter]

Veeam will tell you it's a Microsoft fault!, but seems to be more on an issue with 9.5 than 9.0!

You could try changing VSS account permissions, do not run too many jobs at once..... all the suggestions are in the previous questions and answers.
0
 
Hello ThereSystem AdministratorCommented:
Please check this link. It talks about a known issue and provides a link to a KB that should solve it.
https://www.veeam.com/kb1944

Also check in the properties of the virtual machine if "Integration Services" -> "Backup (Volume snapshot)" is unchecked.
0
 
NJ-EWhiteAuthor Commented:
When you said to check the properties of the virtual machine if "Integration Services" -> "Backup (Volume snapshot)" is unchecked, where would I find that.

I've looked, but didn't see it as aoption.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
That's rubbish, and for Hyper-V!

I'm afraid you wasted your time, there is no Integration Services on VMware VMs!
0
 
NJ-EWhiteAuthor Commented:
I'm going to apply the patch today and will let you know how it works on Monday.

Thanks for all the input.
0
 
NJ-EWhiteAuthor Commented:
I'm thinking I wasn't suppose to apply the patch on to the vm server, but on the backup and replication pc, because although the backup finally ran to completion on Fri and Saturday night, it also blocked all access to the D: drive on the VM Server.  I was getting E:\ is not accessible.  Access Denied.  I was up with Dell Support until 5am this morning.  He eventually, copied the drive to another Server and we were able to open it, but when we moved it back to our Data Server, we got the same message.  So we renamed the old drive letter to E: and copied the old drive to a newly created D: drive and was able to access the data on the D; drive.  However, the newly E: drive is with is still configured on Disk1 in Disk Management is still inaccessible.  Any idea's ?Error1.PNG
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
I think I would open a new related question on the recent last post.
0
 
NJ-EWhiteAuthor Commented:
OK!  Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.