The reason to have separate binaries for each instance is that the process in
AIX is tied to the binary file and holds it open.
Orville L. Lantto
________________________________
From: ADSM: Dist Stor Manager on behalf of Loon, E.J. van - SPLXM
Sent: Tue 1/22/2008 02:55
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Upgrading TSM on an AIX server running multiple TSM
instances
Hi Orville!
Thank you very much for you help!
I read the technote (1052631) Richard pointed out. That doesn't mention
copying the dsmserv executable.
Any reason why you choose to do so?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Orville Lantto
Sent: maandag 21 januari 2008 19:11
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Upgrading TSM on an AIX server running multiple TSM
instances
You do not really need a full install of the TSM server code in both
locations. Just a separate directory, separate config files, a separate
copy of the dsmserv binary and a the appropriate environment to run it
in.
export DSMSERV_DIR=/usr/tivoli/tsm/server/bin
export DSMSERV_CONFIG=/usr/tivoli/tsm/server/instance2/dsmserv.opt
Our upgrade procedure is to do the primary install and copy the dsmserv
binary to each instance directory. Done.
Orville L. Lantto
________________________________
From: ADSM: Dist Stor Manager on behalf of Loon, E.J. van - SPLXM
Sent: Mon 1/21/2008 06:11
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Upgrading TSM on an AIX server running multiple TSM
instances
Hi *SM-ers!
I'm running two TSM server instances on an AIX host.
Upgrading them from 5.3 to 5.4.0.0 works fine. I installed the 5.4.0.0
code through smitty, changed the /usr/tivoli/tsm/server path to the
second instance and install the 5.4.0.0 code here, using the force (-F)
flag. Both instances are on 5.4.0.0 at that point.
Now I'm trying the same trick for the upgrade to 5.4.2.0. Upgrading the
first instance works fine, but since this is an update, the -F flage is
not allowed by smitty during the upgrade of the second instance:
Force Apply Failures
--------------------
The following is a list of fileset updates. Updates cannot be specified
from the command line when the force flag (-F) is used in combination
with the apply flag (-a).
Maybe an AIX expert (and I now there are plenty of them on this list)
can help me with this one?
Thank you VERY much in advance!!!!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com <http://www.klm.com/> <http://www.klm.com/> . This e-mail
and any
attachment may contain confidential and privileged material intended for
the addressee only. If you are not the addressee, you are notified that
no part of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately by
return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or
its employees shall not be liable for the incorrect or incomplete
transmission of this e-mail or any attachments, nor responsible for any
delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
Airlines) is registered in Amstelveen, The Netherlands, with registered
number 33014286
**********************************************************************
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com <http://www.klm.com/> . This e-mail and any attachment may
contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
|
