December 10, 2008 at 5:32 am
Hi,
I am new to this logshipping concept and tried to configure LogShipping for my Database, in this set up i had two servers (Sql Servers). I was not having the Monitor server instance.
In the view history of the job which was used to LSRestore_ and LSCopy_ it shows success and doesnt have any error, but my secondary database is still showing as restoring...
So can i access the Db in the Secondary server to check whether the Primary and secondary Db is in synch or not. And also i would like to know how to access the secondary database.
Please let me know about this.
With Regards
Dakshin
December 10, 2008 at 6:20 am
From your description I understand that your logshipping is working fine. And you can't access the database.
Now there are two scenario one is you can keep your secondary database in Read_Only mode or Restoring mode. In your case it's Restoring mode hence you are not able to access the db. Read_Only generally used in case database is require for read_Only purpose and for short period of time.
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
December 10, 2008 at 11:21 am
2 options for restoring LS DB on the Secondary Server
NORECOVERY mode - it's not accessible, period, continues to restore future TLOGS
STANDBY mode - read-only, continues to restore future TLOGS
Log Shipping for 2005
http://msdn.microsoft.com/en-us/library/ms187103(SQL.90).aspx
December 31, 2008 at 3:04 am
Hi,
How to make log-shipped database to be available for queries.
I have MyDB in one Server which is used for Log-shipping and in the other Server MyDB is getting Logshipped. Now how do i cross check the DML Operations done in MyServer for MYDB is also been made in the other Server which is getting log-shipped.
In the sence can i execute a Select Statement to the logshipped DB in the other Server, even still my DB in My Server is active.
With Regards
Dakshin
December 31, 2008 at 4:23 am
Your questions were really answered by Jerry. It appears that you have LS configured in NORECOVERY mode which is not going to allow you to query the database to ensure that you are seeing the transactions unless you failover so that database is in a state that you can query from it. Could be more work than what you are looking for. You can look at the status of Log Shipping through some stored procedures - check out BOL topic for Log Shipping Status.
If you need to be able to query the database on a regular basis then you should consider using the STANDBY mode. Read up on both options in the link that Jerry provided and you should have most or all the information you need.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
December 31, 2008 at 4:38 am
Thanks for the information, I Wish You A Very Happy New Year 2009
December 31, 2008 at 4:56 am
Thank you! Same to you!
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
January 3, 2009 at 12:07 am
Hi,
I have a doubt and want to know how to make this to work in logshipping.
I have a chat Db in my Primary Server, i have enabled this for logshipping with Recovery Mode. Once i have configured the logshipping with my secondary server for the chat Db, i have made some manupulations like i have inserted few records, update few and deleted few. Now assuming that the chat Db in Primary Server went wrong. I want the Secondary DB which was in the Secondary Server to view whether the changes which was done to my Primary Chat Db in Primary server has also changed the secondary servers chat Db which was configured for Logshipping.
Please let me know how to make this happen.
With Regards
Dakshin
January 3, 2009 at 12:44 am
You will need to take the tail log backup (if you are able to take) of the primary database, copy this log backup on the secondary database. Restore this log backup and put the secondary db in RECOVERY mode. Once the database is in recovery mode, you will be able to use it normally. You'll need to to a role change of the primary and secondary servers. and point all your applications to the new primary servers either by chaging IP and Name of the new primary server or changing the DNS... (in most cases these solutions work)
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/udb9/html/2d7cc40a-47e8-4419-9b2b-7c69f700e806.htm
---------------------------------------------------------------------
Also, if you just want to make sure if logs are successfully getting restored to the secondary database, you'll need to change the restoration job from NORECOVERY mode to STANDBY mode as pointed by Jerry. Under NORECOVERY mode you wont be able to query your database where as in STANDBY mode you'll be able to read from the database (DB remains in read-only mode).
---------------------------------------------------------------------
January 3, 2009 at 1:44 am
Ok Sir, Thanks a lot i tried and i was able to obtain that. Thanks a lot all of you who helped me in this aspect.
With Regards
Dakshina Murthy
January 5, 2009 at 2:22 am
dakshinamurthy (12/10/2008)
Hi,I am new to this logshipping concept and tried to configure LogShipping for my Database, in this set up i had two servers (Sql Servers). I was not having the Monitor server instance.
In the view history of the job which was used to LSRestore_ and LSCopy_ it shows success and doesnt have any error, but my secondary database is still showing as restoring...
So can i access the Db in the Secondary server to check whether the Primary and secondary Db is in synch or not. And also i would like to know how to access the secondary database.
Please let me know about this.
With Regards
Dakshin
For that u have to configure secondary server on stand by mode. otherwise u can not read without recover.
January 6, 2009 at 4:17 am
Hi,
I am getting the following error while working on Logshipping. Please suggest what to be done.
Cannot open backup device '\\serverip\Logshipping\DB.bak'. Operating system error 5(Access is denied.).
RESTORE FILELIST is terminating abnormally. (Microsoft SQL Server, Error: 3201)
I have a doubt while configuring or seting up Logshipping Should we have all the Servers
under a single domain and the SQL Server agents should be running under a single account.
With Regards
Dakshina Murthy
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply