April 30, 2009 at 12:04 pm
Hi,
Iam getting the below message in the view history of the restore job in secondary server. The job is able to find the log backfile BUT failed to restore. Could you please tell me how to fix this
Found first log backup file to restore. Secondary DB: 'ABC', File: '\\ServerA\z$\logs\ABC_20090430171501.trn'
Skipping log backup file since load delay period has not expired. Secondary DB: 'ABC', File: '\\ServerA\z$\logs\ABC_20090430171501.trn'
The restore operation was successful. Secondary Database: 'ABC', Number of log backup files restored: 0Deleting old log backup files. Primary Database: 'ABC'
The restore operation was successful. Secondary ID: '068f180a-4012-4430-8f1c-a6fefe03b303'
Job schedules configured:
when I configured through the wizard, I kept all the default job schedule except for the restore job
backup 10:15am(every 15 mins)
Copy 10:15am(every 15 mins)
restore 10:20 (every 20 mins)
At 10:15 backup job done successfully
at 10:15 Copy job done successfully but no files copied (I think no files copied because of both backup n copy ran at same time. )
Checking to see if any previously copied log backup files that are required by the restore operation are missing. Secondary ID: '068f180a-4012-4430-8f1c-a6fefe03b303'
2009-04-30 10:15:00.70The copy operation was successful. Secondary ID: '068f180a-4012-4430-8f1c-a6fefe03b303', Number of log backup files copied: 0
2009-04-30 10:15:00.73----- END OF TRANSACTION LOG COPY -----
at 10:20 restore job done successfully but restoring NO backup file
Found first log backup file to restore. Secondary DB: 'ABC', File: '\\ServerA\z$\logs\ABC_20090430171501.trn'
Skipping log backup file since load delay period has not expired. Secondary DB: 'ABC', File: '\\ServerA\z$\logs\ABC_20090430171501.trn'
The restore operation was successful. Secondary Database: 'ABC', Number of log backup files restored: 0Deleting old log backup files. Primary Database: 'ABC'
The restore operation was successful. Secondary ID: '068f180a-4012-4430-8f1c-a6fefe03b303'
So do we need to set any delay in copy job schedule?
could you please recommend me how to schedule these jobs?
Thanks
April 30, 2009 at 1:51 pm
It looks to me that you have load delay setup, so you transaction log cannot be restored until that delay has elapsed.
If you don't want that delay, remove it. in SSMS, connect to the LS primary, right click on the log-shipped DB, properties, select the "Transaction Log Shipping" page. Highlight the LS secondary in the center of the page, the click the ... at the right to bring up the "Secondary Database Settings" page. Switch to the "Restore Transaction Log" tab, and in the middle is where you can set/adjust the delay.
November 4, 2009 at 4:09 am
Same problem i can see on my server.
Delay restoring backup atleast = 0 Minutes
I have tried running the restore job manually several times but it is giving same message again and again.
Job is running successfully.
Any other thoughts ?
Cheers
November 4, 2009 at 9:08 am
You're getting "Skipping log backup file since load delay period has not expired" in the history, but load delay is set to zero?
December 8, 2009 at 4:00 am
Yes it is set to zero.
I keep on running job manually several time. Job execute successfully but giving this information.
Skipping log backup file since load delay period has not expired .... Why?
December 8, 2009 at 6:31 am
Wow! You responded within 32 days. 😉
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 8, 2009 at 9:06 am
Sometimes happens...
Any reason in your mind please ?
December 8, 2009 at 9:25 am
Can you post the error message you get, since the original post here is someone else error, rather than that, if you can describe your issue, what you have tried, it would be better.
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 14, 2009 at 4:52 am
The Log-shipping restore job runs successfull but last restored file is the which was copied 2 hours earlier. All jobs (backup, copy and restore) are set to run every 15 min automaticallly. For example
Last backup job ran at 0900
Last Copy job ran at 0900 (all files copied to the destination)
Last file restored by restore job = file_date_0700.trn
I tried manually several times the same job and getting following information all the time:
Skipping log backup file since load delay period has not expired ....
As said earlier restore delay period is set to ZERO. So the job should restore all the files available whenever the restore job runs.
unable to understand this information.
Kindly help.
Cheers
January 20, 2010 at 9:41 am
Can you tell what is this "Load delay period" ?
Can we configure this somehow, somewhere ?
January 20, 2010 at 5:03 pm
Load Time Delay= Destination Database waits before it restores the T-Log
February 1, 2010 at 7:43 am
but why there is a delay when the setting is set to zero ?
can you read my detailed comments above.
March 29, 2010 at 4:23 am
Did you resolve the problem? If so please tell the procedure you followed.
August 15, 2010 at 10:54 am
I encountered the issue described after many years I had stopped working with such a legacy as Log Shipping. -:)
In short, there's a bug in the SQLLogShip application. Sometimes depending on the machine time it gets a negative number and checks if it's less than tha value of the msdb.dbo.log_shipping_secondary_databases.restore_delay column.
Try to apply the following script on the secondary server:
use [msdb];
update dbo.log_shipping_secondary_databases
set [restore_delay] = -2000000000;
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply