SQL Server 2008 R2, Windows 7 x64, Windows Backup, VSS, SQL Writer Service - by Olaf Pietsch DETECON

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 573067 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 7/4/2010 3:38:16 AM
Access Restriction Public


On windows 2008 R2 we use windows backup to backup the SQL Server database files while SQL Service is running. (The SQL Server database files were not excluded.) In the error log of SQL Server we found entries like:
... I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
... I/O was resumed on database master. No user action is required.

I understand these entries showing that the ntbackup with VSS-Service, SQL Writer Service and SQL Server works correctly. The database files are backup in a consistent state.

Doing the same on Windows 7 (with running SQL Server) we could _not_ find any similar entry in the SQL Server error log mentioned above after backup has finished. 

We are now unsure that the database files are backup in a consistent state with Windows 7 backup while SQL Service is running.

Sign in to post a comment.
Posted by Stefan Falk on 7/29/2010 at 9:33 AM
Hello everybody,

This issue has an impact for me as a software developer running SQL Server Developer Edition locally. Windows Backup definitely should include other VSS writers, or at least have an opt-in choice available to do so. What sense do VSS writers make if, without our knowing until now, they aren't used at all?

The same holds true for Windows 7 Hyper-V VMs with SQL databases, if just the VMs are backed up (using Data Protection Manager, for example), and consistency entirely depends on the VSS writers inside the VMs. Not a quite usual scenario, but still possible I guess.

Btw, what was the reason for the backup team to change that in Windows 7? Are there so bad VSS writers out there?

Best Regards,
Stefan Falk
Posted by Ralf Dietrich - datafino GmbH on 7/24/2010 at 4:47 PM
As you're writing that win 7 nativly has no option to include the requested feature - it might move to the windows client team to put this feature back to us as soon the next SP ships.
It's usually not easy to have consistend backups for clients but with a two step approach it becomes more complex and resides outside te scope from most business users. (please be aware that currently the SQL Express Edition does not support SQL Agent!)
Maybe they will include this ability for the sql writer feature in business editions of windows 7 only.
Posted by Microsoft on 7/13/2010 at 4:41 PM
As confirmed to me by the Windows backup team, Windows 7 Backup explicitly excludes any Writer which is not itself part of Windows. This means that the Windows backup app on Win7 excludes the SQLWriter, which is why you don't see any log entries from it.
On the Server backup app, they do pull in more Writers sucn as SQL Server so you see the log entries as expected.

The recommendation would be to use TSQL to back up the databases on Win7. This has the advantage that TSQL backup only includes the allocated extents within the database, so backups will be smaller.
If you need to archive, you could then use Windows Backup to save the TSQL backup files themselves.
Posted by Microsoft on 7/9/2010 at 9:51 AM
I am contacting the Windows Backup team.
I recall a conversation with them about Windows Backup specifically excluding any writer which was not part of the System backup.
This would explain the lack of log entries on Win7, as the SQL Writer would not be invoked on that platform.

I need to both verify my memory and get details.
I will keep you posted when I hear back.

Kevin Farlee
SQL Server Storage Engine PM