Hello Steve,
I have mentioned in my message my TSM Server Version is 5.5.4.0. So I do not
have DB2 at all now in production. I am testing TSM 6.1.2.1 now, but I have not
reached disaster recovery testing yet.
I hate DB2 administration after managing application called MERVA (similar to
SWIFT) in the past.
I only hope we will not need to administrate DB2 straight way in TSM 6.1. At
least I am running TSM 6.1 in test mode for quite long time (6.1.0 --> 6.1.1
--> 6.1.2.0 -->6.1.2.1) and I never use direct DB2 administration, but I saw
some advices in documentation like "Connect to DB2 and do next....".
Any way, I prefer to shutdown TSM Server before making replication copy. Of
course, it is possible in my environment, but it can be impossible in other
cases. You advice is useful for non-stop environment.
Kindest regards,
Grigori G. Solonovitch
Senior Technical Architect
Information Technology Bank of Kuwait and Middle East http://www.bkme.com
Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: G.Solonovitch AT bkme
DOT com
Please consider the environment before printing this Email
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Steven Harris
Sent: Wednesday, December 16, 2009 11:40 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Q about TSM 6.1 DB and hardware replication
Grigori,
It should not be necessary to stop your TSM database. DB2 can suspend
IO with the command
set write suspend for db
you can then sync your mirrors and issue
set write resume for db
This will need a DB2 connection rather than a TSM command line, and the
suspend and resume should be issued from the same connection.
How easy is it to access the DB2 instance directly under 6.1?
Regards
Steve
Steven Harris
TSM Admin
Finally prospectively employed again after six months!
Sydney Australia
Grigori Solonovitch wrote:
> Hello Wanda,
>
> We have TSM Server 5.5.4.0 under AIX 5.3.
>
> We are mirroring TSM database to disaster site by IBM Metro Mirror (PPRC) for
> DS8100.
>
> I have experienced some problems with online mirroring. It means we faced
> problems with disaster site activation in case of sending any changes at Head
> Office (DB, logs and configuration files) to Disaster Site online (nature of
> PPRC). Finally I came to next procedure:
>
> 1) complete all backups for current day;
>
> 2) complete all copies for current day;
>
> 3) run TSM database backup to tape volume;
>
> 4) run backups for volume history and device configuration;
>
> 5) stop TSM Server;
>
> 6) enable mirroring to Disaster Site;
>
> 7) wait till both sites are in sync (usually only a few minutes, because we
> have two 1Gb/s fiber optics links for mirroring);
>
> 8) suspend mirroring;
>
> 9) start TSM Server at Head Office and send disaster copy volumes to disaster
> site.
>
> In this case, TSM database, logs and configuration files are in sync and they
> are in sync with disaster copy of data.
>
> I think, for TSM 6.1 you need to use the same procedure or something similar,
> because DB2 will definitely escalate all problems with online mirroring.
>
> Kindest regards,
>
>
>
> Grigori G. Solonovitch
>
>
>
> Senior Technical Architect
>
>
>
> Information Technology Bank of Kuwait and Middle East http://www.bkme.com
>
>
>
> Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: G.Solonovitch AT
> bkme DOT com
>
>
>
> Please consider the environment before printing this Email
>
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Wanda Prather
> Sent: Tuesday, December 15, 2009 8:40 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Q about TSM 6.1 DB and hardware replication
>
>
>
> In prior TSM server versions, replicating the TSM DB and log using hardware
>
> replication works fine as long as the DB and log are in a consistency group.
>
>
>
> Any issues with hardware replication of the TSM 6.1 DB and log? With
>
> appropriate changes to dsmserv.opt, will a DR TSM server be able to open the
>
> replicated DB and use it? (Just a little nervous about what all those DB2
>
> services will think..)
>
>
>
> Any insight appreciated!
>
>
>
> W
>
>
>
> Please consider the environment before printing this Email.
>
> ________________________________
> "This email message and any attachments transmitted with it may contain
> confidential and proprietary information, intended only for the named
> recipient(s). If you have received this message in error, or if you are not
> the named recipient(s), please delete this email after notifying the sender
> immediately. BKME cannot guarantee the integrity of this communication and
> accepts no liability for any damage caused by this email or its attachments
> due to viruses, any other defects, interception or unauthorized modification.
> The information, views, opinions and comments of this message are those of
> the individual and not necessarily endorsed by BKME."
> ------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 9.0.716 / Virus Database: 270.14.109/2567 - Release Date: 12/16/09
> 06:58:00
>
>
|