>for this newyear i'm upgrading my old server ADSM 3.0
>to TSM 4.3 or it may be TSM 5.2
>
>is it possible to upgrade my ADSM 3.0 to TSM 4.2
>without affecting DB
>Any idea about the DB backup..can i able to restore my
>old DB in upgrade one...if i do fresh installation of
>TSM.
>
>I'm thinking of upgrading my OS also from AIX 4.3.2 to
>4.3.3 or may be 5.3
>
>can any one suggest me better idea in this...it would
>be of gr8 help.
>
>Any precaution measure before upgrading ....
>
>Thanx in advance..
Yes, that will work...which is a credit to the programming
of the product. I've moved an ADSM 3.1 server from an AIX 4.1
system on an old R3U processors box to AIX 5.2, TSM 5.2 on a p650,
via 'dsmserv restore db'. The restore happily works, and the
'dsmserv UPGRADEDB', needed in that kind of migration, works
fine as well. (If you upgrade to TSM over an in-place db, you
should not have to perform an UPGRADEDB, as it should to that
automatically.) The UPGRADEDB took only a few minutes.
Be aware that UpgradeDB, be it implicit or explicit, is not in
a position to "modernize" things. For instance, TSM5 introduced
pathing, so you will probably find that your tape drives will not
be usable until you do DELete DRive, then DEFine DRive and DEFine
PATH, to have the modern composite definitions in place.
Some advice: Study and become very clear about what filesets are
32-bit and which are 64-bit, and DO NOT INSTALL BOTH! In some
sites, the TSM software may be installed by someone, such as an
AIX guy, who is unfamiliar with TSM. He may think to himself,
"I'll be safe and install both." Wrong. Components such as
dsmlicense and dsmserv are singular, and in installing both 32-bit
and 64-bit filesets you will end up with only the one most
recently installed. That can make for a chaotic mix, and some
"interesting" ANR messages.
Hasn't it been great to get so much mileage out of that ADSM
license? :-)
Richard Sims http://people.bu.edu/rbs
