September 14, 2008 at 6:12 pm
first i would like to thank all the contributors to make this forum so useful..Now, i was practising log shipping and and couple of questions regarding it..if some body could share their ideas that will be nice....
1)i know dat we cannot automatically failover in log shipping..so how do u manually failover the primary...
2)how to transfer logins from primary to secondary....i know that the users will be transfered...i tried using sp_change_users_logins to map the logins with users..the query ran successfully but i wasnt able to logon with the sql login on the secondary...
3)can we perform log shipping on same instance..i know it doesnt makes sense..but just curious to know...
4)and if there are like 100 dbs and we need to bring them back on the secondary do we have to manually go to each db and restore it..or can we run a script on the secondary for each db by changing the name..
thanks in advance for responding to my questions...
September 16, 2008 at 7:53 am
1) you'll have to read up on this but basically you ensure the latest logs are copied from the primary to failover, restore the logs, stop all log shipping jobs and recover the databases to bring them online
2) you may need to copy the users from the primary to failover. What errors did you get when you tried to log in?
3) yes
4) you need to do it manually or you can create a script - the script is likely to be complex though
September 18, 2008 at 11:55 am
Hi
you can write a script to restore all the databases, once you need to bring the warm servers live then run this script, the same involves in Logins as well, you can script the logins as a daily process and store it in a seperarte location( or when ever there is a new login added).
The best pratice is to keep an up to dated script file on the warm server, so it will be usefull to run that in case of emergency.
Cheers
🙂
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply