Hi Kevin,
I did follow the below steps on the same server and yet to test on DR server,,,
I have kept TSM DB and Log(active/archive ) in different VG
Configured flash copy ( DS8K)
Note: Tested it when TSM database was running
DB2 has feature called write suspend and it will ensure TSM DB consistency state
Step 1:
I have suspended database and all writes were suspended for all table spaces
db2 command
db2 connect to TSMDB1
db2 set write suspend for TSMDB1
Step 2 : Wait for 1 min until archive logs become consistent ( check db2diag
log )
Step 3:
Tested below steps when backup stg was running
Take flash copy backup
And resume database for write operation
db2 set write resume for TSMDB1
Step 4:
Took file level backup to check flash copy state
Halt TSM server
Step 5:
Unmount TSM db and log vg( production copy )
Step 6:
Mount flash copy LUN and import TSM db and log VG
Step 7 :
Note: Flash copy will have database in write suspend mode and we need to bring
the database into normal mode before starting TSM server
db2start
Db2 restart db TSMDB1 write resume
Db2stop
Step7:
Start TSM server and ur database will come up without any issue
Tested above steps in production and my plan is to test it on DR site with help
of PPRC backup
In your case , you can take mksysb of prod and restore ur instance dir if not
in storage disk
By Sarav
+65-82284384
> On 10 Apr, 2014, at 4:27 am, James Choate <jchoate AT CHOOSES1 DOT COM> wrote:
>
> I have done this recently on Windows, AIX and Linux.
> We treated it like a DR exercise and basically installed TSM (same version)
> on new hardware.
>
> Made sure I migrated storage pools to 0.
> Ran a prepare.
>
> Put the volhist, devconf, dsmserv.opt in the proper place.
> Took care of zoning with the tape library
> Allocate new storage for DB/activelog/archlog (we kept paths to these the
> same as old server, but used new storage just in case)
>
> Restore DB
>
> ***the above order may vary, but I think you get the point. The important
> step is next.
>
> Go to lunch.
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Kevin Kettner
> Sent: Wednesday, April 09, 2014 2:02 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Moving TSM instance to new hardware
>
> I'm running 6.3.4 server on AIX. The server is getting to the end of it's
> life so we're planning to replace the hardware. I have just about everything
> related to TSM installed on SAN disk, besides the stuff that gets installed
> in /usr. The last time I did a hardware swap was with TSM 5.5. The basic
> procedure was this:
>
> 1. Install the TSM software(exact same version) on the new hardware.
> 2. Shutdown TSM on the old hardware.
> 3. Export all volumes.
> 4. Rezone all SAN storage.
> 5. Import volumes on new hardware.
> 6. Start TSM.
>
> I did that several times and never had any problems.
>
> So I'm wondering if anyone has done something similar with TSM 6.x?
>
> Thanks!
>
> -Kevin
|
