Pre- Install Checklist

On both the nodes, ensure that the local Administrators group has the following
privileges:
Act as part of the operating system
Log on as a service
Replace a process level token
Click on Start-Programs-Administrative Tools-Local Security Policy,
Under the Local Policies Folder, click on Users Rights Assignment
Double Click on each of the rights mentioned above and confirm that
Administrator group has been assigned this right. Else assign the rights to the
Administrator group

Ensure that the following accounts have been set up in the AMD domain and that
they are part of the local Administrators group on each clustered node
<SID>cluadm
<SID>sqladm
<SID>adm
SAPService<SID>

eg sbtcluadm
eg sbtsqladm
eg sbtadm
eg SAPServiceSBT

Ensure that the following groups have been set up in the AMD domain
SAP_<SID>_GlobalAdmin eg SAP_SBT_GlobalAdmin
The <SID>adm , SAPService<SID> , <SAPSID>cluadm, <SAPSID>sqladm
should be a part of the SAP_<SID>_GlobalAdmin group

Add the SAP_<SID>_GlobalAdmin to the local Administrators group

On both nodes logon as SAP<SID> and map \\SAUSSAP1\SAPCD to the I drive

Ensure that the IP address for the following servers are there in the DNS:
Physical Node A
Physical Node B
Virtual Server for Cluster
Virtual SQL Server Name
Virtual SAP Server Name

eg ausr3sbtdc0a
eg ausr3sbtdc0b
eg ausr3sbtcl00
eg ausr3sbtdb00
eg ausr3sbtci00

The following IPs need not be in the DNS:

Heartbeat for Node A:
Heartbeat for Node B:

: IP 10.10.10.1
: IP 10.10.10.2

Ensure that each node can see only its own J drive

Ensure that both nodes have access to the K, M, L, N, O,Q drives .

To confirm this right click on the My Computer Icon on the desktop ( it might be
called <HOSTNAME> instead of My Computer). Click on Manage and click on
Disk Management . The following screen should appear

Drive Letter Assignments for Node A and Node B

Clustering the Operating System

1. Install Windows 2000 Advanced Server on both nodes
2. Install Cluster Service Component on node A
Click on Control Panel-Settings-Add/Remove Programs

Click on Add/Remove Windows Components

Click on Clustering Service and then click Next. Take care not to uncheck any other
checked boxes. On the next screen click on Remote Administration

Click OK and browse to the I386 directory on the Win2K Advanced Server CD and click
OK. In case you dont have the CD browse to the I386 directory on \\ausxxris00\Win2K.
You will be prompted for the location once more. Browse to the the I386 directory on the
Win2K Advanced Server CD and click OK again. In case you dont have the CD browse
to the I386 directory on \\ausxxris00\Win2K.

Click on Next
Click on I understand on the next screen and click Next again

Click on The first node in the cluster if you are configuring Node A else click on The
second node in the cluster if you are adding a new node to the existing cluster.
Click Next

Input the Virtual Server name for the cluster and then Click Next

Input the <SID>cluadm account and password and then click Next

Select the disk for J: ( SQL Executables) and click on Remove. This implies that all other
disks except the J drive are shared disks to be seen by both nodes. Each node will have its
own J drive

Click Next

On the next screen you need to input the drive letter that corresponds to the Quorum disk
( generally Q) and then Click Next

This section configures the communication mode for all active network connections
participating in the cluster, namely the Heartbeat and the Public/Private/Team network
card.
Select Internal cluster communications for the Heartbeat connection

Select All Communications for the Public/Private/Team network connection and click
Next

Click OK

Input the IP address corresponding to the Virtual Server for the cluster ( eg
AUSR3SBTCL00) and then Click Next

Click Finish to finish the Cluster Service Installation

Click Ok

Click on Start-Programs-Admin Tools-Cluster Admin

Right Click on the Cluster Name ( AUSR3SBTCL00) and click on Properties

Click on the Network Priority Tab and ensure the HeartBeat Network is above the Public
Network. If not use the Move up button to ensure that is the case

Click Ok
3. Install Cluster Service Component on node B
Repeat the process in Step 2 with the following exceptions:
In the Create or Join a Cluster Screen of the Cluster Service Configuration Wizard,
select This is the next or second node in the cluster option
In the Cluster Name screen of the Cluster Service Configuration Wizard, input the
name of the cluster node B has to join along with the cluster admin credentials
(<SID>cluadm username and password) as follows:

4. Check the binding order on Node A

From Start Menu choose Start-Settings-Network and Dial Up Connections and then
choose Advanced-Advanced Settings

On the Adapters and Bindings tab, ensure that the card of the Public/Private Network
must be displayed before that if the heart beat network. Use the Move Up/Down arrows
to change the order of entries.
5. Check the binding order on Node B
Repeat Step 6 for Node B
6. Install the latest DLLs on node A
On the \\SAUSSAP1\SAPCD share, click on the R3DLLINS executable in the
NTPATCH directory. When the installation has finished, you are prompted to reboot the
system to activate the changes. If your DLLs were already up-to-date before you started
the R3DLLINS.EXE no new DLLs are installed and you are not prompted to reboot.
7. Install the latest DLLs on node B
Repeat Step 8 on Node B
8. Add Quorum Disk to Cluster Group

Open the cluster Administrator by clicking on Start-Programs-Administrative ToolsCluster Administrator

Click on Cluster Group under the Groups Folder and ensure that that all entries under this
folder are owned by Node A

9.

Create Database Cluster Group

In the Cluster Administrator right click on New-Group

Enter MSSQL as name of Cluster Group Click Next

Click on both the nodes in the Available Nodes section and click on Add

Click Finish.

Click on OK.

10. Move the resources for Disk L to the MSSQL Cluster Group
Right click on the MSSQL Cluster Group that was just created and click on Bring Online.

Click on Resources. Under resources right click on Disk L and then click on Move
Group and then select MSSQL as the group to which Disk L needs to be moved:

Click Yes

Click Yes to finish moving Disk L to Group MSSQL

11. Move the resources for Disk M to the MSSQL Cluster Group
Repeat step 12 for Disk M
12. Move the resources for Disk N to the MSSQL Cluster Group
Repeat step 12 for Disk N
13. Rename Disk Group to SAP-R/3 <SID>
Right click on the Disk Group containing drive K and select Rename

Type in SAP-R/3 <SID> and press Enter.

16 Delete the other three Disk Groups that no longer contain resources.