April 10, 2018 at 2:42 pm
Hello, First time posting here. I have a few unanswered questions about troubleshooting log shipping errors, and I was wondering if I could get some clarification, so here goes.
1.) Backup job is completing normally every 15 minutes, but some time after initial setup, the copy job for whatever reason fails to move a few of the backups to the secondary server. Assuming i corrected the reason for the failed copy, can i either just kick off the copy job, which will move all log backups from the backup location, or would i need to manually copy the log backups in order for them to be restored? I'm thinking that kicking off the copy job will automatically move the log backups to the secondary server (assuming they are not past the retention time set), and no manual copying is needed. I also assume that the restore job knows what LSN it is expecting, and it will be able to search through the log backups in the copy destination folder and start restoring from the correct log backup, all the way to current?
2.) If i choose to initialize the secondary DB by using the prior days full backup, say 8 hours old, I believe I will still need to restore all the intermediate backups (diff or log), up until the next log backup happens through the log shipping job correct? in essence, i need to have a complete log chain from the time the full backup completed to the time the 1st log shipped log was restored? If a backup is missing during that time, I would be better served by initializing the secondary from a fresh full backup taken during Log Shipping configuration, correct?
April 11, 2018 at 9:21 am
gloeffler - Tuesday, April 10, 2018 2:42 PMHello, First time posting here. I have a few unanswered questions about troubleshooting log shipping errors, and I was wondering if I could get some clarification, so here goes.1.) Backup job is completing normally every 15 minutes, but some time after initial setup, the copy job for whatever reason fails to move a few of the backups to the secondary server. Assuming i corrected the reason for the failed copy, can i either just kick off the copy job, which will move all log backups from the backup location, or would i need to manually copy the log backups in order for them to be restored? I'm thinking that kicking off the copy job will automatically move the log backups to the secondary server (assuming they are not past the retention time set), and no manual copying is needed. I also assume that the restore job knows what LSN it is expecting, and it will be able to search through the log backups in the copy destination folder and start restoring from the correct log backup, all the way to current?
If the copy job is failing check the permissions from the secondary to the share where the primary stores it backup files.
Make sure you know the account the secondary agent service runs under and check the remote share for access.
gloeffler - Tuesday, April 10, 2018 2:42 PM
2.) If i choose to initialize the secondary DB by using the prior days full backup, say 8 hours old, I believe I will still need to restore all the intermediate backups (diff or log), up until the next log backup happens through the log shipping job correct?
Correct
gloeffler - Tuesday, April 10, 2018 2:42 PM
in essence, i need to have a complete log chain from the time the full backup completed to the time the 1st log shipped log was restored? If a backup is missing during that time, I would be better served by initializing the secondary from a fresh full backup taken during Log Shipping configuration, correct?
A complete chain is required, yes, prior to the LS plan starting.
It breaks if there are log backups already in force by an existing backup job, remove from here if there is
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply