June 29, 2009 at 4:21 pm
Hello all,
1.Configured log shipping between primary and seconday succesfully
2.Now, I want to brong the secondary onlile. For this I did the following:
a) Copy all the Tlogs to secondary server and restore the last tlog with WITH RECOVERY option to bring the database online.
b)In primary server , I have scripted the login using the Script availble in the link http://support.microsoft.com/kb/918992/ and ran in the secondary server and bring the secondary database online and every thing is fine.
3) Now, what shoul I do go back to the previous step. i.e make the original primary database as again primary and secondary as secondary agian?
4) I already moved the logins from primary to secondary in step2, what should I do in future one more time to bring the secondary online?
Do I need to Script the logins again using the script availble in the link http://support.microsoft.com/kb/918992/ and ran in the secondary server and bring the secondary database online agian or No need to transfer the logins for the second time?
5) If only couple of logins created after the first time transfer of logins to secondary, I can create those 2 logins manually in the secondary or do I need to transfer all logins one more time?
6)We have 10 databases in the primary server instance and we are configuring log shipping for only one database.
Now how to script and transfer the users and logins related to that database only after bringing that log shipped database in secondary online??
how this works in real time?
June 29, 2009 at 4:41 pm
IF you have updated the secondary whilst it was online you will have to back it up and then restore it from that same backup with norecovery.
copy the same backup to the primary and restore with recovery.
Move any old transaction log backups in the logshipping shares out of the way (on both sides). Just start running the SQLAgent logshipping jobs again.
Having copied over the logins once, if all your logins are windows authenticated you can schedule the SSIS transfer logins task to keep the two servers in line. Don't use this for SQL authenticated ids, it changes the passwords!
If you have SQL authenticated ids and they don't change too often manually keeping them in line good as anything. Run the sp_help_revlogin script on a regular basis as well and keep the output on the secondary server, then you know you can always recover the ids.
script out their default language and any server roles assigned as well.
---------------------------------------------------------------------
June 29, 2009 at 4:58 pm
6)We have 10 databases in the primary server instance and we are configuring log shipping for only one database.
Now how to script and transfer the users and logins related to that database only after bringing that log shipped database in secondary online??
could you please tell me how can we do the above
and we have all sql authentication logins
June 30, 2009 at 2:31 am
could you please tell me how to achieve step 6...
June 30, 2009 at 4:13 am
If they are not changing often I would do this manually, run sp_help_revlogin and edit the output to only include the logins you want, then load them in.
---------------------------------------------------------------------
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply