Suppose for maintenace i bring primary down. . i have to manually bring the secondary server online. usnig restore databse with restore.
1) so far so good. But what now. How can i re-sync the old primary with the new primary?
2) can i return the original secondary back to standby mode so that the primary can resume its role and the log shipping process proceeds.i had a look at this.
http://msdn2.microsoft.com/en-us/library/ms178117.aspx
but when ever i try to do step 3. it fails.
this is what i do .. enable log shipping on server A as primary and Server B as standby.
log shipping works and i can see the changes going through.
then i stop the jobs.
i bring server B online.
back to server A and i use the backup log option leaving the database in restoring state. norecovery.
i configure Server B as primary andd server A as secondary. The jobs fails and no chagnes are going through.
This document stays that its easy to switch roles.. but i am finding it almost impossible.Please if u have setup log sipping and have swapeed roles then let me konw..
|||
From your description it seems like you are bringing server B online before you have placed the database on server A in NORECOVERY mode.
The steps to failover from A to B are as follows:
On A:|||Hey Mark , After the roles have been swapped .. how do we go about synching up the database users ? Could you please help out with that as well !!!
Thanks
******
|||Hi you can make use of the below link,http://sql-articles.com/articles/lship/fail-lship.htm
you can make use of the stored procedure
Code Snippet
sp_change_users_login
Thanxx
Deepak
No comments:
Post a Comment