Hi TSM'ers,
Please find the migration instructions attachment.
(See attached file: tsmmigration.txt)
Thanks to one who prepared it .
Regards
sreekumar.
Farren Minns
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
UK> cc:
Sent by: "ADSM: Subject: Re: Migrate Install 3.7 to
4.2 any Notes?
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
04/10/2002 16:31
Please respond to
"ADSM: Dist Stor
Manager"
Hi George
I am soon to be doing the very same upgrade. I'm running TSM Server 3.7.3.8
on a Solaris box.
Did you go directly from 3.7.x.x to 4.1.x.x and what exact patch level did
you upgrade to?
Also, I know this has been questioned before, but I'm a little confused
about the problems people were having with the licenses. Unfortunately for
me, I was not present when our TSM server was set up and I did not see the
licenses being set up.
Sorry for being such a novice.
Thanks ever so much
Farren Minns - Trainee Solaris and TSM system admin
John Wiley & Sons Ltd
George Lesho <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 09/04/2002 22:41:52
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Migrate Install 3.7 to 4.2 any Notes?
I saved off all config files, the accounting log and a bunch of other
things. I backed up the db and was ready for the worst. I needed nothing...
it was very straightforward. The licesnse files need to be installed
properly. I would highly recommend latest ATAPE driver and that is about
it. I didn't need any of the stuff I had saved off... no config changes at
all when upgrade was complete... only had to redo licensing.
George Lesho
System/Storage Admin
AFC Enterprises
Craig Simpson
<[EMAIL PROTECTED] To:
[EMAIL PROTECTED]
COM> cc: (bcc: George
Lesho/Partners/AFC)
Sent by: "ADSM: Subject: Re: Migrate
Install 3.7 to 4.2 any Notes?
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
04/09/02 04:53 PM
Please respond to
"ADSM: Dist Stor
Manager"
On AIX 4.3.3. Any notes you have would be great. We are running an IBM 3494
Librairy with 3590 drivers.
Craig
--
Craig Simpson
"Jolliff, Dale"
<[EMAIL PROTECTED]> To:
[EMAIL PROTECTED]
Sent by: "ADSM: cc:
Dist Stor Subject: Re: Migrate
Install 3.7 to 4.2 any Notes?
Manager"
<[EMAIL PROTECTED]
.EDU>
04/09/02 03:27 PM
Please respond to
"ADSM: Dist Stor
Manager"
What OS?
I just did some 3.7.4 to 4.2.x for AIX.
It's pretty straightforward for the server code itself, but watch out for
changes in the startup scripts if you use an externally managed library.
-----Original Message-----
From: Craig Simpson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 3:15 PM
To: [EMAIL PROTECTED]
Subject: Migrate Install 3.7 to 4.2 any Notes?
Doing a Migrate Install from 3.7 to 4.2.11. Do anyone have any notes on
doing this? Any hang ups that they ran into?
Anyone have issues with the following:
Schedules
Tuning
New features that might be on by default
How much configuration do we lose
Lisenceing
Thanks,
Craig
--
Craig Simpson
MIGRATION INSTRUCTIONS
1) Use the BACKUP DEVCONFIG command to backup the ADSM "Device
Configuration" file to an alternate location.
NOTE: The 'QUERY OPTION' command will show the DEVCONFIG option, if
defined, which will identify the current location of this file.
Performed in ADSM.
backup devconfig filenames=/archive/adsmtmp/devconfig.bak
SPECIAL NOTE: We originally backed up the files to the /tmp directory,
but moved them upon realization that a reboot was required for the
install. Sure enough, the files were gone from /tmp.
Performed in ADSM.
q library * f=d > /archive/adsmtmp/adsm.txt
q drive lib_name f=d >> /archive/adsmtmp/adsm.txt
2) Copy the "Server Options" file, dsmserv.opt, to an alternate
location.
Performed from the unix command line.
cp /usr/lpp/adsmserv/bin/dsmserv.opt /archive/adsmtmp/dsmserv.opt.bak
3) If you are also updating ADSM code for the client residing on the
same machine as the server, you should also copy the "Client Options"
file(s) to an alternate location. The default location for these files
on AIX is: /usr/lpp/adsm/bin
Performed from the unix command line.
cp /usr/lpp/adsm/bin/dsm.sys /archive/adsmtmp/dsmserv.sys.bak
cp /usr/lpp/adsm/bin/dsm.opt /archive/adsmtmp/dsmserv.opt.bak
4)Copy the operating system definitions for any devices utilized by
ADSM. Use the AIX 'lsdev' command to save the device definitions for any
tape or optical device used with, and supported by, the ADSM device
driver. (the 'op', 'mt', 'lb' names)
Performed from the unix command line.
lsdev -Cc adsmtape > /archive/adsmtmp/device.config
lsdev -Cc tape >> /archive/adsmtmp/device.config
lsdev -Cc library >> /archive/adsmtmp/device.config
lsdev -Cc rwoptical >> /archive/adsmtmp/device.config
You will also need to know the parent adapter of each device:
Performed from the unix command line.
lsdev -Cc adapter >> /archive/adsmtmp/device.config
NOTE: This is not necessary for the 3570,3575,3490,3590,3494, and any
device classified as GENERICTAPE to ADSM.
5) Please refer to the TSM Server README for your specific operating
system to determine any special requirements related to the
installation or support for devices. This may include required
device-driver upgrades, or required operating system maintenance.
6) Use the 'Q DBVOL' and 'Q LOGVOL' commands to identify the size and
location of all existing ADSM database and recovery log volumes.
Save this to a file.
Performed in ADSM.
q dbv * f=d >> /archive/adsmtmp/adsm.txt
q logv * f=d >> /archive/adsmtmp/adsm.txt
Note: This information will be used in the event that it is desirable
to return to your current version of ADSM.
7) Copy the dsmserv.dsk file to an alternate location.
Performed from the unix command line.
cp /usr/lpp/adsmserv/bin/dsmserv.opt /archive/adsmtmp/dsmserv.opt.bat
8) Prevent new processes from establishing themselves:
A) Perform in ADSM:
1) using the "QUERY PROCESS" and "CANCEL PROCESS" commands, end
all currently running processes.
2) using the "QUERY SESSION" and "CANCEL SESSION" commands, end
all currently running sessions.
B) If your system is under heavy use, you may require:
1) In the dsmserv.opt file, add "DISABLESCHEDS YES" This will
disable schedules once ADSM is restarted
2) In the dsmserv.opt file, add "EXPINTERVAL 0" This will disable PAGE
expiration once ADSM is restarted
3) For each storage pool, from the DSMADMC command line,
issue "UPDATE STG <name> RECLAIM=100 HI=100"
This will disable migration and reclaimation.
4) From the DSMADMC command line, Issue "DISABLE SESSSIONS" This
will prevent clients from connecting during upgrade
5) From the DSMADMC command line, issue "HALT" This will stop
ADSM Server.
6) Restart ADSM For UNIX, run rc.adsmserv from the server/bin
directory.
9) Complete a full ADSM database backup as follows:
Performed in ADSM.
backup db devclass=<devclassname> type=full
10) Use the BACKUP VOLHIST command to backup the ADSM "Volume History"
file to an alternate location.
Performed in ADSM.
backup volhist filenames=/archive/adsmtmp/volhist.bak
11) Use "QUERY MOUNT" and "DISMOUNT VOLUME" to empty the drives if
required.
Performed in ADSM.
query mount
dismount volume <volumename>
12) Stop the ADSM server by entering:
Performed in ADSM.
halt
13) If upgrading your client, uninstall it after copying dsm.sys and
dsm.opt files to a safe location first
NOTE: Make sure to keep your old install media in case you need to
return to the old version.
Performed from the unix command line.
installp -u adsm.client
SPECIAL NOTE: We did not perform this step. We updated the client
code in step 15.
14) If using AIX and going from ADSM to TSM, remove your ADSM device
definitions first with:
contained in your output from step 4 (/archive/adsmtmp/device.config)
Performed from the unix command line.
rmdev -dl rmt0
rmdev -dl lb1
rmdev -dl od1
rmdev -dl od2
+---------------------------------------------------------------------
SPECIAL NOTE: We did not remove the rmt0 definition. After the install
the 8MM drive defined in TSM was unavailable and the device was set
to /dev/mt0. We deleted the DEVCLASS and DRIVE definitions in TSM. We
then removed the rmt0 definition and ran cfgmgr. We then redefined
the DEVCLASS and DRIVE in TSM. The drive was now available, but the
device type reads GENERICTAPE instead of 8MM.
15) Install the new code from base-install media per the instructions
contained in the README file for you operating system type.
Here is the SMIT procedure:
1. Log in as the root user.
2. Load the CD-ROM into the selected drive.
3. From your desktop window, access SMIT and make selections
according to the level of your AIX operating system.
+----------------------------------------------------------
|smit install_update &
OF
+----------------------------------------------------------
Then select:
+----------------------------------------------------------
|Install and Update Software
|
+----------------------------------------------------------
4. On the next window, select the device that you are using for
the installation. You can enter the drive name in the window or click
on List to access the device list. If you click on List, select the
CD-ROM drive that you are using for the installation (for example,
/dev/cd0).
5. Click on OK.
6. Check the default settings for the options on this window.
BDC
7. To continue, click OK.
+-----------------------------------------------------------------
|ARE YOU SURE?...
+-----------------------------------------------------------------
8. To continue, click OK.
This installation may take several minutes.
9. After the installation is complete, click Done, remove the CD,
and exit from SMIT.
10. Reboot the server.
16) Install any required Device driver updates or operating system
updates as required from Step 5.
SPECIAL NOTE: This step was NOT REQUIRED.
17) If step 14 was followed, and your devices were deleted from AIX,
Re-define your AIX devices: `smitty devices` -> TSM Devices go into
Tape for mt's and "add Device" for each go into Optical for od's and
"add Device" for each go into library for lb's and "add Device" for each
Here is an example of how to set up a 3995 optical library:
"smitty / devices / Tivoli Storage Manager devices / define drive
smitty devices
Tivoli Storage Manager devices
Optical Device
Add an Optical Drive
TSM-SCSI-OP
adapter 00-02-01
Connection Address 1,0
then create the library device with:
smitty devices
Tivoli Storage Manager Devices
Library Device
Add a Library Devices
TSM-SCSI-LB
adapter 00-02-01
Connection Address 6,0
This defines one drive, op0, and the library device, lb0.
18) Verify that the dsmserv.opt (and optionally the dsm.sys and
dsm.opt files) are present in their default locations as determined in
steps 3 and 4. NOTE: The verification of the dsm.opt and dsm.sys files
is only required when updating the ADSM client code.
Verify that dsmserv.opt is in the /usr/tivoli/tsm/server/bin directory.
Verify that dsm.opt is in the /usr/tivoli/tsm/client/ba/bin directory.
cp /archive/adsmtmp/dsm.opt.bak /usr/tivoli/tsm/client/ba/bin/dsm.opt
Verify that dsm.sys is in the /usr/tivoli/tsm/client/ba/bin directory.
cp /archive/adsmtmp/dsm.opt.sys /usr/tivoli/tsm/client/ba/bin/dsm.sys
Verify that dsm.opt is in the /usr/tivoli/tsm/client/api/bin directory.
cp /archive/adsmtmp/dsm.opt.bak /usr/tivoli/tsm/client/api/bin/dsm.opt
Verify that dsm.sys is in the /usr/tivoli/tsm/client/api/bin directory.
cp /archive/adsmtmp/dsm.sys.bak /usr/tivoli/tsm/client/api/bin/dsm.sys
19) Make any modifications to the dsmserv.opt, dsm.sys, dsm.opt files
as required based on changes to the options contained within said files
as outlined in the Release Notes and README files for the current
version.
Performed from the unix command line.
cp /archive/adsmtmp/volhist.bak /usr/tivoli/tsm/server/volhist.vol
cp /archive/adsmtmp/devconfig.bak /usr/tivoli/tsm/server/devconfig.vol
We then updated the /usr/tivoli/tsm/server/bin/dsmserv.opt file.
Performed from the unix command line.
vi dsmserv.opt
volumehistory /usr/tivoli/tsm/server/volhist.vol
devconfig /usr/tivoli/tsm/server/devconfig.vol
20) Verify that the "Device Configuration" and "Volume History" files
are present in the their default locations as determined in prior steps
of this document.
We copied the files from the /archive/adsmtmp directory to the
/usr/tivoli/tsm/server directory in step 19 above.
21) Ensure that the dsmserv.dsk file is present in the default
location as determined above.
NOTE: The dsmserv.dsk is always read from the directory in which the
server is started. The file was in the /usr/tivoli/tsm/server/bin
directory.
22) Start the TSM server
NOTE: If you are given a notice that the database needs to be updated,
you can restart the adsm server with the "upgradedb" parameter.
This will not be required on subsequent restarts of the server.
Note: On the AIX platform, it is not necessary to explicitly specify the
upgradedb parameter as the initial dsmserv process will
automatically perform this function. However, you may issue it without
negative effect to the server.
Performed from the unix command line.
nohup dsmserv quiet >/dev/null 2>&1 &
SPECIAL NOTE: This is where we ran into problems.
When we tried to logon with dsmadmc userid password, we would get a
tcpip -50 error.
We then did the following:
We loaded the sample scripts into the database, issuing the following
command
Performed in TSM.
./dsmserv runfile /usr/tivoli/tsm/server/webimages/scripts.smp
Tivoli Storage Manager is shipped with sample command scripts that can
be loaded into the database and run from an administrative client,
administrative Web interface, or server console. They can also be
included in administrative command schedules. The sample scripts,
in scripts.smp, are primarily SELECT queries, but also include scripts
that define volumes for and extend the database and recovery log and
that back up storage pools.
Note: The sample scripts may have been loaded when a previous version
of ADSM or TSM was installed. Loading the sample scripts again at this
point will overlay any existing scripts of the same name and any
modifications made to those scripts will be lost.
We then started the TSM server.
Performed in TSM.
./dsmserv
We noticed on startup that the script was still pointing to the
/usr/lpp/adsmserv/bin directory.
We then verified that the environment variables reflected the new
directory structure.
Performed from the unix command line.
export DSMSERV_CONFIG /usr/tivoli/tsm/server/bin/dsmserv.opt
export DSMSERV_DIR /usr/tivoli/tsm/server/bin
To save this environment, save these entries in the .cshrc or .kshrc
file of your $HOME directory. We added the lines to root's .profile
file.
23) Once you have verified that the server is operating normally,
reset any values changed in section 8.B, including:
1) remove "ENABLE SCHEDS" from the dsmserv.opt
2) remove "EXPINTERVAL 0" from the dsmserv.opt
3) issue "UPDATE STG <name> RECLAIM=<orig> HI=<orig>" for each
pool changed
4) issue "ENABLE SESS" at a dsmadmc command prompt
5) Stop ADSM by issuing "HALT" from a dsmadmc command prompt
6) restart TSM by running rc.adsmserv from the server/bin
directory on UNIX
24) Your licenses from the previous version are no longer valid and
must be reregistered.
Note: The tivoli.tsm.license package is required to register licenses.
This package isinstalled when you install the TSM server package.
Performed in TSM.
register license file=/usr/tivoli/tsm/server/bin/10mgsyslan.lic
register license file=/usr/tivoli/tsm/server/bin/1library.lic
25) Verify that the Migration from ADSM to TSM was successful.
backup db devclass=<devclassname> type=full
We edited ADSM/6000 section of the ars.cfg file.
cd /usr/lpp/ars/config
vi ars.cfg
update the file with the environment variables
DSMSERV_CONFIG /usr/tivoli/tsm/server/bin/dsmserv.opt
DSMSERV_DIR /usr/tivoli/tsm/server/bin
DSM_CONFIG /usr/tivoli/tsm/client/ba/bin/dsm.opt
DSM_DIR /usr/tivoli/tsm/client/ba/bin
DSMG_CONFIG /usr/tivoli/tsm/client/ba/bin/dsm.opt
DSMG_DIR /usr/tivoli/tsm/client/ba/bin
DSMI_CONFIG /usr/tivoli/tsm/client/ba/bin/dsm.opt
DSMI_DIR /usr/tivoli/tsm/client/ba/bin
The OnDemand Test was then successful.
3995. Offsite copy was successful.
**********************************************************************
