Yes, I understand about the differences.

No, I was not expecting to just move the DB and viola, it works.

We are defining the boxes, brand new, and then doing "export to server" of 
each node, or in some cases, deleting the old and just moving the 
definitions.



Markus Engelhard <Markus.Engelhard AT BUNDESBANK DOT DE> 
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
03/21/2007 04:54 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Moving Library Owner/Manager






Hi Zoltan,

as I understand, you will be changing OS for all your TSM-instances from
AIX to Linux. There is no supported way to just simply make TSM data
written by AIX readable by another OS apart from painstakingly
exporting/importing the node data and database references.
My best guess would thus be to set up a seperate TSM-Library Manager as
suggested by William Boyer (works like a charm, very flexible and smart to
run, fast restore if it fails and can allways be rebuilt from scratch in
very short time) on a Linux, keeping the library clients on AIX in the
first step. Just take care there is no data interaction before you have
audited the libraries from the library client side. After that define the
Linux library clients and then move your nodes. I personally prefer just
exporting node definitions (including policies) plus archives, backing up
the data again on the new servers and letting the old data expire on the
AIX to delete after your retention period. Don´t forget the data will not
expire altogether and has to be deleted by batch or manually.
If you are at it, consider setting up one TSM-Instance dedicated for your
archives (I seperate nodes for backups and archives even if on one client
system) making future migrations easy and fast.

;-) Is SSA really that slow? At the moment I would really prefer them to
cr...p SATA...

Regards,
Markus


--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet.

Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der
Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch
raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser
Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder
grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch
virenbefallene Software oder E-Mails aus.

Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, 
dennoch
schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer
irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden.
______________________________________________________________________

This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorised copying, disclosure or distribution of  the material in this
e-mail or of parts hereof is strictly forbidden.

We have taken precautions to minimize the risk of transmitting software
viruses but nevertheless advise you to carry out your own virus checks on
any attachment of this message. We accept no liability for loss or damage
caused by software viruses except in case of gross negligence or willful
behaviour.

Any e-mail messages from the Bank are sent in good faith, but shall not be
binding or construed as constituting any kind of obligation on the part of
the Bank.