Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
udaykathaiyan
Starting Member
2 Posts |
 Posted - 2007-09-06 : 14:13:26
|
| Hi I am new to Forum. So not sure if i am posting my problem under the right topic. We have a sql server 2005 enterprise edition 4 way cluster on windows 2003 advance server. I am logshipping these database to a different server at a different location.My logshipping went fine until one the cluster server failed and the server instance failed over to another node.The backup that happened around that time got copied over to the secondary by the copy job.The log file that got copied to the secondary server tried restoring and i think it failed int he middle of restoring it.(You would think that the sql would knoe if the backup is in complete and will move on to the next file. Not sure what happened there.)There is no indication of the *.TUF file in the directory where i have the log files. I tried restoring it manually and i got the following errorMsg 4319, Level 16, State 3, Line 1A previous restore operation was interrupted and did not complete processing on file 'sessionlog1'. Either restore the backup set that was interrupted or restart the restore sequence. Msg 3013, Level 16, State 1, Line 1RESTORE LOG is terminating abnormally. I looked in the msdb..log_shipping_secondary_databases and looked for the last file that it restored and tried restoring it again with the following restore command by removing and adding some of the keywords that you see after the "WITH" clause. MSFT do not recommand to use continne_after_error unless its absolutley necessary. I stilll get the above error. restore log sessiondata from disk = 'I:\sql13qasm\logs\sessiondata\sessiondata_20070901124516.trn'with restart, CONTINUE_AFTER_ERROR, norecovery When i add the restart int he with clause, The restart-checkpoint file 'J:\Microsoft SQL Server\MSSQL.5\MSSQL\Backup\sessiondata.CKP' was not found. The RESTORE command will continue from the beginning as if RESTART had not been specified.Msg 4319, Level 16, State 1, Line 1A previous restore operation was interrupted and did not complete processing on file 'sessionlog1'. Either restore the backup set that was interrupted or restart the restore sequence. Msg 3013, Level 16, State 1, Line 1RESTORE LOG is terminating abnormally. I checked it the backup directory and i can't locate the .CKP file. Does anyone ever come accross this issue? Is there anyother way i could recover this DB in a standby or norecovery mode. Any kind of help to resolve this issue (beside copy the full backup and redo the whole log-shipping process again) would be appreciated. sicne my primary and secondary server are totally ina different location, i need to ship a tape, if i need a full backup. This is the 3rd time its happening on that cluster. its frustrating to ship a tape everytime this happens. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2007-09-06 : 15:29:59
|
| If you have any recent full backup and the entire transaction log chain, then you can use that to get log shipping going again. We use log shipping for our SQL Server 2000 systems only. For all 2005 systems, we use database mirroring. Log shipping is just too troublesome to use when database mirroring accomplishes the same thing (in our situation at least) and it is so much easier to setup.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
udaykathaiyan
Starting Member
2 Posts |
Posted - 2007-09-06 : 20:20:36
|
| The server is in a remote location.I want to leave the full backup resotores as the last option. |
|
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-09-06 : 22:14:57
|
| Try restore failed log backup again if that log backup file still exists. |
|
|
|
|
|
|
|
|
Logshipping - backup and restore