Article ID: 2550085
When you create a new SQL database (or it is created automatically by an application), and there are multiple backslash (\) characters defined in the database data or log file physical path (like C:\\SQL\test.mdf), you will encounter the following error when you protect this database with System Center Data Protection Manager 2010 and try to recover it to an alternate SQL instance. After you start the recovery process you will see an error in DPM console:
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)
Also on the target SQL server, where the database cannot be restored a SQLWRITER 24583 error event is logged in the Application log with the following message:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Note that backup jobs will run without any issues, and when the database is added, SQL server will accept the path with multiple backslash characters and create the database. Later when you check the physical path of the database files in SQL Management Studio, you will see only one backslash character, as the GUI hides the others.
You can check the original physical path of the database files with the following query:
SELECT * FROM Sys.Database_files
As SQL VSS Writer returns with the path visible in the result of the above query, DPM will also use this path for recovery processes.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2550085 - Last Review: May 31, 2011 - Revision: 2.0