Browse Prior Art Database

TMR Server in a NT Microsoft Cluster High Availability Environment

IP.com Disclosure Number: IPCOM000016228D
Original Publication Date: 2002-Sep-25
Included in the Prior Art Database: 2003-Jun-21
Document File: 2 page(s) / 63K

Publishing Venue

IBM

Abstract

A solution is disclosed for configuring a TMR Server in High Availability MSCS for NT environment. Obtaining that kind of configuration following the steps described below:

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 2

TMR Server in a NT Microsoft Cluster High Availability Environment

A solution is disclosed for configuring a TMR Server in High Availability MSCS for NT environment. Obtaining that kind of configuration following the steps described below:

Scenario:

Machines SMADAVG01 and SMADAVG02 are the ones who provide us the high availability solution. The cluster virtual node is SMADAVG00 been unit J:\ the one to be shared for both machines SMADAVG01 and SMADAVG02.

The High Availability solution, using MSCS for NT, acts active-pasive mode. For a certain moment of time, one node of the cluster (ie: SMADAVG01) is the owner of the cluster (active node), who is also the owner of the shared unit (J:\ in our example). The other node of the cluster acts as pasive node (ie: SMADAVG02) is not able to use the shared unit at that time.

The steps hended in order to obtain this TMR Server over a MSCS High Availavility configuration are:

1. Make SMADAVG02 the active node of the cluster
2. Install Tivoli on SMADAVG02. Binaries and data base on SMADAV00 (unit J:\)
3. Add (Tivoli one) a administrator login not depending on machine name.
4. odadmin odlist add_hostname_alias 1 dir_ip_SMADAVG00 SMADAVG00
5. wlocalhost with the virtual node name (SMADAVG00)
6. Odadmin odlist Set_force_bind TRUE 1
7. odadmin odlist change_ip 1 ip_SMADAVG00 TRUE
8. Make SMADAVG01 the active node of the cluster
9. Install Tivoli on SMADAVG01. Binaries and data base on SMADAV00 (unit J:\)
10. Delete SMADAVG01.db

1

[This p...