I agree, this should work fine.  I think the thing that previous posters were
commenting on (saying that the db would become corrupted), that wasn't made
clear in the original question, is that you want to make sure you shut down the
primary TSM server prior to breaking the mirror.   As long as you do that, I
don't see why it shouldhn't work....

Paul

Quoting "Rushforth, Tim" <TRushforth AT WINNIPEG DOT CA>:

> We've used a similar procedure in the past for quicker upgrades and a
> quick backout.
>
> We would mirror the TSM Logs and DB on separate physical disk drives.
> These disk drives were internal to our server and we have another server
> that is the same so the upgrade consisted of (simplified):
>
> Shutting down TSM on old server, swap drives, bring up new server, run
> upgrade, re-mirror DB and log.
>
> If any problems, the original server is still functional.
>
> -----Original Message-----
> From: fred johanson [mailto:fred AT UCHICAGO DOT EDU]
> Sent: Thursday, February 10, 2005 4:24 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Question from a non-TSM person
>
> I was asked if it was possible to move TSM from machine to machine by
> mirroring the DB and log, breaking the mirror, moving the mirrored
> portions
> to a new machine, adding the old mirror volumes to dsmserv.dsk, and
> bringing up the new machine as if nothing happened?
>
>
>
> Fred Johanson
> ITSM Administrator
> University of Chicago
> 773-702-8464
>


----------
paul AT fielding DOT ca
http://www.fielding.ca

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/