May 6, 2013 at 8:42 am
Hi,
I have a 3 node virtualized cluster running on Windows 2008R2 and SQL 2012SP1 in an AG group. Nodes 1 and 2 backup fine and the VSS provider works as it should. On the 3rd node the VSS SQL provider crashes when a job runs through. The errors are below-
Cannot open backup device '{A12661EE-E2A5-4314-BB71-C574C9BB1756}6'. Operating system error 0x80070002(The system cannot find the file specified.).
SQLVDI: Loc=SVDS::Open. Desc=Open(Control). ErrorCode=(2)The system cannot find the file specified.
. Process=1424. Thread=4516. Server. Instance=MSSQLSERVER. VD=Global\{A12661EE-E2A5-4314-BB71-C574C9BB1756}6_SQLVDIMemoryName_0.
A VSS writer has rejected an event with error 0x800423f4, The writer experienced a non-transient error. If the backup process is retried,
the error is likely to reoccur.
. Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer.
Operation:
PrepareForSnapshot Event
Context:
Execution Context: Writer
Writer Class Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Name: SqlServerWriter
Writer Instance Name: SQL Server Code-Named 'Denali' CTP2:SQLWriter
Writer Instance ID: {283f2144-d32b-4fe6-883b-12e0d67b4203}
Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
Process ID: 3800
I have removed and reinstalled the VSS provider for SQL 2012 with no change in behavior as well as Googling the various resources available to fix the VSS provider. SQL 2012 still seems a bit new so I am not much that is specific to this version, but I can see in the errors that some file is missing but how can I found out what exact file is missing.
Any thoughts or ideas someone might have would be much appreciated.
Thanks
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy