Discussions specific to the VMware vSphere hypervisor
Post Reply
jbarrow.viracoribt
Expert
Posts: 184
Liked: 18 times
Joined: Feb 15, 2013 9:31 pm
Full Name: Jonathan Barrow
Contact:

SQL writer error: Backup type 5 not supported

Post by jbarrow.viracoribt » Nov 20, 2014 3:48 pm

We're seeing this error show up on one SQL server that has an express edition of SQL installed:

Image

This article seems to state a possible fix but this isn't Veeam specific solution. Would this be a suggested fix?

https://kb.acronis.com/content/8414

Just a heads up, this seemed to start after we upgraded to 8.0.

foggy
Veeam Software
Posts: 18123
Liked: 1536 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: SQL writer error: Backup type 5 not supported

Post by foggy » Nov 20, 2014 4:41 pm

How about the actual backup job? Does it produce any errors/warnings? Have you contacted support with this?

jbarrow.viracoribt
Expert
Posts: 184
Liked: 18 times
Joined: Feb 15, 2013 9:31 pm
Full Name: Jonathan Barrow
Contact:

Re: SQL writer error: Backup type 5 not supported

Post by jbarrow.viracoribt » Nov 20, 2014 9:02 pm 1 person likes this post

Error was:

Code: Select all

11/20/2014 8:06:38 AM :: Failed to prepare guest for hot backup. Error: VSSControl: -2147212300 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: [{a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}]. Instance ID: [{77c817e0-bca1-41d3-8e23-1a21cef54c05}]. Writer's state: [VSS_WS_FAILED_AT_PREPARE_BACKUP]. Error code: [0x800423f4]. 
Looks like I may have found it. The account that veeam was using, may not have been flagged as a SQL admin. Once I added that account to our SQL admins group, the job seemed to start running properly again.

foggy
Veeam Software
Posts: 18123
Liked: 1536 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: SQL writer error: Backup type 5 not supported

Post by foggy » Nov 21, 2014 11:01 am

Jonathan, thanks for providing the actual resolution. Lack of permissions can indeed be the reason of VSS failure.

Post Reply

Who is online

Users browsing this forum: Bing [Bot] and 29 guests