Upgrading TSM – TSM V6 to TSM V7.1.1.100
Audience: This document assumes basic understanding of the AIX command line and basic TSM administration processes. For additional help with TSM command line syntax, consult the Version 6.3 and/or 7.1 Administrator’s Guide for Tivoli Storage Manager for AIX. The official version of this document is on page 648 of this document.
NOTE: This document assumes that all hardware/software requirements have already been evaluated.
Preparing the system
To prepare the system for the upgrade from V6.2 or V6.3 to V7.1, you must gather information about each DB2 instance. Then, back up the server database, save key configuration files, cancel sessions, and stop the server.
Log on to the computer where Tivoli Storage Manager is installed..
Ensure that you are logged on with the instance user ID.
Obtain a list of DB2 instances. Issue the following system command: /opt/tivoli/tsm/db2/instance/db2ilist The output might be similar to the following example: tsminst1 Note: Ensure that each instance corresponds to a server that is running on the system.
For each DB2 instance, note the default database path, actual database path, database name, database alias, and any DB2 variables that are configured for the instance. Keep the record for future reference. This information is required to restore the V6 database.
A. Obtain the default database path of the DB2 instance by issuing the following system command: . ~/sqllib/db2profile; LC_ALL=C db2 get dbm cfg | grep DFTDBPATH
The output might be similar to the following example: Default database path (DFTDBPATH) = /tsminst1/tsminst1
Tip: If you are upgrading the server from V6.3, the default database pathis /tsminst1/tsminst1. If you are upgrading the server from V6.2, the default database path is /home/tsminst1/tsminst1.
B. Obtain information about the DB2 instance databases by issuing the following system command: . ~/sqllib/db2profile; LC_ALL=C db2 list database directory
The output might be similar to the following example:
C. Obtain the DB2 instance variables by issuing the following system command: . ~/sqllib/db2profile; LC_ALL=C db2set –all
The output might be similar to the following example:
For example, issue the following system commands:
cp ~/sqllib/userprofile copy_location cp ~/sqllib/usercshrc copy_location
where copy_location is the location where the copied file is saved.
The file content might be similar to the following example:
setenv DSMI_CONFIG /tsminst1/tsminst1/tsmdbmgr.opt setenv DSMI_DIR /opt/tivoli/tsm/client/bin64 setenv DSMI_LOG /tsminst1/tsminst1 setenv LD_LIBRARY_PATH /usr/local/ibm/gsk8_64/lib64:$LD_LIBRARY_PATH
Things to do on TSM server:
Connect to the Tivoli Storage Manager server by using an administrative user ID
Prevent activity on the server by disabling new sessions. Issue the following Tivoli Storage Manager administrative commands: disable sessions client disable sessions server
Verify whether any sessions exist, and notify the users that the server will be stopped. To check for existing sessions, issue the following Tivoli Storage Manager administrative command: query session
Cancel sessions by issuing the following Tivoli Storage Manager administrative command: cancel session allThis command cancels all sessions except for your current session.
Cancel processes by issuing the following Tivoli Storage Manager administrative command for all processes: cancel process <process num>
Wait for all mounted media to dismount. Verify with the following Tivoli Storage Manager administrative command: query mount
Back up the Tivoli Storage Manager database. For example, you can create a snapshot backup by issuing the following Tivoli Storage Manager administrative command: backup db type=dbsnapshot devclass=tapeclassA snapshot backup is a full database backup that does not interrupt any scheduled database backups. For more information about this command and other Tivoli Storage Manager administrative commands, see the Administrator’s Reference.
Back up the device configuration information to another directory by issuing the following Tivoli Storage Manager administrative command: backup devconfig filenames=file_namewhere file_name specifies the name of the file in which to store device configuration information. Tip: If you decide to restore the V6 database, this file is required.
Back up the volume history file to another directory. Issue the following Tivoli Storage Manager administrative command: backup volhistory filenames=file_namewhere file_name specifies the name of the file in which to store the volume history information. Tip: If you decide to restore the V6 database, this file is required.
Save a copy of the server options file, which is typically named dsmserv.opt. The file is in the server instance directory.
Stop the server by issuing the following Tivoli Storage Manager administrative command: Halt
Verify that the server is shut down and no processes are running. Issue the following command: ps -ef | grep dsmserv ps -ef | grep db2
In the server instance directory of your installation, locate the NODELOCK file and move it to another directory, where you are saving configuration files. The NODELOCK file contains the previous licensing information for your installation. This licensing information is replaced when the upgrade is complete.
Installing the V7.1 server and verifying the upgrade
To complete the process of upgrading the server from V6.2 or V6.3 to V7.1, you must install the V7.1 server. Then, verify that the upgrade was successful by starting the server instance.
NOTE: Before you begin: You must be logged on to the system by using the root user ID.
As root, use sftp to transfer software package to a temporary directory on the AIX server that hosts the instance. mkdir /tmp/upgrade ls –l Output may be similar to below.root@host:/tmp/upgrade# ls -l TSM_7111_AIX_AGT_ML.bin -rwxr-xr-x 1 root system 1615693411 Jul 09 12:09 TSM_7111_AIX_AGT_ML.bin
Add executable rights to the file root@host:/tmp/upgrade# chmod +x TSM_7111_AIX_AGT_ML.bin
Execute the binary to extract the installation files NOTE: Make sure there’s enough space in the /tmp/ filesystem so that it doesn’t run out of space. root@host:/tmp/upgrade# ./TSM_7111_AIX_AGT_ML.bin
We have two ways to execute the code. 1. command line and 2. GUI by exporting DISPLAY to VNC Session. I am using GUI at the moment. Set the session’s DISPLAY variable to a VNC session. if you are not familiar to exporting DISPLAY to VNC sessions.. Can continue with command line.The output might look similar to below root@host:/tmp/upgrade# export DISPLAY=host/NIM server:45.0
Use VNC viewer to connect to the VNC session.
Execute the install.sh script that was extracted from the binary. The install window will appear in the VNC window, not the AIX session. root@host:/tmp/upgrade# ./install.sh
Select Install from menu.
Select the Server and License features.
Accept the defaults for the install directories.
Under Install Packages, select IBM Tivoli Storage Manager Extended Edition.
Accept the license agreements.
Under instance credentials, enter Instance name, password and verify. NOTE: If this step fails, contact AIX administrator. Its trying to determine the password it can ssh to the server hostname without a root password prompt.
Allow installation to proceed. It takes from 15-30 minutes.
Once the install finishes, start the TSM server to verify that the upgrade was successful. NOTE: Startup may take longer than usual as the installation will make database changes at this stage.Startup example for TSMINST1:nohup /opt/tivoli/tsm/server/bin/rc.dsmserv -u tsminst1 -i /tsminst1/tsminst1 -q >/dev/console 2>&1 &
Once the server starts responding, initiate another database full backup.
Verify all disk pools are online and enable client sessions.
Change TSM server option “BackupInitiationRoot” to no which is new feature added in v7.1 which prevents Application backups to run with non-root user. Syntax setopt BackupInitiationRoot no
Comentarios