February 14, 2014 at 1:46 am
I am logshipping Db across 2008 r2 servers. After few log backup restore, db comes to suspect mode.
one of the log restore is the culprit however verify only is good for this tlog backup.
Any idea??
Error while restore:
100 percent processed.
Processed 0 pages for database '***', file '***' on file 1.
Processed 1 pages for database '***', file '****' on file 1.
Msg 9004, Level 16, State 6, Line 1
An error occurred while processing the log for database '***'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
February 14, 2014 at 1:53 am
Have you checked the disk integrity where the log backups are moved to on the secondary server?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 14, 2014 at 2:29 am
I dosent work even after specifying restore file path same as backup location.
means I am picking same backup file
February 14, 2014 at 2:34 am
SQLb2t (2/14/2014)
I dosent work even after specifying restore file path same as backup location.means I am picking same backup file
I think you're misunderstanding what i am asking.
Log shipping has a copy job that copies the log backups from the backup location used by the primary to a specified location on the secondary. Run chkdsk for this location on the secondary to ensure the disk or filesystem is not corrupt.
Even though you have verified the backup file on the primary, if you copy the file to a disk with corruption issues the file may become unstable.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 14, 2014 at 2:45 am
I am not relying on the copied location instead now I am giving path directly to backup file with unc...e.g\\primaryserver\backup\abc.trn
February 14, 2014 at 3:19 am
restoring over a network is just as bad, why do you think the copy job moves the files locally to the secondary instance 😉
Fo you have any other errors, etc in the sql server log
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 14, 2014 at 3:37 am
manually copied to secondary server, disk verified. Error below:
Msg 9004, Level 16, State 6, Line 1
An error occurred while processing the log for database '####'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
February 14, 2014 at 4:12 am
do you have another mlocation where you can test restore the backup files
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 14, 2014 at 10:03 am
I tried restoring to the same primary server and it succeeded. So story so far is...back up of primary can be restored on primary but not on secondary. here are the SQL Server versions:
Secondary: Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Primary: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1790.0 (X64)
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply