This document serves as a guide for upgrading from ADSM to TSM. The procedure described in this document will allow a complete recovery to an earlier service level if needed at a later date. This document is not specific to any particular ADSM supported operating system or specific ADSM version. Where an operating system command example is appropriate, AIX commands are used.
NOTE: Please use this document in combination with the README file
for your type of operating system.
Related documentation
The product documentation library is also available:
http://www.rs6000.ibm.com/resource/aix_resource/Pubs/index.html
The Tivoli Storage Manager (TSM) Server includes recovery log and database structural enhancements to support new functionality. For this reason, once this upgrade is applied, returning to an earlier service level requires the reinitialization of the database and recovery log volumes. This reinitialization process (dsmserv format), will remove all previous information stored in the database and recovery log. This upgrade procedure, while more detailed than previous upgrade instructions, is designed to ensure that should a reversion to an earlier service level be necessary for any reason, all information that could be required to assist in that process is stored for future use. IMPORTANT: If a reversion is later needed, ensure that you keep your old installation media.
TSM Server README files are available online at:
ftp://service.software.ibm.com/storage/tivoli-storage-management
Select one of the server directories, such as:
Inside each server directory will be server and client code in their respective directory paths.
NOTE: Server full-product code, required for an ADSM to TSM Version/Release upgrade (for example, 3.7, 4.1), can be purchased through Tivoli Marketing at 1-800-2-TIVOLI or your local branch/marketing office.
BACKUP DEVCONFIG <FILENAMES>=/tmp/devconfig.bak
The QUERY OPTION command will show the DEVCONFIG option, if defined, which will identify the current location of this file. If you do not have one defined, please define it now by adding the following option to the dsmserv.opt file:
DEVCONFIG /<my_directory>/deconfig.out
NOTE: You can acquire the same information through the QUERY LIBRARY, QUERY DRIVE, and other types of commands. Examples follow:
Q LIBRARY * F=D Q DRIVE <lib_name> F=D Q DEVCLASS F=D Q SERVER F=D
cp /usr/lpp/adsmserv/bin/dsmserv.opt /tmp/dsmserv.opt.bak
cp /usr/lpp/adsm/bin/dsm.sys /tmp/dsm.sys.bak cp /usr/lpp/adsm/bin/dsm.opt /tmp/dsm.opt.bak
NOTE: Windows, OS/2, and Netware clients do not have a dsm.sys file.
lsdev -Cc adsmtape > /tmp/device.config lsdev -Cc tape >> /tmp/device.config lsdev -Cc library >> /tmp/device.config lsdev -Cc rwoptical >> /tmp/device.configYou will also need to know the parent adapter of each device, enter:
lsdev -Cc adapter >> /tmp/device.config
NOTE: This is not needed for Atape/IBMTAPE devices, such as the 3570, 3575, 358X 3490, 3590, 3494, or any device classified as GENERICTAPE to ADSM.
Please refer to the TSM Server README file 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.
Q SYSTEM
cp /usr/lpp/adsmserv/bin/dsmserv.opt /tmp/dsmserv.opt.bak
DISABLESCHEDS YESThis will disable schedules once ADSM is restarted.
EXPINTERVAL 0This will disable expiration once ADSM is restarted.
QUERY STG
This will collect the information that you will later need if system recovery is required.
UPDATE STG <name> RECLAIM=100 HI=100
This will disable migration and reclamation.
DISABLE SESSSIONS
This will prevent clients from connecting during upgrade.
HALT
This will stop ADSM Server.
BACKUP DB DEVCLASS=<devclassname> TYPE=FULL SCRATCH=YES
SCRATCH=NO can also be used if appropriate for your environment.
BACKUP VOLHIST FILENAMES=/tmp/volhist.bak
NOTE: The QUERY OPTION command will show the VOLUMEHISTORY option, if defined, which will identify the current location of this file. If you do not have one defined, please define it now by adding the following option to the dsmserv.opt file:
VOLUMEHISTORY /<my_directory>/volhis.out
HALT
rmdev -dl mtX rmdev -dl lbX rmdev -dl odX
Where X represents the drive number. Do this for each drive contained in your output from step 4 (/tmp/device.config).
smitty devices
NOTE: The verification of the dsm.opt and dsm.sys files is only required when updating the ADSM client code.
NOTE: On the AIX and NT platforms, it is not necessary to explicitly specify the upgradedb parameter as the initial dsmserv process will automatically perform this function. However, you can issue it without negative effect to the server.
UPDATE STG <name> RECLAIM=<orig> HI=<orig>
ENABLE SESS
HALT
rc.adsmserv
ftp://service.software.ibm.com/storage/ tivoli-storage-management
lslpp -l | grep -i adsm install -u adsm (or adsm.client, adsm.server, etc.)
pkginfo pkgrm
NOTE: Ensure that you do not uninstall a package that you have not replaced, with the exception of Space Management, which cannot run backlevel.
[ Doc Ref: 98052918210162 Publish Date: Feb. 06, 2001 4FAX Ref: 8801 ]