February 7, 2014 at 9:47 pm
I am facing issue while backing up database on one of the drive, it works fine on rest of the drive. Error below:
Location: mediaWrite.cpp:690
Expression: (m_pWriteBuffer->GetCurrentSize ()% GetBlockSize ()) == 0
SPID: 55
Process ID: 13212
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
Location: mediaWrite.cpp:690
Expression: (m_pWriteBuffer->GetCurrentSize ()% GetBlockSize ()) == 0
SPID: 55
Process ID: 13212
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
Msg 3624, Level 20, State 1, Line 1
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
SQL Server Version:
Microsoft SQL Server 2012 (SP1) - 11.0.3128.0 (X64) Dec 28 2012 20:23:12 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
February 7, 2014 at 9:51 pm
Since you are able to back this database up to a different volume it sounds like the drive that is failing might have some problems. This could be anything from it being write-protected to physical errors.
That is assuming you are performing a full backup successfully to a different drive.
I would run CheckDB against the database just to make sure.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
December 5, 2014 at 10:47 pm
I get the same thing. On an Iscsi mount
Writing the same db to my fibre lun's is no issue.
Location: mediaWrite.cpp:582
Expression: (m_pWriteBuffer->GetCurrentSize ()% GetBlockSize ()) == 0
SPID: 53
Process ID: 1428
Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally.
Msg 3624, Level 20, State 1, Line 1
A system assertion check has failed. Check the SQL Server error log for details. Typically, an assertion failure is caused by a software bug or data corruption. To check for database corruption, consider running DBCC CHECKDB. If you agreed to send dumps to Microsoft during setup, a mini dump will be sent to Microsoft. An update might be available from Microsoft in the latest Service Pack or in a QFE from Technical Support.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply