April 14, 2010 at 1:48 pm
we have a process on our SAN where we sync some volumes to other volumes and mount them on another backup SQL server as a backup. for the last few days the backup sql server has been getting this error when we mount one of the databases. we added a new volume and file on sunday night and the first night it sync'd OK, but the last few days we've had problems.
we're putting some indexes on it and i thought that maybe it's because the sync happened during the times i've created new indexes. the production database is up and running with no errors. we have checksum error checking enabled and Netbackup scans every db page that it backs up as well
The operating system returned error 38(Reached the end of the file.) to SQL Server during a read at offset 0x00000559192000 in file 'c:\mount\disk17\SCS_INDX3.NDF'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online. [SQLSTATE HY000] (Error 823) During redoing of a logged operation in database 'SCS', an error occurred at log record ID (1538697:147050:15). Typically, the specific failure is previously logged as an error in the Windows Event Log service. Restore the database from a full backup, or repair the database. [SQLSTATE HY000] (Error 3313). The step failed.
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply