|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 6:49 AM
Points: 1,895,
Visits: 4,155
|
|
| check how long you are keeping the tran log backups for on the primary. All I can think of if you get an out of synch error after not restoring for an hour is the tran log backup file has been deleted from the primary
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Friday, October 30, 2009 4:50 AM
Points: 264,
Visits: 883
|
|
Hi,
The line from you error message included below would seem to suggest that the log files are being located successfully but that they are unable to applied to the database.
2008-06-13 08:45:15.81 *** Error: The log backup file '\\share\folder\database_20080613041516.trn' was verified but could not be applied to secondary database 'database'.(Microsoft.SqlServer.Management.LogShipping) ***
Are you able to confirm what your restore settings are? I am wondering if there are users connected to the database and the configuration is not disconnecting the users in order to perform the restore operation and is therefore failing.
The checkbox option I am referring to can be found on the "Restore Transaction Log" tab of the wizard and is labeled "Disconnect users in the database when restoring backups"
Also, any further troubleshooting you carry out, if you could also provide details of any error messages, error log details that would be most appreciated.
Cheers,
John
--------------------------------------------------------------------------------------------------------------------------------------------------
John Sansom | www.johnsansom.com
* Calling out all SQL Server experts. Have you entered the SQL Server Guru Challenge *
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, October 07, 2009 6:35 AM
Points: 42,
Visits: 200
|
|
Hello again,
I've been using No Recovery Mode on the Secondary Transaction Log.
Do you recomend placing it on Standby Mode with the Disconnect users in the database when restoring backups activated?
I might be wrong, but won't this disconnect the users on the production server?
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 6:49 AM
Points: 1,895,
Visits: 4,155
|
|
The point from the previous post is worth checking out but the original error message does contain the line :
2008-06-13 08:45:15.78 *** Error: This log cannot be restored because a gap in the log chain was created. Use more recent data backups to bridge the gap.
RESTORE LOG is terminating abnormally.(.Net SqlClient Data Provider) ***
suggesting there are transactions missing.
also, thinking about it, jjsilva, I note your out of synch' threshold is set at 45 mins, so if you do not do a restore for an hour you will get these Messages, so its not really an error just a warning you can ignore with regard to the test u did in the afternoon
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Friday, October 30, 2009 4:50 AM
Points: 264,
Visits: 883
|
|
Hi,
I would not recommend that you change the restore mode of your configuration as if you are using the with No Recover option the database will not even be accessible to users.
You can test the theory that George has outlined by manually running the various SQL Server jobs that control your log shipping configuration.
For example, run the Alert threshold job to see if it generates the error messages you are detailing. The job is typically called LSAlert_ServerName by default.
Next Manually run the copy job (LScopy_ServerName) followed by the restore job (LSRestore_ServerName).
If you now run the Alert threshold job again, and no error messages are presented then it is indeed a timing issue.
--------------------------------------------------------------------------------------------------------------------------------------------------
John Sansom | www.johnsansom.com
* Calling out all SQL Server experts. Have you entered the SQL Server Guru Challenge *
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, October 07, 2009 6:35 AM
Points: 42,
Visits: 200
|
|
Strangely It failed again at 6:45AM. (Online Backup starts at 5:00AM).
Will try to get some more info and will get back to you.
Appreciate your patience.
|
|
|
|
|
SSC Veteran
Group: General Forum Members
Last Login: Friday, October 30, 2009 4:50 AM
Points: 264,
Visits: 883
|
|
Yes please do.
--------------------------------------------------------------------------------------------------------------------------------------------------
John Sansom | www.johnsansom.com
* Calling out all SQL Server experts. Have you entered the SQL Server Guru Challenge *
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, October 07, 2009 6:35 AM
Points: 42,
Visits: 200
|
|
Hello,
just confirmed the error. It started going Out of Sync at 6:15AM and got the first Event Error at 7:00AM.
So it really seems to be something with the Online Backup.
Strangely I've checked the Backup software and the scripts are not configured to do Log Cleaning.
I already did the Schedule test to stop before Backup and restart Backup, the same errors came out.
Any more ideas? Is there any extra info you need?
Thanks once again.
|
|
|
|
|
SSCommitted
Group: General Forum Members
Last Login: Today @ 6:49 AM
Points: 1,895,
Visits: 4,155
|
|
| if a log backup is happening, or a truncate log, it will be recorded in your errorlog. go through that to see if you can find evidence of a log backup outside of your logshipping plan.
|
|
|
|
|
SSC Rookie
Group: General Forum Members
Last Login: Wednesday, October 07, 2009 6:35 AM
Points: 42,
Visits: 200
|
|
No errors or Truncate on the Logs.
Tomorrow I will have a final report from the Backup Team, but so far I can't seem to find a logical reason behind this Out of Sync on the LSRestore SQL Agent.
|
|
|
|
