I was obviously not having a good day yesterday.
I got the poster's name wrong and the gist of the question.
Apologies Stuart and all.

Leigh

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allen S. Rout
Sent: 09 August 2006 18:55
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Migrating windows clients to AIX

>> On Wed, 9 Aug 2006 10:19:08 +0100, "Pitt, Stuart"
<STUART.PITT AT RWENPOWER DOT COM> said:

> I have the opportunity of moving all my windows clients to an lpar
>  on a P5. [...]

> I'm guessing that I can't just export the TSM DB from the windows
> server and put it on the AIX server.

Terms of art are important here: You _can_ "export" the TSM server to
the new arch, using e.g. export server TOSERVER or such.

You cannot "restore" a backed-up database to a different architecture.

If you can get the database-export-import process to complete inside
your outage window, then all you have left to do is make sure that you
can define the libraries and devclasses identically (or 'with
identical function') in both environments.  This will not be trivial.
But if I'm remembering past conversations about this correctly, the
data format on stgpool tapes does not change between TSM server
architectures.


> Is there anything else I can try.


At the risk of tooting my own horn:

http://open-systems.ufl.edu/services/NSAM/whitepapers/50ways.html

recorded all the ways I could come up with to move data from one
server to another.  I'll repeat the encouragement to nitpick about my
examples, or add more; last update of the list was some time ago.

The list was compiled in the environment of same-architecture
transition; the addition of 'appropriate for moving between platforms'
decoration to the options would probably be a good idea.


Depending on your time pressure, you might be able to use same-arch
methods to calve a new TSM server which would exist only to be a
smaller chunk, perhaps of a size manageable for export to the P5
instance.  For example, split the windows server, and zap every node
except the target node from the new one, and then export-import that
server, in a timeframe short enough to be acceptable.



- Allen S. Rout
- Beep.