how change biztalk service accounts check failover cluster management

4
Updating the service accounts used by the BizTalk SQL Servers and Checking the Failover Cluster Management Applies To SQL Servers having Clustered environment Introduction How to change the password for updating the service accounts used by BizTalk Servers and checking the Failover Cluster Management after updating service accounts. BizTalk Servers: 1. OMABTDBPROD1 2. OMABTDBPROD2 3. OMABTDBPROD3 There are 2 SQL Server instances on each server a. MGMT1 b. MSGBOX1 Prerequisites Account name & associated passwords of the servers that have to change. Two or more clustered server having interconnected node. Procedure 1. Shut down the BizTalk services from the application side. 2. Remote into OMABTDBPROD1. Bring the following cluster services offline: SQLMGMT1. SQLMSGBOX1 2.1. Start Administrator Tools Failover Cluster Management (cluster name is OMABTDB1CLUS) 2.2. Right click each respective cluster service (listed above) and select “Take this service or application offline”.

Upload: wasimss

Post on 21-Apr-2015

37 views

Category:

Documents


4 download

TRANSCRIPT

Page 1: How Change BizTalk Service Accounts Check Failover Cluster Management

Updating the service accounts used by the BizTalk SQL Servers and Checking the Failover Cluster Management

Applies To

SQL Servers having Clustered environment

Introduction

How to change the password for updating the service accounts used by BizTalk Servers and checking the Failover Cluster Management after updating service accounts.

BizTalk Servers: 1. OMABTDBPROD1

2. OMABTDBPROD2

3. OMABTDBPROD3

There are 2 SQL Server instances on each server

a. MGMT1

b. MSGBOX1

Prerequisites

Account name & associated passwords of the servers that have to change.

Two or more clustered server having interconnected node.

Procedure

1. Shut down the BizTalk services from the application side.

2. Remote into OMABTDBPROD1. Bring the following cluster services offline:

SQLMGMT1.

SQLMSGBOX1

2.1. Start Administrator Tools Failover Cluster Management (cluster name is OMABTDB1CLUS)

2.2. Right click each respective cluster service (listed above) and select “Take this service or application offline”.

Page 2: How Change BizTalk Service Accounts Check Failover Cluster Management

3. Open the SQL Configuration Manager.

3.1. Verify that the service is stopped

Change the SQL Server Service (SSDE) to reflect the accounts in the file

4. Right click the service and select Properties

:

Page 3: How Change BizTalk Service Accounts Check Failover Cluster Management

4.1. Update the Account name to reflect the corresponding account in the file.  Supply the password.

4.2. Click OK.

5. Repeat for the SQL Server Agent Services (SSAG).

6. Adjust the following service accounts to run under “Local Service” and then disabled for startup.

6.1       Full Text Indexing

6.2       Analysis Services

6.3       Reporting Services

With the cluster services offline, you can do the other two servers, OMABTDBPROD2/OMABTDBPROD3

7. Once all three servers have been updated, you can bring the cluster services back online:

8. Test the failover between the nodes of the cluster.

9. Select the service.  Right click, select “Move this server or application to another node”

Move SQLMGMT1 to OMABTDBPROD1

Move SQLMSGBOX1 TO OMABTDPROD3

10. After testing please make sure:

SQLMGMT1 is on OMABTDBPROD3

SQLMSGBOX1 is on OMABTDBPROD1.

Page 4: How Change BizTalk Service Accounts Check Failover Cluster Management

Comments

It is advised that after updating the account and password, test the Failover Cluster Management services by using above mentioned method by moving this server or application to another node. This will enhance the performance of the production servers.