I sought assistance in the SQL High Availability and DR forums, but was not able to resolve this issue.

http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/65540244-0957-4c2d-868e-a817c2e49de5/#33f82460-529e-4491-8b8f-dde1d07a1921

I am getting VSS errors on a protected server. -- 

This is with both with DPM 2010, and with a DPM 2012 SP1 RU2 box trying to protect a Windows 2012 Server Running SQL 2012 SP1. I am aware that the local NT Authority\System needs the sysadmin role to the instance - Errors on the SQL 2012 SP1 Server --

Event ID - 1, SQLVDI   --   

SQLVDI: Loc=SVDS::Open. Desc=Open(Control). ErrorCode=(5)Access is denied.
. Process=1788. Thread=8844. Server. Instance=DW. VD=Global\{C49FD3D9-F417-4EB1-A713-25ADF5CEB237}1_SQLVDIMemoryName_0. 

--------

Event ID - 8229, VSS

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: {f07785c1-4c66-4f49-8128-a3519c620a0d}
   Command Line: "C:\Program Files\Microsoft SQL Server\90\Shared\sqlwriter.exe"
   Process ID: 5388

--------

Event ID - 3041, Backup  -- sample event - there is one for every database.

BACKUP failed to complete the command BACKUP DATABASE master. Check the backup application log for detailed messages.

<Security UserID="S-1-5-18" /> -- 

Errors from the DPM 2012 SP1 RU2 server --

Event 3106, DPM-EM -- stating that the VSS writer is in a bad state -- ID:30111

The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The writer experienced a non-transient error.  If the backup process is retried,
the error is likely to reoccur.
 (0x800423F4))

Please check that the Event Service, the VSS service and the shadow copy provider service is running, and check for errors associated with these services in the Application Event Log on the server dc-sc-data.msb.priv. Please allow 10 minutes for VSS to repair itself and then retry the operation.
For more information on this error, go to http://go.microsoft.com/fwlink/?LinkId=132612.

Following the error code 0x800423F4 -- from the referenced article stated that the MountVol Automount may be disabled. I tried enabling it via mountvol /e -- but there was no out put (run as administrator). Searching the Registry on multiple working 2012 SQL SP1 servers, I do not find a reg key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MountMgr\NoAutoMount

Any ideas on how to resolve the VSS errors on the protected server?

Can you explicitly add NTAuthority\System to the Sysadmin group on SQL Server 2012 and try again?

Hi Siddharth Jha -

Yes, I have verified that NT Authority\System is specifically part of the SysAdmin server role. I did some additional testing since my last post in the DPM forums, and it appears that the SQLVDI isn't actually being generated. Using both Microsoft SQL Server Backup Simulator - and WindowsBackup -  results in the same permission errors. All accounts are granted the permissions for SeCreateGlobalPriveleged - verified by whoami /priv from a command line.

I'm about to see if I can build up a side-by-side system to migrate the DataBases to as backing up using native SQL backups, and backing up backups of backups.. is exactly what I'm trying to get away from.

Until that happens - any other suggestions? 

I have the same problem with a SQL 2012  (upgraded from SQL 2008), its impossible take a valid recovery point for 3 sql bbdd, but others 8 bbdd in the same server are working good...

Any ideas?

• Proposed as answer by ctorresmen001 17 hours 7 minutes ago
• Unproposed as answer by ctorresmen001 17 hours 6 minutes ago

I have the same problem with a SQL 2012  (upgraded from SQL 2008), its impossible take a valid recovery point for 3 sql bbdd, but others 8 bbdd in the same server are working good...

Any ideas?

• Proposed as answer by ctorresmen001 Wednesday, March 25, 2015 2:30 PM
• Unproposed as answer by ctorresmen001 Wednesday, March 25, 2015 2:30 PM

I have the same problem with a SQL 2012  (upgraded from SQL 2008), its impossible take a valid recovery point for 3 sql bbdd, but others 8 bbdd in the same server are working good...

Any ideas?

• Proposed as answer by ctorresmen001 Wednesday, March 25, 2015 2:30 PM
• Unproposed as answer by ctorresmen001 Wednesday, March 25, 2015 2:30 PM

Migrated the protection from a server DPM 2012 SP1 to other server DPM 2012 R2 UR4 and now working... in spanish we say: "matar una mosca a caonazos".