dbTalk Databases Forums  

Change MSDTC Location on Clustered W2k3

microsoft.public.sqlserver.clustering microsoft.public.sqlserver.clustering


Discuss Change MSDTC Location on Clustered W2k3 in the microsoft.public.sqlserver.clustering forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
David Gregg
 
Posts: n/a

Default Change MSDTC Location on Clustered W2k3 - 12-29-2003 , 04:03 PM








I have mistakenly installed MSDTC on my Clustered W2k3 server in the
Cluster Group. I now know this is not recommended. I have not found a
procedure for safely moving this resource under Windows 2003. KB 301600
does not show how to change it once it is installed. KB 243204 applies
to Windows 2000. If anyone knows how to do this or can shed some light
I would appreciate it. We have already installed SQL 2k3 sp3 and it is
working but if I am running a risk with MSDTC in its current location I
would like to change it. Thanks!

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Reply With Quote
  #2  
Old   
Uttam Parui[MS]
 
Posts: n/a

Default RE: Change MSDTC Location on Clustered W2k3 - 12-30-2003 , 05:51 PM






Hi David,

You are correct, it is not recommended to use Quorum disk for anything
other than MSCS (Microsoft Cluster Service). If are currently using quorum
disk for MSDTC and everything is working fine, then you can leave it the
way it is. Although not recommended, I have seen many environments use this
primarily because they do not have a spare disk for MSDTC. If you have a
seperate disk that you can use for MSDTC you can create a seperate group
for MSDTC and use the spare disk. Also, in some cases depending on what is
using MSDTC, we may have to use a seperate disk for MSDTC. For example, a
clustered BizTalk Server configuration requires that MS DTC be placed on a
separate drive and in a separate cluster group.

Here are the steps that you will follow to move the MSDTC resource in
Windows 2003 :

Start Cluster Administrator. Delete all resources created for Windows NT
4.0; these would typically be MSDTC, MSDTC Network Name, and MSDTC IP
address.

1) Delete the MSDTC resource after taking it offline.
2) Create a new group (call it MSDTC for simplicity ----- note: you can
call it anything)
3) Move the shared drive that you want to use for MSDTC in this group.
4) Create the following resources in the MSDTC group:
MSDTC TCP/IP Address, dependent on the drive where you want MS DTC to be
created.
MSDTC Network Name, dependent on the MSDTC TCP/IP address.
5)Create the MSDTC resource as follows (Here is what changes for Windows
2003)
Right-click the MSDTC Group, and then click New\Resource.
Type a name, such as MSDTC Resource.
In Resource Type, click to select Distributed Transaction Coordinator,
verify that the MSDTC Group check box is selected, and then click Next.
In Possible Owners, click Next unless you do not want MSDTC to run on a
particular node.
In Dependencies, press and hold the CTRL key on the keyboard, select both
the shared drive and MSDTC Network Name and then click the Add button.
Click Finish, and then click OK to confirm that the resource has been
created.
Right-click the MSDTC Resource, and then click Bring Online.
6) Test it.

Note : A new MSDTC.log gets created in the MSDTC shared disk when you
create the MSDTC resource.Once everything is working, you can delete
MSDTC.log from the quorum drive.

HTH,

Uttam Parui
SQL Server Developer Support Engineer, MCDBA, MCSE, MCT
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.