The work to set it up really isnt that bad. You setup the main TSM database, do a offline backup of it and restore it to your secondary (standby) DB2 instance.
You then configure the following parameters on each database (you can get the values by typing "db2 get db cfg for TSMDB1"): HADR_LOCAL_HOST = hostname of the the server you're configuring HADR_REMOTE_HOST = hostname of "the other" DB2 server HADR_LOCAL_SVC = Port to use on the host you're configuring HADR_REMOTE_SVC = TCP/IP port to use on "the other" DB2 server HADR_REMOTE_INST = Name of the DB2 instance on "the other" DB2 server There are also a few optional configuration parameters on the database: HADR_SYNC_MODE = Default is NEAR_SYNC and you have the option to change it to SYNC or ASYNC. For further description of the different alternatives, see here: http://publib.boulder.ibm.com/infocenter/db2luw/v9/index.jsp?topic=/com.ibm.db2.udb.admin.doc/doc/c0021056.htm HADR_TIMEOUT_VALUE = Should be left by default or lowered. Tells DB2 when the primary node should be considered down and a forced HADR takeover should be done. When the above configuration is set, you start the "standby" node first by doing db2 start hadr on TSMDB1 as standby and then follow up by starting up the primary node (on the server where TSM is suppose to be active initially) db2 start hadr on TSMDB1 as primary There are several gotchas when using HADR. For example, if you end up in a situation where both nodes are down, and you start up the wrong node first as primary, you might end up in a "split-brain", aka two nodes who both think they have the primary copy. There are several ways of monitoring HADR, and it all depends on what kind of monitoring tools you're using today. I've seen HACMP handling HADR through scripting, Veritas handling it by using Veritas Cluster and other solutions. I wouldnt recommend using HADR if your shop has no DB2 competence at all. Not because it's hard to setup, but if something happens, you might find yourself in a situation where lacking DB2 competence might be a severe issue. Best Regards Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -----"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> skrev: ----- Till: ADSM-L@VM.MARIST.EDU Från: "Prather, Wanda" <wprat...@icfi.com> Sänt av: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Datum: 06/15/2011 16:51 Ärende: Re: TSM 6.x and HADR I'm interested in hearing from folks using it. >From the presentation, I am uneasy at all the cmd-line DB2 setup commands >required to use it, and wonder if it's suitable for a shop with no in-house >DB2 expertise. Once it's set up, how much time/expertise does it take to monitor/manage it? In fact, how do you monitor it at all? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Langdale Sent: Tuesday, June 14, 2011 3:19 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 6.x and HADR > > I might be hijacking the thread (excuse me) so I'll change the subject too. > Is there already an official announcement of TSM 6.x and replicating > the database by means of HADR? > > It is supported: https://www-304.ibm.com/support/docview.wss?uid=swg27021382&wv=1 But it aint free, you have to purchase a DB2EE license for it. As for who is using it, I'm sure I recall someone on the mail list was doing it a few weeks back. Steven
