Comments
3 comments
-
I'm sure he's already mentioned it, but you probably need the MAXDATABLOCK argument that's available in one of the patched versions.
-
It's backing up to a local drive so can't use MAXDATABLOCK prarameter.
-
Has anyone sent you a patch for a memory write error in the extended stored procedure? Maybe the thread is quitting because of a memory issue. Could also be the case that the hard disk really is out of space.
Add comment
Please sign in to leave a comment.
Internal I/O request 0x7F0E74A0: Op: Write, pBuffer: 0x22160000, Size: 1048576, Position: 51790741504, UMS: Internal: 0x0, InternalHigh: 0x100000, Offset: 0x9E50000, OffsetHigh: 0x6, m_buf: 0x22160000, m_len: 1048576, m_actualBytes: 1048576, m_errcode: 112, BackupFile:
BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'SQLBACKUP_1787EFF4-45E0-4B65-9D40-C2EA5D46D3E0'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).
BackupMedium::ReportIoError: write failure on backup device 'SQLBACKUP_1787EFF4-45E0-4B65-9D40-C2EA5D46D3E0'. Operating system error 112(There is not enough space on the disk.).
Thanks
-Paul