SQL Server 2005 Log Shipping question
I have setup log shipping on our production SQLServer to send the logs to a server I have at my home for a warm backup solution. The process seemed to work but then I had a problem on my secondary server - it seemd to stop working for a period of 2 weeks (I dont know why - I could not login to it and had to power it off to reset it)and I didnt notice until I did a random check. My question is will log shipping survive if the receiving server goes off line for 2 weeks ? When I bring it back on line does it go and collect all the logs it hasnt yet seen and RESTORE them correctly ? The reason I ask is because I am now seeing errors saying "cannot be restored due to a "gap in the log chain" how do I solve this issue ?
Software/Hardware used:
SQL Server 2005
Software/Hardware used:
SQL Server 2005
ASKED:
November 30, 2009 9:27 PM
UPDATED:
August 2, 2010 12:26 PM
Answer Wiki:
It will survive short gaps. The length of time it will survive is controlled by the amount of time the system keeps the transaction logs on the primary servers hard drive. Once they are deleted from there they are gone.
You'll need to do a full backup and restore it to the backup machine then the log shipping can work again.
To see all answers submitted to the Answer Wiki: View Answer History.
It will give a problem..log backups s are arranged according to the LSN.. if one of the log file is corrupted ypu can go ahead for the recovery.. so wat u can do is collect all the log files for ur primary server n replace the copy present on the secondary server n then apply i accordingly..