By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
454,236 Members | 1,355 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 454,236 IT Pros & Developers. It's quick & easy.

howto keep two db2 in sync ?

P: n/a
Hello,
I have two db2 box here, running a vrrp daemon to provide IP failover...
The two nodes are perfectly identical (same os, users, and db2 setup
(instances, db, tables...)).

[DB2_node1] <---- Common Virtual IP Addr ----> [DB2_node2]
MASTER (working) BACKUP (standby)
I know nearly nothing about db2 internals...

The only way I know to keep them in sync is to stop db2 on both nodes,
then run rsync on instances, fenced and admin home directories... then
restart db2.

Is it enough to keep nodes in sync ?
Is there a risk of data corruption ?
I know I should use some smart realtime replication, using db2 internals
and so on, but I can't afford working on this direction :(

Bye,
Mat.
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Ian
M.L. wrote:
Hello,
I have two db2 box here, running a vrrp daemon to provide IP failover...
The two nodes are perfectly identical (same os, users, and db2 setup
(instances, db, tables...)).

[DB2_node1] <---- Common Virtual IP Addr ----> [DB2_node2]
MASTER (working) BACKUP (standby)
I know nearly nothing about db2 internals...

The only way I know to keep them in sync is to stop db2 on both nodes,
then run rsync on instances, fenced and admin home directories... then
restart db2.

Is it enough to keep nodes in sync ?
Is there a risk of data corruption ?
This is not supported by IBM, although it will work until someone
changes the physical database configuration and moves something
out of the instance owner home directory.
I know I should use some smart realtime replication, using db2 internals
and so on, but I can't afford working on this direction :(


There are lots of options,

DB2 Replication
Standby database using Log Shipping
HADR (new in Stinger)
Hardware HA (using Sun Cluster / Veritas Cluster / HACMP / etc.)
Probably the easiest is #2 (log shipping). There are some articles on
this at the DB2 Developer Domain.


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
Nov 12 '05 #2

P: n/a
There are multiple options for this - log shipping, replication or HADR
which in new in FP7.

HADR would be the best way to keep 2 DB2 databases in sync. When used with
the new client re-route it will minimise any possible downtime.

Cheers,

"M.L." <m.l@no_sP_am_oceanfree.net> wrote in message
news:ch**********@news-reader2.wanadoo.fr...
Hello,
I have two db2 box here, running a vrrp daemon to provide IP failover...
The two nodes are perfectly identical (same os, users, and db2 setup
(instances, db, tables...)).

[DB2_node1] <---- Common Virtual IP Addr ----> [DB2_node2]
MASTER (working) BACKUP (standby)
I know nearly nothing about db2 internals...

The only way I know to keep them in sync is to stop db2 on both nodes,
then run rsync on instances, fenced and admin home directories... then
restart db2.

Is it enough to keep nodes in sync ?
Is there a risk of data corruption ?
I know I should use some smart realtime replication, using db2 internals
and so on, but I can't afford working on this direction :(

Bye,
Mat.

Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.