Red Gate forums :: View topic - Hyperbac: Operating System Error 31
Return to www.red-gate.com RSS Feed Available

Search  | Usergroups |  Profile |  Messages |  Log in  Register 
Go to product documentation
SQL HyperBac 5
SQL HyperBac 5 forum

Hyperbac: Operating System Error 31

Search in SQL HyperBac 5 forum
Post new topic   Reply to topic
Jump to:  
Author Message
Matt51F1



Joined: 10 Nov 2011
Posts: 3

PostPosted: Thu Nov 10, 2011 2:46 am    Post subject: Hyperbac: Operating System Error 31 Reply with quote

(warning: this post could get lengthy....)

OK - a bit of info first....
x86, WS2003SP2 + SS2005 (build 5266)
SQL Server is running under local system account.

Hyperbac 5.4.1.5 using .BKD extension, zip compatible. (licenced)
Hyperbac is running under local system account.

Backup drive has authority to write files.

-----

Backup is failing on a 47Gb database and I cannot work out why.

Turn off Hyperbac and the backup works OK. Turn it on - fail.
Hyperbac works perfectly when on databases >10Mb.
Service is used on other servers for 200+Gb databases and no problems.

Added exclusion for .BKD to virus protection program - fail.
Shut down service for virus protection program - fail.
Run Hyperbac under different service owner (with admin auth) - fail.
Explicitly grant drive & directory auths to userid - fail.

There are a multitude of error messages and the "Operating System Error 31" makes me wonder how I keep managing to find the new age versions of "Syntax Error" Sad

There are heaps of error code 112 out there - disk space - this is not a problem as the space free far exceeds the size of the database and will allow a non-Hyperbac backup to be written (~34Gb)

ANY information would be appreciated - thanks!


SQL Server error log:
---------------------------------------------------------------
BackupDiskFile::RequestDurableMedia: failure on backup device 'E:\SQLBACKUP\CAAB32\CAAB32_backup_201111101037.BKD'. Operating system error 31(error not found).
Error: 18210, Severity: 16, State: 1.
---------------------------------------------------------------


Error in SSMS when running the backup command alone:
---------------------------------------------------------------
Msg 3202, Level 16, State 2, Line 1
Write on "E:\SQLBACKUP\CAAB32\CAAB32_backup_201111101047.BKD" failed: 31(error not found)
Msg 3271, Level 16, State 1, Line 1
A nonrecoverable I/O error occurred on file "E:\SQLBACKUP\CAAB32\CAAB32_backup_201111101047.BKD:" 31(error not found).
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.



Hyperbac Log

*******************************************************************
*
* 10 Nov 11 11:11:20.734 OPENED LOG FILE
*
HyperFile=00A12F98
FileName=E:\SQLBACKUP\CAAB32\CAAB32_backup_201111101047.BKD
OpenTime=Thu Nov 10 11:10:37 2011
OpenProcessId=6268
OpenProcessName=sqlservr.exe
ProcessAttr1=0
ProcessAttr2=0
IndexNumber=0x700000000152C
HeaderVersion=2
FileType=1
FormatVersion=0x0
CreateVersion=0x5040105
CreateOS=0x10502
FileFlags=0x4
RequiredVersion=0x0
WriteAccess=Yes
FillFactor=131072
VirtualEOF=0x104EC0000
FileActualStart=0x400
FileActualEnd=0x268A2240
LastDataBlock=0x0
FileActualMetaEnd=0x0
LastCrcOffset=0x93FD0000
SequentialOffset=0x93FC0000
LastBlockOffset=0x0
IndexType4Format=1
IndexStart=0x200
IndexEnd=0x0
OpenHandleCount=1
FileDirty=Yes
IoError=0
UpdateCount=0x0
LastIoOffset=0x0
ActiveWrites=15
FileState=0x0
LastSumOffset=0x0
AffinityMask=0xFFFFFFFFFFFFFFFF
*
*******************************************************************

10 Nov 11 11:11:20.734 HyperVirtualWrite: Failed to write block to offset: 0x104600000, Length: 0x1A00, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.31 HyperVirtualWrite: Failed to write block to offset: 0x104610000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.78 HyperVirtualWrite: Failed to write block to offset: 0x104620000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.78 HyperVirtualWrite: Failed to write block to offset: 0x104630000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.93 HyperVirtualWrite: Failed to write block to offset: 0x104640000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.109 HyperVirtualWrite: Failed to write block to offset: 0x104650000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.125 HyperVirtualWrite: Failed to write block to offset: 0x104670000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.125 HyperVirtualWrite: Failed to write block to offset: 0x104680000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.140 HyperVirtualWrite: Failed to write block to offset: 0x104690000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.156 HyperVirtualWrite: Failed to write block to offset: 0x1046A0000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.171 HyperVirtualWrite: Failed to write block to offset: 0x1046B0000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.187 HyperVirtualWrite: Failed to write block to offset: 0x1046D0000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.203 HyperVirtualWrite: Failed to write block to offset: 0x104700000, Length: 0x1A00, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.218 HyperVirtualWrite: Failed to write block to offset: 0x104710000, Length: 0x10000, Offset: 0x0. Error: -1
10 Nov 11 11:11:21.218 KD-Write: Error: 0xC0000001, fd: 0x86081100, cpos: 0x105F01A00, ToWrite: 0x100000, Written: 0x0.
10 Nov 11 11:11:21.234 KD-Write: Error: 0xC0000001, fd: 0x86081100, cpos: 0x105F01A00, ToWrite: 0x100000, Written: 0x0.
10 Nov 11 11:11:21.250 KD-HyperWrite: Return code: 0xC0000001, FileObject: 86081100, Offset: 0x105F01A00, Bytes to write: 1048576, Bytes written: 0.
10 Nov 11 11:11:21.265 HyperFlushBuffers: Previous async error: -1.
10 Nov 11 11:11:21.265 HyperProcessOperation: Failed to flush buffers: -1.
10 Nov 11 11:11:57.703 FlushCompLatches: Not flushing data due to a previous IO error: -1
10 Nov 11 11:11:57.718 HyperCloseFile: File object: 0x86081100, FileRecord: 00A12F98, Flush dirty complatches error: -1.
10 Nov 11 11:11:58.109 HyperCloseFile: Previous async error: -1.
[/b]
Back to top
View user's profile Send private message
Matt51F1



Joined: 10 Nov 2011
Posts: 3

PostPosted: Thu Nov 10, 2011 3:03 am    Post subject: New development Reply with quote

I have run a backup through changing the backup option from Compressed(Zip) to Compressed(Fast) and it worked.

The fact that it is ZIP compatible is telling me that it is linked to the virus scanner and the exclusions have not been set up correctly by the server admins.
Back to top
View user's profile Send private message
Matt51F1



Joined: 10 Nov 2011
Posts: 3

PostPosted: Mon Nov 14, 2011 6:10 am    Post subject: Wrong again.... Reply with quote

Looks like I was blaming McAfee for this problem but I managed to switch off the scanning engine and the problem continues.

Still running with the HBC2 extension but would really like to get the ZIP compatible option running without spending any more time on it.... Sad
Back to top
View user's profile Send private message
peter.peart
Site Admin


Joined: 02 Sep 2008
Posts: 362
Location: Top floor, RG towers with the cool kids

PostPosted: Mon Nov 14, 2011 4:12 pm    Post subject: Reply with quote

Thanks for your posts. Unfortunately, this is a known issue when backing up and using the zip format on some systems.

We do have it logged in our systems, and I believe that we will be releasing another version of the tool in the next few weeks that we hope will address the issue for you.

In the meantime, the workaround is to continue backing up to a different file format, like you are.

HTH!

Pete
_________________
Peter Peart
Red Gate Software Ltd
+44 (0)870 160 0037 ext. 8569
1 866 RED GATE ext. 8569
Back to top
View user's profile Send private message Send e-mail
Phil_Aronova



Joined: 06 Jan 2012
Posts: 1

PostPosted: Fri Jan 06, 2012 11:54 am    Post subject: Reply with quote

Just wanted to post here so I can be kept up to date - I'm assuming a note will be added to the thread when a permanent fix is available.

We have the very same issue on our SQL 2000/Windows 2003 machine. Once the backup file to be compressed gets over a certain size, the backup fails. In our setup we are using HyperBac to compress the Differential backups, when the DIFF was 6GB it was fine, when it was around 15GB or so the backup failed (using zip compression for portability).

Incidentally we were using the HyperBac on our SQL 2005/Windows 2003 server with similar backup sizes and zip compression, and all was well.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic All times are GMT + 1 Hour
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group