ADSM-L

TR: ADSM Upgrade Options

1998-04-13 05:37:00
Subject: TR: ADSM Upgrade Options
From: Naveed Mustafa <Naveed_Mustafa AT MCKINSEY DOT COM>
Date: Mon, 13 Apr 1998 05:37:00 -0400
Hi Robert,

Thanks for the advice.  Well, you might already have got the new and latest
PTF which fixes the device support problem.

Based on the options which I presented to the ADSMers regarding ADSM
upgrade and migrate ADSM to a new server, in your opinion, which one should
I follow.  My original mail is followed by your response below.

Any help from someone who has already gone through this major upgrade will
serve us a great help.

Thanks and Regards,
Naveed.
---------------------- Forwarded by Naveed Mustafa on 04/12/98 01:13 AM
---------------------------
---------------------------
aloes AT ACORUS DOT FR on 04/09/98 02:36:22 AM
aloes AT ACORUS DOT FR on 04/09/98 02:36:22 AM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Naveed Mustafa)
Subject:  TR: ADSM Upgrade Options



Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable



Hi Mustafa,
We did install V3.1.1.1 on AIX V4.2 in order to use our STK9710 with AC=
SLS,
but
we got this: "SERVER NOT IN COMPLIANCE with license terms, Advanced Dev=
ice
 Support is required", but advdev.lic actually is installed (and always=

 has been).
We tried the REG LIC again, without success, and we CAN'T use the STK u=
nder
this
level. IBM is working on it and a fix will be ready in about 2 weeks.
So, wait before to get this nasty problem.
Robert Spieth
aloes AT acorus DOT fr
----------
De :    Naveed Mustafa
De :    Naveed Mustafa
Date=A0:        mercredi 8 avril 1998 21:32
A :     ADSM-L AT VM.MARIST DOT EDU
Objet : ADSM Upgrade Options
Hello there,
We are in the planning phase to upgrade our existing ADSM V2.1.0.13
environment to ADSM 3.1.1.1 and are looking for some expert advise.
Our current environment includes ADSM 2.1.0.13 running on an AIX 4.1.5
server (980B).  We are using STK 9710 library and are running Open
Microsystem's "Enhanced ADSM" version 2.1.0.13 which is installed on to=
p of
base ADSM.  The STK 9710 library is being controlled by ACSLS version 5=
.1.1
software (provided by STK) which is running on a Solaris machine.  The =
ADSM
storage pools (backup, archive, copy pools) are defined on a SSA disk
stand-alone tower, connected to the ADSM server.
Our upgrade goals include the following:
   Move ADSM to a new server (J50) with AIX 4.2
   Install new version of ADSM V3.1.1 (since the new version of ADSM no=
w
   support STK 9710 directly, we are no longer required to install Open=

   Microsystems' "enhanced ADSM").
   Install the latest version of ACSLS software version 5.2 also on the=
 new
   server (i.e., eliminate Solaris machine).
The ADSM Version 3 "Quick Start" guide does provide some information
regarding V2 to V3 upgrade, but does not provide sufficient information=

based on our ADSM infrastructure (meaning not only upgrading the softwa=
re
but moving to a new server as well).
Based on our research, there are basically two options available throug=
h
which we can achieve our goals:
Option 1
------------
   Install the latest version 5.2 of STK provided ACSLS software on the=
   Install the latest version 5.2 of STK provided ACSLS software on the=
 new
   server running AIX 4.2.
   On the old ADSM server, run EXPORT SERVER command.
   On the new ADSM server, install the latest version of ADSM V3.1.1.1.=

   Configure the STK 9710 library to ADSM.
   Run the IMPORT SERVER command on the new server.
Option 2
------------
   Install the latest version 5.2 of STK provided ACSLS software on the=
   Install the latest version 5.2 of STK provided ACSLS software on the=
 new
   server running AIX 4.2.
   Backup the ADSM database on the old ADSM server.
   Upgrade ADSM 2.1.5.15 on the new ADSM server along with enhanced ADS=
M
   version of 2.1.5.15.
   Restore the ADSM database on the new ADSM server. ( I am not quite s=
ure
   if we have to perform this step.  Reason being that we have the ADSM=

   database and storage pools defined to the SSA tower on a separate Vo=
lume
   group, namely ADSMVG.  Once moved to the new server, we will import =
the
   volume group on this SSA tower and mount all the filesystems belongi=
ng
   to it which, in my opinion, should keep all data intact.  Please giv=
e me
   your feedback....?????????)
   Upgrade ADSM 2.1.5.15 to 3.1.1.1 following the procedure documented =
in
   V3 "Quick Start" guide.
Concerns
-------------
For option 1, the export server command will be very intensive and sinc=
For option 1, the export server command will be very intensive and sinc=
e we
have our V2 environment up and running for almost two years, the sequen=
tial
tapes generated after this command will be enormous.
For Option 2, there will be several steps involved before we achieve ou=
r
goal.

Based on your expertise and thorough knowledge of the product, could yo=
u
please assist me in figuring out the best possible solution to perform =
this
upgrade (may be there are some other better options that we have not lo=
oked
into).
I shall be grateful to all of you.
Thanks in advance,
Naveed.



=
<Prev in Thread] Current Thread [Next in Thread>