| likes 2004-06-19, 10:27 am |
| Hi,
I am trying to implement the DB2 clustering(High Availability) using
WebSphere Edge Server
( reference : http://www-106.ibm.com/developerwor...ry/i-cluster/#8
).
I am having following Software Configuration on two intel machines :
1) RedHat linux 9 (2.4.20-8)
2) IBM DB2 Universal Database V8.1 (DB2 Enterprise Server Edition )
3) WebSphere Edge Server Installed on both machines.
I setup the architecture as mention in the architecture diagram of above
url.
I am facing the Synchronisation problem of these two servers.
Also, I don't know how to create the shared storage (as mention in the
architecture diagram of attached url).
Can anyone help me on this.
Thanks,
Likhesh
========================================
================
Output on Primary Server :
-------------------------------------------------------
[root@server1 bin]# ndcontrol high status
High Availability Status:
-------------------------
Role ................. Primary
Recovery strategy .... Auto
State ................ Active
Sub-state ............ Not Synchronized
Primary host ......... 192.168.0.22
Port ................. 54321
Preferred target ..... n/a
Heartbeat Status:
-----------------
Count ................ 1
Source/destination ... 192.168.0.22/192.168.0.19
Reachability Status:
--------------------
Count ................ 1
Address .............. 192.168.0.103 reachable
========================================
===============
Output on BackUp Server :
-------------------------------------------------------
[root@server2 bin]# ndcontrol high status
High Availability Status:
-------------------------
Role ................. Backup
Recovery strategy .... Auto
State ................ Active
Sub-state ............ Not Synchronized
Primary host ......... 192.168.0.22
Port ................. 54321
Preferred target ..... n/a
Heartbeat Status:
-----------------
Count ................ 1
Source/destination ... 192.168.0.19/192.168.0.22
Reachability Status:
--------------------
Count ................ 1
Address .............. 192.168.0.103 reachable |