DB2 has a HADR mechanism (High Availability Disaster Recovery) to replicate a database to another server.
It is basically just log shipping from the active db to the passive db. The most strict mechanism is that a commit to an SQL statement is only given to the application when the DB2 memory cache that contains the results of the statement is flushed to disk on the standby server. The standby server cannot be accessed, it is in a rollforward status. >From what I've been reading so far, the HADR mechanism will not be supported initially. It requires some changes to the primary database and IBM tells strictly that the DB2 database can (or should) be accessed in a read-only way. Regards, Kurt -----Oorspronkelijk bericht----- Van: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] Namens Allen S. Rout Verzonden: donderdag 2 april 2009 17:51 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: Re: [ADSM-L] TSM 6.1 : Database replication Feature >> On Thu, 2 Apr 2009 09:21:38 +0700, Wira Chinwong <w...@scsi.co.th> said: > The TSM6.1's database is DB2. Is there any way to replicate the TSM > database to another site (DR site) by using DB2 feature? You're on your own for the experiment, and that path is unexplored, so expect problems. But the short answer is "Probably, yes.". Expect to understand DB2 replication a LOT before you get it to work. - Allen S. Rout *** Disclaimer *** Vlaamse Radio- en Televisieomroep Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/disclaimer
