It's funny you posted that because an hour ago I actually started a backup using the Windows backup utility. It completed successfully and I was coming back to report my findings. There was no RollbackSnapshotTempDB left over and no errors in either the SQL or Windows logs. So even though SSR is just using the Microsoft VSS Provider, there must be something that is different.
I can see in the SQL logs where the snapshots were created, very similar to how the logs look when SSR is running a backup, but there was a difference. When both the SSR and Windows backups are running you will see each of these log entries in the SQL log, one for every database on the server:
Date 7/26/2013 12:53:22 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid105
Message
I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
Date 7/26/2013 12:53:23 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid105
Message
I/O was resumed on database model. No user action is required.
Date 7/26/2013 12:53:25 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source Backup
Message
Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 169, first LSN: 75:653:34, last LSN: 75:668:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{7289D6DB-5BCC-4154-8A68-918138C6D375}1'}). This is an informational message only. No user action is required.
With the Windows backup each database was reported as backed up by the last message and that was it, no more backup related messages in the SQL log. However when the SSR backup runs there are additional messages in the SQL log that look like this:
Date 7/26/2013 12:40:25 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid183
Message
Starting up database 'RollbackSnapshotTempDB{C4CF49CB-870B-47B5-BAE2-835956D9BB98}'.
Date 7/26/2013 12:40:26 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid183
Message
CHECKDB for database 'RollbackSnapshotTempDB{C4CF49CB-870B-47B5-BAE2-835956D9BB98}' finished without errors on 2013-07-26 09:53:44.937 (local time). This is an informational message only; no user action is required.
Date 7/26/2013 12:40:26 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid183
Message
Setting database option RECOVERY to SIMPLE for database RollbackSnapshotTempDB{C4CF49CB-870B-47B5-BAE2-835956D9BB98}.
Date 7/26/2013 12:40:26 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid183
Message
Setting database option SINGLE_USER to ON for database RollbackSnapshotTempDB{C4CF49CB-870B-47B5-BAE2-835956D9BB98}.
These 4 messages repeat a dozen or so times and then stop. The name of the database that is shown in these messages matches the RollbackSnapshotTempDB database that is left over after SSR backup completes. After the above messages stop these errors start showing up:
Date 7/26/2013 12:48:09 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid5s
Message
Error: 17053, Severity: 16, State: 1.
Date 7/26/2013 12:48:09 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid5s
Message
LogWriter: Operating system error 21(The device is not ready.) encountered.
Date 7/26/2013 12:48:09 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid5s
Message
Write error during log flush.
Date 7/26/2013 12:48:09 PM
Log SQL Server (Current - 7/26/2013 12:53:00 PM)
Source spid92
Message
fcb::close-flush: Operating system error (null) encountered.
So all of the above messages are what show up in the SQL log. What follows are similar messages that show up in the Windows Application log. First these messages appear near the beginning of the SSR backup job:
Log Name: Application
Source: SQLWRITER
Date: 7/26/2013 12:40:35 PM
Event ID: 24583
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: servername
Description:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3724
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: Cannot drop the database 'RollbackSnapshotTempDB{C4CF49CB-870B-47B5-BAE2-835956D9BB98}' because it is being used for replication.
Log Name: Application
Source: VSS
Date: 7/26/2013 12:40:35 PM
Event ID: 8229
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: servername
Description:
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.
Finally, these messages show up shortly after the SSR job finishes and seem to correlate exacly with similar messages in the SQL log:
Log Name: Application
Source: MSSQLSERVER
Date: 7/26/2013 12:48:09 PM
Event ID: 5084
Task Category: Server
Level: Information
Keywords: Classic
User: username
Computer: servername
Description:
Setting database option OFFLINE to ON for database RollbackSnapshotTempDB{C4CF49CB-870B-47B5-BAE2-835956D9BB98}.
Log Name: Application
Source: MSSQLSERVER
Date: 7/26/2013 12:48:09 PM
Event ID: 17053
Task Category: Server
Level: Error
Keywords: Classic
User: N/A
Computer: servername
Description:
LogWriter: Operating system error 21(The device is not ready.) encountered.
Log Name: Application
Source: MSSQLSERVER
Date: 7/26/2013 12:48:09 PM
Event ID: 17053
Task Category: Server
Level: Error
Keywords: Classic
User: username
Computer: servername
Description:
fcb::close-flush: Operating system error (null) encountered.
