﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / SQL Server 2008 / SQL Server 2008 High Availability  / Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ] / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sat, 18 May 2013 16:03:07 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>I'm sorry, but which part of "remapping users is BAD" is confusing for you? Why would I help you do it the wrong way when we've already told you how to do it the right way?</description><pubDate>Wed, 12 Dec 2012 07:07:03 GMT</pubDate><dc:creator>Robert Davis</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>Believe me, there's nothing difficult about the script i gave you above</description><pubDate>Wed, 12 Dec 2012 05:42:23 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>HI robert &amp; perry ya ivl follow the link and script also if needed. Before that i want to know one thing where should i execute this script for mapping the logins afterSWITCH OVER COMPLETE whether in primary server or in secondary server-----------------------------------------------------EXEC sp_change_users_login'report'andExec sp_change_users_login'auto_fix',users------------------------------------------------------Actually when we perform dc dr dill[switch back &amp; switch over ] it wont be much time for DBA to carry this activity and if i follow this script there is difficult to remmeber long script instead i want to go through the simple script which i provided above just need calification when and where to execute special thanks to u both</description><pubDate>Wed, 12 Dec 2012 02:37:07 GMT</pubDate><dc:creator>naga.rohitkumar</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>I agree with Robert, avoid re mapping unless necessary. Create the login with the correct SID, this script is also useful for generating CREATE LOGIN ... statements from a source server. The roles should be pretty easy for you to figure out ;-)[code="SQL"]SELECT		'CREATE LOGIN ' + name + ' WITH PASSWORD = ' + 		sys.fn_varbintohexstr(password_hash) +		' HASHED, SID = ' + sys.fn_varbintohexstr(sid) + 		', DEFAULT_DATABASE = ' + QUOTENAME(default_database_name) + 		', DEFAULT_LANGUAGE = ' + default_language_name + 		', CHECK_EXPIRATION = ' +		CASE		WHEN is_expiration_checked = 0 THEN 'off'		ELSE 'on'		END + 		', CHECK_POLICY = ' + 		CASE		WHEN is_policy_checked = 0 THEN 'off'		ELSE 'on'		ENDFROM master.sys.sql_logins[/code]</description><pubDate>Wed, 12 Dec 2012 02:06:06 GMT</pubDate><dc:creator>Perry Whittle</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>Delete means "remove" or "get rid of". Don't remap logins. That's bad. Create the logins correctly and there will be no need to remap anything. Use the script I gave you the link to.</description><pubDate>Tue, 11 Dec 2012 09:11:46 GMT</pubDate><dc:creator>Robert Davis</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>Hi Robert Ineed one confirmation for the alternative step about removing bcp steps suggested by you for [delete the part about copying logins]where should i execute  this script for mapping the logins afterSWITCH OVER COMPLETE whether   in primary server  or in secondary server -----------------------------------------------------EXEC sp_change_users_login'report'and Exec sp_change_users_login'auto_fix',users------------------------------------------------------</description><pubDate>Tue, 11 Dec 2012 00:19:17 GMT</pubDate><dc:creator>naga.rohitkumar</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>It should not prefered from my client side all my production severs running in logshipping -clustering environment even i know sme knowledge about mirroring and replication i din't worked on it and that to iam a satater in dba L1 hadling 3 to 4 years work</description><pubDate>Tue, 14 Aug 2012 05:53:33 GMT</pubDate><dc:creator>naga.rohitkumar</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>You also have an opportunity to upgrade from log shipping to mirroring where the failover and tailback is pretty simpler as compared to Logshipping. Food for thought.</description><pubDate>Sat, 11 Aug 2012 04:04:15 GMT</pubDate><dc:creator>Kishore-132325</dc:creator></item><item><title>RE: Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>Your plan is mostly good. delete the part about copying logins (that part is bad .... real bad).If you want some more details on this failover process, I wrote an article on it for SQL Server Pro magazine: [url=http://www.sqlmag.com/article/high-availability/log%20shipping%20techniques-129747]3 Log shipping Techniques[/url] and have a [url=http://www.sqlsoldier.com/wp/logshippingtricksdemo]demo of it[/url] on my website.For the login stuff, bcp'ing or copying syslogins will not work in SQL 2005+. Just so happens, i have a script for this. In fact this script is even better because it syncs passwords and SIDs for SQL logins and also handles role assignments and explicitly granted server level permissions. You can find that script here: [url=http://www.sqlsoldier.com/wp/sqlserver/transferring-logins-to-a-database-mirror]Copy Logins script[/url]</description><pubDate>Sat, 21 Jul 2012 23:04:28 GMT</pubDate><dc:creator>Robert Davis</dc:creator></item><item><title>Dear  All this post is about logshipping DC- DR Drill [switch over and switch back (or)failover and failback ]</title><link>http://www.sqlservercentral.com/Forums/Topic1332796-1549-1.aspx</link><description>Iam a starter in sql server dba handling 3.5 to 4 yrs wrki too googled and taken feedback from so many but i did'nt got clear idea so i mergerd all into a action and really tried so many times,i worked it in my laptop after so many times then i prepared this succesfully now it is working and i hope it will be useful to many like me as in early stage.of their career.see below in detailed for logshiping DC [primary]-DR[secondary] Drill in sql server.-------------------------------------------------------------------------------------- TAKE CONFIRMATION FROM APPLICATION TEAM WHETHER ALL APPLICATION SERVICES ARE STOPPED PROPERLY-----1. take full backup in DC FOR the DATABASE 2. run lsbackupjob and disable in DC3. run lscopyjob and disable in DR4. run lsrestorjob and diable in DR5 take taillog backup6. restore the database rightclick on databases --&amp;gt;restore database--&amp;gt;--&amp;gt;--&amp;gt;7. IN RECOVERY STATE--&amp;gt;SELECT THE OPTION RESTORE WITH RECOVERY./////8.-- AND CONFIGURE AGAIN LOGSHIPPING MAKING DR AS PRIMARY AND DC AS SECONDARY9.--  NOW CAN SEE THE DATABASE IN DC[CURRENT DR] IN (Standby/Read-Only)mode 10.-- check the logshipping sync working properly or not 11.-- inform to application team 12. --------- SWITCH OVER COMPLETED----------------------------------------------------------------------------------------------------"same for switch back also follow the same steps above mentioned then your DR vl be acts as DC and DC will acts as DR " ""not yet prepared for mirroring  and replications" not having clear idea on that.</description><pubDate>Fri, 20 Jul 2012 03:24:55 GMT</pubDate><dc:creator>naga.rohitkumar</dc:creator></item></channel></rss>