Consider the following scenario. The SQL Writer service is running on a computer that has Microsoft SQL Server 2005 installed. You use SQL Server Management Studio to back up a database. Additionally, you use the Backup tool (NTBackup.exe) to back up the database files. Then, you try to restore the database from the backup set by using SQL Server Management Studio. In this scenario, you receive an error message that resembles the following:
Restore failed for Server '<ServerName>'. (Microsoft.SqlServer.Smo)
System.Data.SqlClient.SqlError: Cannot open backup device '<GUID of the device>'. Operating system error 2(The system cannot find the file specified.). (Microsoft.SqlServer.Smo)
If you examine the start date and the finish date of the backup set, you find that the dates are updated to the date that you used the Backup tool.
This problem occurs because the Backup tool uses the SQL Writer service to back up SQL Server 2005 databases. The Backup tool triggers the SQL Writer service to create a snapshot. After the SQL Writer service creates the snapshot, the Backup tool determines whether the database files are on the exclude list. The database files include .ldf files and .mdf files. If the database files are on the exclude list, the Backup tool deletes the database files from the snapshot. However, the Backup tool adds entries in the backupset
table in the msdb
To resolve this problem, stop the SQL Writer service when you use the Backup tool if you use both the Backup tool and the SQL Server 2005 backup functionality on the computer. Do not use the Backup tool to back up the database files. Instead, use the built-in functionality in SQL Server 2005 to back up the database.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
If you examine the SQL Server error log file, you find messages that resemble the following message for the user databases and for the system databases: