Home Dashboard Directory Help
Search

Backup errors with Microsoft SQL Server Backup to Microsoft Windows Azure tool by Azhar Taj


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 811600
Opened: 12/14/2013 1:44:22 PM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

While using Microsoft SQL Server Backup to Microsoft Windows Azure tool (http://www.microsoft.com/en-us/download/details.aspx?id=40740) for a SQL server running SQL Server 2008 R2 CU3 (build 10.50.4266), I get the following error while backing up a small 50 MB database:

2013-12-12 14:23:57.790    Backup    Error: 3041, Severity: 16, State: 1.
2013-12-12 14:23:57.790    Backup    BACKUP failed to complete the command BACKUP DATABASE TestDB. Check the backup application log for detailed messages.
2013-12-12 14:23:57.790    spid101    Error: 18210, Severity: 16, State: 1.
2013-12-12 14:23:57.790    spid101    BackupVirtualDeviceFile::SendFileInfoBegin: failure on backup device '{C08F2475-277F-43E8-AF8E-36FA22E7533E}1'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

The backup was performed via a query window in SSMS. The command used is as follows:

backup database TestDB to disk = 'S:\Mssql\TestBak\TestDB.bak' with init, compression, stats = 1

Backup completes successfully, as per the backup command output. The .bak backup file created also seems to be good. However, this backup was supposed to be copied to the cloud because of the rule created via the Microsoft SQL Server Backup to Microsoft Windows Azure tool. It seems that while doing that the system runs into issues and produces the above errors.
Details
Sign in to post a comment.
Posted by Microsoft on 12/16/2013 at 2:42 PM
OK. That helps. In your config file, you have the filename pattern as: filenamePattern=".bak"
In order to fire this rule, you would need to literally name your backup “C:\MSSQL\TestBak\.bak”
The pattern is intended to include wildcards, such as:
“*.bak” or “DB1*.bak” etc.

So, that explains why the tool didn’t pick up this backup and redirect to Azure. The error that you did see is strange, as it is normally associated with VDI backups, which would be active in the BackupToURL or SmartBackup features, or in many 3rd-party backup tools. Was the message reported directly to the query window, or did you see it in the log about the same time?

Kevin
Posted by Microsoft on 12/16/2013 at 1:43 PM
Can you send me directly the file
C:\ProgramData\Microsoft SQL Server Backup to Windows Azure Tool\config.xml
That will help me to understand your configuration.

Thanks
Sign in to post a workaround.