Day 27: Log Shipping Errors
Log shipping is another tool for High availability it will generally have primary and secondary server, Full Backup restores at both location and then Tlog backups will copied to secondary server and restore.
The step by step and detail information about log shipping with related links are blog here.
Like replication or any other High availability tools, you can use one way from lower version to higher version, means your primary sever should be “LOWER” version and “SECONDORY” should be higher version, you cannot restore backup from sql server 2005 and restore to sql server 2000(should by other way round )
Generally, everything goes good things will not have any issue on it, as log shipping is very simple and easy to maintain.
Some errors we get in log shipping is as follows:
- Description of error message 14420 and error message 14421 that occur when you use log shipping in SQL Server
For sql server 2000
Error message 14420
Error: 14420, Severity: 16, State: 1
The log shipping primary database %s.%s has backup threshold of %d minutes and has not performed a backup log operation for %d minutes. Check agent log and logshipping monitor information.
Error message 14421
Error: 14421, Severity: 16, State: 1
The log shipping secondary database %s.%s has restore threshold of %d minutes and is out of sync. No restore was performed for %d minutes. Restored latency is %d minutes. Check agent log and log shipping monitor information.
Below link shows detail information about
- when the primary and secondary server backup and restored is miss matched due to missing tlog backup you may get error
Msg 4305, Level 16, State 1, Line 3
The log in this backup set begins at LSN 22000000018800001, which is too recent to apply to the database. An earlier log backup that includes LSN 21000000002500001 can be restored.
Msg 3013, Level 16, State 1, Line 3
RESTORE LOG is terminating abnormally.
Generally for such issue you have to apply the Tlog backup restore sequentially, by any chance if you miss the tlog backup(Lost), you make have to start again with FULL backup and then restoring tlog backup their after.
- Sometime due to permission issue you may get an access denied error
The Service account on the Production and the Stand-By server must have the same account