Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Convert Mirroring to Log Shipping


Convert Mirroring to Log Shipping

Author
Message
JeremyE
JeremyE
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3720 Visits: 4028
Comments posted to this topic are about the item Convert Mirroring to Log Shipping
Alistair Board
Alistair Board
Forum Newbie
Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)Forum Newbie (4 reputation)

Group: General Forum Members
Points: 4 Visits: 72
We have 2 servers that used to implement mirroring.

In both access even though the mirroring was removed conventionally there appears to be a number of processes related to the mirroring that seem to persist.

Notably the BROKER_TASK continues to be seen as a significant wait type when on similar systems which never had mirroring it is not seen at all.

I have tried to help myself.
On a test system I deleted broker related items and did remove the wait type and did not dame the server.
However I was not comfortable or confident and was perplexed thinking that removing the mirroring should have put the system back to the sate it was in before mirroring was implemented.

I am left feeling that the only way back to the pre-mirroring sate is to reinstall - tell me I am wrong, please.
JeremyE
JeremyE
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3720 Visits: 4028
You may have to delete the mirroring endpoint as well if there are no databases mirrored. There are various other internal tasks to SQL Server that use Service Broker also. For details on Service Broker waits see the blog below.

http://blogs.msdn.com/b/sql_service_broker/archive/2008/12/01/service-broker-wait-types.aspx
Dan Guzman - Not the MVP
Dan Guzman - Not the MVP
Right there with Babe
Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)

Group: General Forum Members
Points: 724 Visits: 736
Items 9 and 14 are missing from the screen shots. I assume you are referring back to the main 'Transaction Log Shipping' page in the properties view. It might be helpful to show the full screen shot. Thanks for the article.

Can you please explain why you disabled the restore transaction log job, and when it would be necessary to leave it on?
JeremyE
JeremyE
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3720 Visits: 4028
The reason for disabling the restore transaction log job on the secondary was given in the 3rd paragraph of the article.

"Once we convert the mirrored database to a log shipped database we can disable the restore job on the secondary and have the secondary available as a hot standby in case of an upgrade failure. This allows us to quickly backout of the upgrade by simply bringing the secondary online and pointing the application servers at it. Once the system is back online we can reestablish mirroring back to the original principal. If the upgrade is successful, we enable the restore job on the secondary, allow the secondary to catch up, and then reestablish mirroring."

If you are not planning to use the secondary as a backout plan for a failed implementation then you can just enable the restore transaction log job and convert mirroring to log shipping.
Dan Guzman - Not the MVP
Dan Guzman - Not the MVP
Right there with Babe
Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)Right there with Babe (724 reputation)

Group: General Forum Members
Points: 724 Visits: 736
So, this example is only intended for fail implementations? You plan on reverting back to mirroring when the implementation is complete?

Or, did you mean to include a statement to come back later and turn on that job after the code implementation was complete?

I guess what I'm not clear on is what the restore trans log job is for, in the big picture sense.

After I have converted my system to TLS, is this restore TL job the only step I need to disable/enable for all future code implementation fail over tasks?
JeremyE
JeremyE
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3720 Visits: 4028
Dan Guzman - Not the MVP (8/19/2010)
So, this example is only intended for fail implementations? You plan on reverting back to mirroring when the implementation is complete?

Or, did you mean to include a statement to come back later and turn on that job after the code implementation was complete?


Once the code upgrade completes successfully the LS restore job can be turned on to catch up the secondary. Then we can reestablish mirroring for high availability.


The reason for switching to log shipping from mirroring is to have that "hot" standby copy ready on the mirror/secondary server which the application servers can point to. This brings the entire system back online faster in the event of a code upgrade failure. The traditional way of backing out of a code upgrade would be to restore the principal/primary database from backup. That may take several hours depending on the size of the VLDB creating a longer backout time.
SQLRNNR
SQLRNNR
SSC-Insane
SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)SSC-Insane (21K reputation)

Group: General Forum Members
Points: 21029 Visits: 18258
Thanks for the article. Good stuff.



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server, MVP


SQL RNNR

Posting Performance Based Questions - Gail Shaw

simon.murin
simon.murin
SSC Journeyman
SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)SSC Journeyman (79 reputation)

Group: General Forum Members
Points: 79 Visits: 575
Well, wouldn't it be easier to suspend DB mirrorring session in this case?

In case of upgrade failure: 1)turn off db mirrorring; 2) bring mirror db online.

3 t-sql statements in total:

1) ALTER DB SET PARTNER SUSPEND

2) ALTER DB SET PARTNER OFF

3) RESTORE DATABASE DB WITH RECOVERY
JeremyE
JeremyE
Hall of Fame
Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)Hall of Fame (3.7K reputation)

Group: General Forum Members
Points: 3720 Visits: 4028
That should work as long as the transaction log on the principal is large enough to hold all the transactions during the upgrade.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search