December 15, 2008 at 12:01 pm
I have a customized log shipping procedure that does not seem to be working properly from my primary to secondary server. It runs fine all day and then starts to fail stating that the LSN number is to early to apply. In order to fix it I have to take a full backup and re-establish log shipping. I look at the system backupset table on the primary server and the lsn numbers seem to be in sequence. I also ran a profiler trace and did not see any operations being performed that would cause log shipping to fail. My questions are:
Since this is 2005 shouldn't the transaction log backups start to fail (which is not the case) on the primary side if the next transaction log backup is not able to be restored?
What else can I look into as to why this is failing?
I have this same log shipping procedure running fine on all my other servers except for this particular one.
Thanks in advance.
January 28, 2009 at 7:22 pm
My questions are:
Since this is 2005 shouldn't the transaction log backups start to fail (which is not the case) on the primary side if the next transaction log backup is not able to be restored?
No, SQL Server doesn't take responsibility for the log backups. Its upto the users to validate the backup files before they send it to secondary server. Therefore, you may have to add functionality of verifying yuor backups before you ship it to your secondary server.
What else can I look into as to why this is failing?
As its your custom built process, during restoration process on secondary server, you have to make sure that the file you are restoring is with correct required LSN. If not, then send a notification message for any failure to the concerned group.
February 26, 2009 at 9:20 am
did you resolve this?
If not I would look for jobs backing up or truncating your logs outside of your log shipping process. Such actions would be reported in the errorlog (a truncation would not show up in msdb)
---------------------------------------------------------------------
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply