August 11, 2009 at 1:39 pm
I'm just starting to setup log shipping on '05 and I notice that after the db's are synched, the status of the db on the secondary server is always (Restoring). Is this normal is or is it still trying to restore from the initial backup?
I've tested this on 2 db's so far and it shows the same status on both db's.
Thanks,
Danny
August 11, 2009 at 2:01 pm
While configuring logshipping, when configuring secondary server instance under restoration tab, there are two options 1st to to be in norecovery state and 2nd in standby state, I think you might have selected this option for this reason you are seeing database in restoring state, even though logshipping in sync.
August 11, 2009 at 3:05 pm
Yes this is normal, part of the recovery process is to restore the latest log with recovery to bring the database online. As noted previously you can setup log shipping in standy mode which allows read only access to the database but you need a process of closing the connections before the next log is restored otherwise it will fail.
August 12, 2009 at 3:24 am
Is it the same you are saying "If we set up the secondary server as standby then we have to close the connections everytime the restore job runs".
-LK
August 16, 2009 at 5:26 am
luckysql.kinda (8/12/2009)
Is it the same you are saying "If we set up the secondary server as standby then we have to close the connections everytime the restore job runs".-LK
You dont have to do that manually. All user connections are killed just before each restore operation in a standby configuration.
August 16, 2009 at 10:35 pm
All user connections are killed just before each restore operation in a standby configuration.
Yes this is the drawback of restoring database with STANDBY option. By the way, logshipping is not meant to have secondary server exactly the same at given point of time, if thats the case then you should look at replication. STANDBY option gives up an opportunity for using it as a read only database only. You can setup your timings on secondary server at after office hours making data as latest as 1 day old or let users know about the short comings of it. It is entirely a business decision. We have a setup as restoring it in morning at 8 am, 12.30 pm and 8 pm.
August 17, 2009 at 2:33 am
Which you have observed is absolutely normal.
You can also keep the database into Read_Only mode if while restoring full database you have kept that option. i.e. with STANDBY Option but in that case it will kill all the conenctions before it resotres each t-log. But DB will be available for read and reporting purpose.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply