switchover cluster

[ruediger.papke]

Hello,

we want to build up a DB2- switchover cluster on 2 solaris machines,
where a db2-instance is switched from one server to another.

we have 2 machines (a,b) with OS solaris 5.9.
both machines habe local filesystems and filesystems in a SAN.
db2 v8.1 is installed locally (/opt/IBM/...) on both machines.
/etc/services, /etc/group, /etc/passwd are identical on a and b.

on machine a (logical host, switchable IP) there was a DB2-Instance
with a database created.
the homedir of the instance-owner and all directories/filesystems with
configurations/tablespaces of db2(without /opt) are on a switchable
filesystem of the SAN.
in case of failure of machine a all db2-filesystems will be switched
to machine b. the mountpoints are identical.
which environment variables, db2-registry-variables or files have to be
changes or have to be switched to get a normal, stable function of the
switched instance on server b.

TIA
ruediger papke

[Larry]

YOu are best off using a commercially available product like Sun Cluster
or Veritas, for which there are documented procedures and expertise
readily available.

Larry Edelstein

ru************@t-online.de wrote:

Hello,

we want to build up a DB2- switchover cluster on 2 solaris machines,
where a db2-instance is switched from one server to another.

we have 2 machines (a,b) with OS solaris 5.9.
both machines habe local filesystems and filesystems in a SAN.
db2 v8.1 is installed locally (/opt/IBM/...) on both machines.
/etc/services, /etc/group, /etc/passwd are identical on a and b.

on machine a (logical host, switchable IP) there was a DB2-Instance
with a database created.
the homedir of the instance-owner and all directories/filesystems with
configurations/tablespaces of db2(without /opt) are on a switchable
filesystem of the SAN.
in case of failure of machine a all db2-filesystems will be switched
to machine b. the mountpoints are identical.
which environment variables, db2-registry-variables or files have to be
changes or have to be switched to get a normal, stable function of the
switched instance on server b.

TIA
ruediger papke

[paul.lapointe]

You should to take in to consideration; your SAN is also a potential
point of failure. SAN based solutions are not necessarily the simplest
or least expensive approach to this problem.

If you are looking for inexpensive, HA/DR will replicate DB2 for you,
and it's free. If you have any requirements for an active-active
solution, or any scalability or DR requirements, you might want to take
a look at GRIDSCALE from xkoto (whom I work for).

IBM has several options for HA with DB2, as well, depending on your
requirements. It might be worth the call to your IBM rep for advice.

ru************@t-online.de wrote:

Hello,

we want to build up a DB2- switchover cluster on 2 solaris machines,
where a db2-instance is switched from one server to another.

we have 2 machines (a,b) with OS solaris 5.9.
both machines habe local filesystems and filesystems in a SAN.
db2 v8.1 is installed locally (/opt/IBM/...) on both machines.
/etc/services, /etc/group, /etc/passwd are identical on a and b.

on machine a (logical host, switchable IP) there was a DB2-Instance
with a database created.
the homedir of the instance-owner and all directories/filesystems with
configurations/tablespaces of db2(without /opt) are on a switchable
filesystem of the SAN.
in case of failure of machine a all db2-filesystems will be switched
to machine b. the mountpoints are identical.
which environment variables, db2-registry-variables or files have to be
changes or have to be switched to get a normal, stable function of the
switched instance on server b.

TIA
ruediger papke