1. Support
  2. Knowledge base
  3. 100019281

SQL RESTORE fails with Error 'RESTORE detected an error on page (10244:1799427905) in database "<DatabaseName>" as read from the backup set'

Article: 100019281
Last Published: 2013-10-24
Ratings: 0 0
Product(s): NetBackup & Alta Data Protection

Problem

SQL RESTORE fails with Error 'RESTORE detected an error on page (10244:1799427905) in database "" as read from the backup set'

Error Message

RESTORE detected an error on page...

Solution

OVERVIEW:
SQL Restoreappears to be progressing and then after a certain percentage fails with theerror 'RESTORE detected an error on page...'
 
TROUBLESHOOTING:
Progress log <install_path>\Veritas\NetBackup\logs\mssql\user_ops\logs\<uniquelog id> on the SQL Client shows:
 
DBMSMSG - ODBC return code <-x>, SQL State <01000>, SQL Message<3211><[Microsoft][SQL Native Client][SQL Server]19 percentprocessed.>
DBMSMSG - SQL Message <3211><[Microsoft][SQL Native Client][SQLServer]29 percent processed.>
DBMSMSG - SQL Message <3211><[Microsoft][SQL Native Client][SQLServer]39 percent processed.>
...
DBMSMSG - SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]88percent processed.>
DBMSMSG - SQL Message <3183><[Microsoft][SQL Native Client][SQLServer]RESTORE detected an error on page (10244:1799427905) in database"DatabaseName" as read from the backup set.>
DBMSMSG - SQL Message <3013><[Microsoft][SQL Native Client][SQLServer]RESTORE DATABASE is terminating abnormally.>
ERR- Error found executing <restore database "DatabaseName" fromVIRTUAL_DEVICE='VNBU0-4824-1540-1223726966' with  stats = 10, blocksize =65536, maxtransfersize = 4194304, buffercount = 2, replace ,norecovery>.
16:13:20INF - Server status = 0
ERR- Error in VDS->Close: 0x80770004.
   CONTINUATION:- An abort request is preventing anything except terminationactions.
INF- OPERATION #1 of batch C:\ProgramFiles\VERITAS\NetBackup\DbExt\MsSql\restore.bch FAILED with STATUS x (0is normal). Elapsed time = 237(0) seconds.
16:13:22(371335.xxx) INF - Status = the requested operation was successfullycompleted.
 
INF- Results of executing <C:\ProgramFiles\VERITAS\NetBackup\DbExt\MsSql\restore.bch>:
<0>operations succeeded. <1> operations failed.
 
WindowsApplication Event Log on SQL Client may show EVENT ID 1 Error fromsource SQLVDI:
 
11-Oct-0816:13:18 SQLVDI Error None 1 N/A SQL1 SQLVDI: Loc=SignalAbort. Desc=Clientinitiates abort. ErrorCode=(0). Process=7464. Thread=4692. Client. Instance=.VD=Global\VNBU0-7464-4692-1223700406_SQLVDIMemoryName_0.
 
<Install_Path>\Veritas\NetBackup\Logs\Dbclientlog on SQL Client (Verbose 5) may show the job reading data before receiving aclose notification:
 
16:13:17.220[4824.1168] <4> dbc_get: INF - bytesRead = 524288
16:13:17.220[4824.1168] <4> dbc_get: INF - ObjectSize: 524288Bytes
16:13:17.220[4824.1168] <4> VxBSAEndData: INF - enteringEndData.
16:13:17.220[4824.1168] <4> readFromServer: enteringreadFromServer.
16:13:17.220[4824.1168] <4> readFromServer: INF - reading 512bytes
16:13:17.220[4824.1168] <2> readFromServer: begin recv -- try=1
16:13:17.220[4824.1168] <4> closeApi: entering closeApi.
16:13:17.220[4824.1168] <4> closeApi: client_activated_close =<1>
16:13:17.220[4824.1168] <4> closeApi: INF - FORCED EXIT STATUS 0: the requestedoperation was successfully completed
 
<Install_Path>\Veritas\NetBackup\Logs\Bptmlog on Media Server may show 'A tape access reached a filemark' and buffer delays:
 
16:13:17.256[19512.20960] <2> mpx_read_data: read short block, bytes = 32768,remainder = 0
16:13:17.272[19512.20960] <2> mpx_read_data: ReadFile returned FALSE, A tape accessreached a filemark. (1101);bytes = 0
16:13:17.272[19512.20960] <2> mpx_read_data: ReadFile detected EOM or EOF, bytes =0
16:13:17.272[19512.20960] <2> db_error_add_to_file: dberrorq.c:midnite =1223668800
16:13:17.272[19512.20960] <4> report_throughput: VBRT 1 19512 4 1 HP.ULTRIUM3-SCSI.002ABD223 0 1 0 42208 42208 (mpxrestore.c.1308)
16:13:17.272[19512.20960] <2> mpx_read_data: waited for empty buffer 253 times,delayed 803 times
16:13:17.272[19512.20960] <2> send_brm_msg: MEDIA NOT READY
16:13:17.272[19512.20960] <2> io_close: closing D:\ProgramFiles\VERITAS\NetBackup\db\media\tpreq\drive_HP.ULTRIUM3-SCSI.002, frommpxrestore.c.2746
16:13:17.272[19512.20960] <2> mpx_read_backup: waiting for children to terminate soexit status can be sent to bpbrm
16:13:18.272[19512.20960] <2> mpx_read_backup: A STOP RESTORE message from bpbrm needsto be processed.
 
SOLUTION:
It wasobserved that Original Backup script was using a different MAXTRANSFERSIZE to the Restore Move Script. Once the RestoreMove Script MAXTRANSFERSIZE was changed to match that in the OriginalBackup script, the restore successfully completed and the SQL database wasbrought on-line.
 
OriginalBackup Script:
 
OPERATIONBACKUP
DATABASE"DatabaseName"
SQLHOST"SQLHOST"
NBSERVER"MASTER"
MAXTRANSFERSIZE0
BLOCKSIZE7
ENDOPERTRUE
 
Restore MoveScript using MAXTRANSFERSIZE 6:
 
NBIMAGE"SQLHOST.MSSQL7.SQLHOST.db.DatabaseName.~.7.001of001.20081007023557..C"
SQLHOST"SQLHOST"
NBSERVER"MASTER"
BROWSECLIENT"SQLHOST"
MAXTRANSFERSIZE6   <- This needs to match the source backupscript
BLOCKSIZE7
RESTOREOPTIONREPLACE
RECOVEREDSTATERECOVERED
NUMBUFS2
ENDOPERTRUE
 

 

Was this content helpful?

Article Languages