Tivoli Storage Manager Upgrade from

Version 5.5 to 6.2

Author: Vamsi
Contact: vamolli!in.im.com

Content, upgradation methods, why should we go for 6.3 and later, estimating techniques for server down
time
Crawford
Pre Requests
=============
# nsure that the server that you plan to upgrade is at version !.3.6 or later.
# nsure that the system where the "! server is located meets the minimum requirements.
#se the information in $ardware and software requirements for the "! server system that is
%eing upgraded to determine whether you need to update your system %efore you continue.
"ard#are $e%uirements
P&'R(), P&'R!), P&'R6), P&'R*)systems computer +6(,%it-
./0 "!.3 +6( %it only-
Memor&:
12 34 of memory or more is optimal and more efficient for the new 5ivoli 6torage 7anager with
integrated 841. 9or this test upgrade, there was 12 34 of memory for each 5ivoli 6torage 7anager instance.
'is( Space :
: ! 74 for the ;var directory
: 32 74 for ;opt directory
: 1 34 for the ;opt;tivoli;tsm directory
: 362 74 for the ;tmp directory
: 322 74 for the ;usr directory
: 1 34 in the home directory

Soft#are $e%uirements:
: ./0 !.3 5echnology <evel +5<- == and 6ervice Pac> +6P- =
: 7inimum C?? runtime level with the @lC.rte A.2.2.B and @lC.ai@!2.rte A.2.2.B filesets. 5hese filesets are
included in the Cune 122B cumulative fi@ pac>age for /47D C?? Runtime nvironment Components for ./0.
: 9or upgrades to 5ivoli 6torage 7anager "ersion 6.1, the %os.iocp.rte fileset.
# nsure that the system where you plan to install the "6.1 server meets requirements.
Chec> the operating system level and the platform against the list of supported operating
systems and platforms.
)eneral Chec(s E

: 7a>e sure that the .synchronous /;& is ena%led

Fou can ena%le this using na%le this manually using Gsmit aioG
Crawford
: 7a>e sure /&CP is ena%led on ./0 platforms
/f not ena%led then you can ena%le using Gsmitty iocpG
: 7a>e sure all the installation mount points are created as rw file systems ..
Modif&ing the server efore the upgrade
*********************************************
# 9rom a 5ivoliD 6torage 7anager administrative command line, issue the commandE
convert ussfilespace
5his command fi@es a pro%lem that might e@ist in older 5ivoli 6torage 7anager data%ases. /f the pro%lem
does not e@ist in your data%ase, the command completes quic>ly. /f the pro%lem e@ists in your data%ase, the
command might ta>e some time to run.
/mportantE 8o not s>ip this step. /f your data%ase has the pro%lem and you do not run this command now, the
867#P3R8 PRP.R84 utility fails when you run it. Fou must then restart the "! server and run the
C&H"R5 #669/<6P.C command %efore continuing with the upgrade process.
'isaling the sessions
***************************
=. Prevent all clients, storage agents, and other servers from starting new sessions with the server. #se
the commandsE
disa%le sessions client
disa%le sessions server
1. Prevent administrative activity from any user /8 other than the administrator /8 that is %eing used to
perform the upgrade preparation. <oc> out other administrator /8s if necessaryE
loc> admin administratorIname
3. Chec> whether any sessions e@ist, and notify the users that the server is going to %e stopped. 5o chec>
for e@isting sessions, use the commandE
query session
Crawford
(. Cancel sessions that are still running. #se the commandE
cancel session
+ac(ing up storage pools and the server dataase
******************************************************
/mmediately %efore upgrading the server, %ac> up primary storage pools to copy storage pools, and perform
a full data%ase %ac>up.
=. 4ac> up primary storage pools to copy storage pools using the 4.CJ#P 653P&&< command. /f you
have %een performing regular %ac>ups of
the storage pools, this step %ac>s up only the data that was added to the primary storage pools since they
were last %ac>ed up.+Hot .pplica%le for the current upgrade-
1. 4ac> up the data%ase using the following command. #se either a full or snapshot %ac>up type.
%ac>up d% type=type devclass=deviceIclassIname
5he device class that you specify must e@ist and have volumes that are availa%le to it. 9or e@ample, to
perform a snapshot %ac>up of your data%ase to the 5.PC<.66 device class using scratch volumes, enterE
%ac>up d% type=d%snapshot devclass=tapeclass
5o use specific volumes instead of scratch volumes, specify the volume names in the command.
Consider ma>ing two copies of the %ac>up to protect the %ac>up from media failures.
+ac(ing up configuration information
***************************************
4efore installing the new version, %ac> up critical files and information for the server. 6tore the files in a safe
place, %ecause they are needed after the installation of the new software version is completed. Fou also
need these files if you must revert to the previous version after the upgrade.
=. 4ac> up device configuration informationE
%ac>up devconfig filenames=fileIname
Crawford
1. 4ac> up volume history informationE
%ac>up volhistory filenames=fileIname
nsure that the volume history includes information a%out the data%ase %ac>up that you completed in the
preceding steps. 9or e@ample, issue the commandE
query volhistory type=d%%ac>up
3. 7a>e copies of these files, which are located in the default directory for the serverE
: server options file, typically named dsmserv.opt
: dsmserv.ds>
(. &ptionalE 7a>e a copy of the accounting log file, dsmaccnt.log.
!. 4ac> up any scripts that have %een used to perform daily house>eeping for the server. @amine the
scripts for changes that are needed after the
upgrade.
6. 6tore the device configuration file, the volume history file, the server options file, and the other files in a
safe place.
6elect a location that is not on the system that is %eing upgraded.
Creating a summar& of dataase contents
*******************************************
Create a summary of the contents of the original data%ase. .fter the upgrade, you can use the same
commands to compare the results and to confirm that the data%ase contents are intact.
7acro will %e used for this..
Macro ,ile
***********
select nodeIname, count+:- as GHum%er of 9ilespacesG from filespaces group %y nodeIname order %y 1
select platformIname, count+:- as GHum%er of HodesG from nodes group %y platformIname
select count+:- as GHum%er of .dministratorsG from admins
select nodeIname,sum+numIfiles- as GHum%er of 4ac>up 9ilesG from occupancy where type=K4>upK group %y
nodeIname
select nodeIname,sum+numIfiles- as GHum%er of .rchive 9ilesG from occupancy where type=K.rchK group %y
nodeIname
select count+:- as GHum%er of 6chedule .ssociationsG from associations
select count+:- as GHum%er of 4ac>upsetsG from %ac>upsets
select count+:- as GHum%er of Client &ption 6etsG from cloptsets
select count+:- as GHum%er of Collocation 3roupsG from collocgroup
Crawford
select count+:- as GHum%er of .rchive Copy3roupsG from arIcopygroups
select count+:- as GHum%er of 4ac>up Copy3roupsG from %uIcopygroups
select count+:- as GHum%er of 8ata 7oversG from datamovers
select count+:- as GHum%er of 8evice ClassesG from devclasses
select count+:- as GHum%er of 8omainsG from domains
select count+:- as GHum%er of 8rivesG from drives
select count+:- as GHum%er of <i%rariesG from li%raries
select count+:- as GHum%er of <i%rary "olumesG from li%volumes
select count+:- as GHum%er of "olumesG from volumes
select count+:- as GHum%er of 7anagement ClassesG from mgmtclasses
select count+:- as GHum%er of Hode 3roupsG from nodegroup
select count+:- as GHum%er of 8evice PathsG from paths
select count+:- as GHum%er of Policy 6etsG from policysets
select count+:- as GHum%er of Client 6chedulesG from clientIschedules
select count+:- as GHum%er of .dmin 6chedulesG from adminIschedules
select count+:- as GHum%er of 6erver 6criptsG from scripts
select count+:- as GHum%er of 6ervers 8efinedG from servers
select count+:- as GHum%er of 6ervers 3roups 8efinedG from serverIgroup
select count+:- as GHum%er of 6torage Pools 8efinedG from stgpools
select nodeIname, count+:- as GHum%er of 9ilespacesG from filespaces group %y nodeIname order %y 1
select platformIname, count+:- as GHum%er of HodesG from nodes group %y platformIname
select count+:- as GHum%er of .dministratorsG from admins
select nodeIname,sum+numIfiles- as GHum%er of 4ac>up 9ilesG from occupancy where type=K4>upK group %y
nodeIname
select nodeIname,sum+numIfiles- as GHum%er of .rchive 9ilesG from occupancy where type=K.rchK group %y
nodeIname
select count+:- as GHum%er of 6chedule .ssociationsG from associations
select count+:- as GHum%er of 4ac>upsetsG from %ac>upsets
select count+:- as GHum%er of Client &ption 6etsG from cloptsets
select count+:- as GHum%er of Collocation 3roupsG from collocgroup
select count+:- as GHum%er of .rchive Copy3roupsG from arIcopygroups
select count+:- as GHum%er of 4ac>up Copy3roupsG from %uIcopygroups
select count+:- as GHum%er of 8ata 7oversG from datamovers
select count+:- as GHum%er of 8evice ClassesG from devclasses
select count+:- as GHum%er of 8omainsG from domains
select count+:- as GHum%er of 8rivesG from drives
select count+:- as GHum%er of <i%rariesG from li%raries
select count+:- as GHum%er of <i%rary "olumesG from li%volumes
select count+:- as GHum%er of "olumesG from volumes
Crawford
select count+:- as GHum%er of 7anagement ClassesG from mgmtclasses
select count+:- as GHum%er of Hode 3roupsG from nodegroup
select count+:- as GHum%er of 8evice PathsG from paths
select count+:- as GHum%er of Policy 6etsG from policysets
select count+:- as GHum%er of Client 6chedulesG from clientIschedules
select count+:- as GHum%er of .dmin 6chedulesG from adminIschedules
select count+:- as GHum%er of 6erver 6criptsG from scripts
select count+:- as GHum%er of 6ervers 8efinedG from servers
select count+:- as GHum%er of 6ervers 3roups 8efinedG from serverIgroup
select count+:- as GHum%er of 6torage Pools 8efinedG from stgpools
Stopping the server efore installing the upgrade
*******************************************************
6top all server processes and dismount any tapes that are mounted. 5hen stop the server.
5he commands in the following procedure are 5ivoliD 6torage 7anager administrative commands.
=. Cancel sessions if any are still running. #se the commandE
cancel session
.llow time for the sessions to %e stopped. 6ome sessions, such as %ac>up %y a %ac>up,archive client,
might ta>e some time to stop.
1. 8etermine whether server processes are running. ither cancel processes, or allow them to complete.
#se the commandsE
query process
cancel process processInum%er
.llow time for the processes to %e stopped. 6ome processes, such as storage pool migration, might ta>e
some time to stop.
3. .fter all sessions and processes are stopped, determine whether any tapes are mounted. 8ismount any
tapes that are mounted. #se the commandsE
query mount
dismount volume volumeIname
(. 6top the server. #se the commandE
Crawford
halt
-nstalling the upgrade utilities on A-. s&stems
****************************************************
/nstall the upgrade utilities on the system. 5he pac>age to install is availa%le for download from the 95P
downloads site. 5he upgrade utilities are used to prepare and e@tract the data%ase from the original server.
=. &%tain the upgrade utilities pac>age from the 95P downloads site.
=. 3o to ftpE;;ftp.software.i%m.com;storage;tivoli,storage,management;maintenance;server,
upgrade;v!r!;
1. Havigate to the directory that names the operating system that your "! server runs on. 9rom that
directory, open the !.!.@.@ directory. 5he !.!.@.@ num%er must %e the same as or later than the level of the "!
server that you are upgrading.
3. 6elect the pac>age that matches your platform, and download it to a convenient location on the
server system. 5he name of the pac>age has the following formE
!.!.@.@,5/",567#P3,./0.tar.gL
5he num%ers at the %eginning of the pac>age name identify the release level of the upgrade utilities
pac>age. 5he level of the upgrade utilities pac>age must %e the same as or later than the level of the "!
server that you are upgrading.
(. &ptionalE 5o install messages in a language other than nglish, open the <.H3 directory, and
download a language pac>age. 5ranslated messages are availa%le in the usual set of languages for a "!
server.
1. <og in with the root user /8.
3. nsure that the system has the following file sets installedE
: @lC.rte B.2.2.!, or later
: gs>sa.rte *.2.(.==
Fou can use the following commands to chec> for these file setsE
lslpp ,< @lC.rte
lslpp ,< gs>sa.rte
/f needed, you can o%tain the gs>sa.rte file set from any of the regular "!.! maintenance pac>ages for
the ./0D server. 5he maintenance pac>ages are availa%le on the 95P downloads siteE
ftpE;;ftp.software.i%m.com;storage;tivoli,storage,management;maintenance;server;v!r!;./0;
(. @tract the contents of the upgrade utilities pac>age. /f you downloaded a language pac>age, also
e@tract the contents of that pac>age.
!. .ccess the 6ystem 7anagement /nterface 5ool +67/5-.
=. nter smitty installIupdate
Crawford
1. 6elect /nstall and #pdate 6oftware M /nstall and #pdate from .<< .vaila%le 6oftware.
6. 6elect the /HP#5 device. 6pecify the directory location of the upgrade utilities pac>age on the system.
*. 6elect 6oftware to /nstall. Press 9( or sc?( for the list of availa%le file sets in the directory.
B. 6elect the file sets for the upgrade utilities, the device driver, and optionally the language pac>. 5he file
set for the upgrade utilities is tivoli.tsmupg.server. &ptional language pac>s include messages for languages
other than #.6. nglish.
A. 6et C&77/5 software updates to Fes. Press 9( or sc?(.
=2. 6et 6." replaced files to Ho.
==. nsure that the default settings for the options in the window for all the selected file sets show success.
=1. Press nter, and respond to the .R F&# 6#RN question %y pressing nter again. 5he installation
%egins.
=3. 'hen the installation is complete, e@it the 67/5 program.
=(. &ptionalE /f you installed a language pac>age, ensure that the locale environment varia%le is set to use
it. nter the following command to set the locale environment varia%le for messagesE
e@port <CI766.36=@@@@
where @@@@ is the locale that you want to use. 9or e@ample, use itI/5 for /talian. 5he upgrade utilities run
with the locale that you specify if the following statements are trueE
: 5he locale is installed on the system.
: 5he upgrade utilities support the locale.
: 5he language pac>age that you installed for the upgrade utilities matches the local
Setting /nvironment values
****************************
.fter installing the upgrade utility pac>age, you must set environment varia%les in the shell from which you
will run the utilities. .n environment varia%le descri%es the operating environment of a process, such as the
home directory or terminal in use.
8676R"I8/R
6pecifies the installed location of the upgrade utilities.
4y default the location isE
: ./0 operating systems ;usr;tivoli;tsm;upgrade;%in

e@port 8676R"I8/R=;usr;tivoli;tsm;upgrade;%in
0reparing the dataase of a V5 server for upgrade
**************************************************
Crawford
4efore e@tracting the data from the data%ase, you must prepare the server data%ase %y using the
867#P3R8 PRP.R84 utility.
/f you have multiple servers on a single system, you must repeat this tas> for each server.
=. nsure that you have completed all preparation steps.
1. <og in using the root user /8 on the system that has the original server.
3. Change to the instance directory for the server that you are upgrading. 5he instance directory is the
directory that contains the files such as dsmserv.ds> for the server.
(. Prepare the data%ase. 8irect the output of the process to a file for monitoring.
./0 operating systems
9rom the instance directory for the server that you are upgrading, issue the following command to run the
process in the %ac>ground and direct the
output to the file called prepare.outE
nohup ;usr;tivoli;tsm;upgrade;%in;dsmupgrd prepared% Mprepare.out 1MO= O
!. 7onitor the process for errors and warning messages. 5he final message indicates success or failure of
the operation. 9rom the instance directory
for the server that you are upgrading, issue the following command to monitor the processE
tail ,f prepare.out
6. nsure that the prepare operation is completed successfully %efore continuing to the ne@t step. /f the
prepare operation fails,
you might need to restart the "! server to fi@ the pro%lem and run the prepare operation again. /f the server
%eing upgraded is a "!.3 or "!.( server,
you might need to restore the data%ase using a %ac>up %efore you can restart the server to correct the
pro%lem.
Uninstalling the V5 program efore installing V6.2
***************************************************
9or %est results when you are upgrading the server to "6.1 on the same system where the "! server is
located, uninstall the "! server program %efore installing the "6.1 server program.
#ninstalling the "! program on ./0D systems
Crawford
#ninstall the "! server, server license, and device driver. 8o not remove the data%ase, recovery log, or any
other related files or directories, such as the server options file.
: 9or a "!.( or "!.! server, issue the following commandsE
;usr;s%in;installp ,ug tivoli.tsm.license.ai@!.rte6(
;usr;s%in;installp ,ug tivoli.tsm.devices.ai@!.rte
;usr;s%in;installp ,ug tivoli.tsm.server.ai@!.rte6(
-nstalling the V6.2 server
***************************
nsure that you have completed all upgrade preparation steps, including %ac>up of the server data%ase,
%efore %eginning the installation procedure. 5he server will not %e availa%le until after installation and
upgrade steps are completed.
# <og on to the system.
./0 operating systems
<og in using the root user /8.
#/f you downloaded the program from Passport .dvantageD as an e@ecuta%le file, complete the following
steps.
./0 operating systems
=. "erify that you have enough space to store the installation files when they are e@tracted from the
product pac>age.
6pace requirements for ./0
: =*22 74 of dis> space to store the downloada%le part.
: 136! 74 of dis> space to unpac> the part.
H&5E 5he ./0 "ersion A.2.2.B C Runtime <i%rary consumes appro@imately *B 74 when the
part is unpac>ed. /nstallation of the "ersion A.2.2.B Runtime <i%rary is optional depending on whether the
minimum required li%rary level is already installed.
: =**2 74 in ;opt and 336 74 in ;usr ,,, dis> space for the installed product.
: 16 74 of space in ;tmp to run the installation program.
1. Change to the directory where you placed the e@ecuta%le file.
Crawford
5ipE nsure that the file is in the directory where you want the e@tracted files to %e located. /n a later
step, the files are e@tracted to that directory.
3. Change the file permissions %y entering the following commandE
chmod a?@ pac>ageIname.%in
5he pac>ageIname is CP36s7<.%in
(. @tract the installation filesE
.;CP36s7<.%in
5he pac>age is large, so the e@traction ta>es some time
#Fou can use either the graphical wiLard or the console wiLard.
./0 operating systems
: 6tart the graphical wiLardE
.;install.%in
: 6tart the console wiLardE
.;install.%in ,i console
6elect the language for the installation and follow the instructions.
./0 operating systems
=. Fou must accept the license agreement to complete the installation.
1. 6elect the components to install. Fou must select at least the server, license, and 5ivoli 6torage
7anager 6erver <anguages in the component
list. 5ypical installations also include the device driver. 9or information a%out other components that you can
choose to install, see the information
a%out installing a new server.
3. &n the 6erver <anguage 6election page, select nglish +not #59B- and any other language pac>s
that you need.
Fou must select nglish %ecause it installs the tivoli.tsm.server.msg.enI#6 pac>age, which includes the
help messages.
Crawford
'hen the installation is complete, verify that you see a message that the installation is successful.
/mportantE /f there are any errors during the installation, a summary panel lists the errors and directs you to
an error log file. 9i@ the errors %efore continuing with the upgrade.
5he installation log is stored in the following locationE
;var;tivoli;tsm
# 8ownload and apply any applica%le fi@es that have %een released for the server. 3o to the product support
site, httpE;;www.i%m.com;support;entry;portal;&verview;6oftware;5ivoli;5ivoliI6torageI7anager, and clic>
8ownload. 6earch for server updates.
Fou can also chec> the 95P downloads siteE ftpE;;ftp.software.i%m.com;storage;tivoli,storage,
management;maintenance;server;
1Creating the directories and the user -' for the upgraded server instance
***************************************************************************
Create the directories that the server instance needs for data%ase and recovery logs, and create the user /8
that will own the server instance.
=. Create the user /8 that will own the server instance. Fou use this user /8 when you create the server
instance in a later step.
./0 operating systems
Create a user /8 and group that will %e the owner of the 5ivoliD 6torage 7anager server instance.
=. Create the user /8 and group.
RestrictionE 5he user /8 and group name must comply with the following rulesE
: /n the user /8, only lowercase letters +a,L-, numerals +2,A-, and the underscore character + I -
can %e used. 5he user /8 must %e B characters or less, and cannot start with i%m, sql, sys, or a numeral.
: /n the group name, only lowercase letters +a,L-, numerals +2,A-, and the underscore character +
I - can %e used. 5he group name must %e B characters or less, and cannot start with i%m, sql, or a numeral.
9or e@ample, create user /8 tsminst= in group tsmsrvrs. 5he following e@amples show how to
create this user /8 and group using operating system commands.
./0 operating systems
Crawford
# m>group id==22= tsmsrvrs
# m>user id==221 pgrp=tsmsrvrs home=;home;tsminst= tsminst=
# passwd tsminst=
1 . Create directories that the server requires. Fou need unique, empty directories for each of the items
shown in the following ta%le.
Create the data%ase directories, the active log directory, and the archive log directory on different physical
volumes.
6ee the planning information for details.
./0 operating systems
5he instance directory for the server, which is a directory that will contain files specifically for this server
instance +the server options file and other server,specific files-
eg E m>dir ;home;tsminst=;tsminst=
5ipE 9or this e@ample, the instance directory is created in the home directory for the instance owner /8,
tsminst=. Fou can place it in other locations.

5he data%ase directories
egE
m>dir ;tsmd%22=
m>dir ;tsmd%221
m>dir ;tsmd%223
m>dir ;tsmd%22(

.ctive log directory
egE m>dir ;tsmlog
.rchive log directory
egE m>dir ;tsmarchlog
Crawford

&ptionalE 8irectory for the log mirror for the active log
egE m>dir ;tsmlogmirror

&ptionalE 6econdary archive log directory +failover location for archive log-
egE m>dir ;tsmarchlogfailover
3 . 9or all directories that were created for the server instance, ensure that the user /8 that owns the server
instance has access.
5he directories to chec> include the instance directory and all data%ase and log directories.
./0 operating systems
Change the owner of the directories that were created to the user /8 for the server instance.
4elow Commands can %e used in ./0 to change the ownership
chown QuseridMEQgoupidM QfilenameM
gE
chown tsminst=Etsmsrvrs ;home;tsminst=
( .9or all dis> space that is used %y the "! server for storage pools +device types of 9/< and 8/6J-, change
ownership or access control so that the user /8
that will own the upgraded 5ivoli 6torage 7anager server instance has ownership or read;write permission.
#se the appropriate method for your operating system.
'e can #se %elow Commands to 8o the a%ove steps
m>vg ,y tsminstvg ,sK1!6K hdis>=A
m>vg ,y tsminstd%vg ,sK1!6K hdis>1 hdis>3 hdis>=1 hdis>=3 hdis>=( hdis>12
m>vg ,y tsminstlogvg ,sK1!6K hdis>=6 hdis>=* hdis>=B hdis>=!
m>lv ,y tsminst ,t Rfs1 tsminstvg *
m>lv ,y d%IdirI22=lv ,t Rfs1 tsminstd%vg 1!2
m>lv ,y d%IdirI221lv ,t Rfs1 tsminstd%vg 1!2
m>lv ,y d%IdirI223lv ,t Rfs1 tsminstd%vg 1!2
m>lv ,y d%IdirI22(lv ,t Rfs1 tsminstd%vg 1!2
m>lv ,y d%IdirI22!lv ,t Rfs1 tsminstd%vg 1!2
m>lv ,y d%IdirI226lv ,t Rfs1 tsminstd%vg 1!2
m>lv ,y tsminstlv ,t Rfs1 tsminstvg =
Crawford
crfs ,v Rfs1 ,d tsminst ,m ;home;tsminst= ,pKrwK ,a ag%l>siLe=K(2A6K ,a logname=K/H</HK
crfs ,v Rfs1 ,d d%IdirI22=lv ,m ;tsminst=;d%IdirI22= ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d d%IdirI221lv ,m ;tsminst=;d%IdirI221 ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d d%IdirI223lv ,m ;tsminst=;d%IdirI223 ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d d%IdirI22(lv ,m ;tsminst=;d%IdirI22( ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d d%IdirI22!lv ,m ;tsminst=;d%IdirI22! ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d d%IdirI226lv ,m ;tsminst=;d%IdirI226 ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d logIactlv ,m ;tsminst=;logIact ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a logname=K/H</HK
crfs ,v Rfs1 ,d logIactmlv ,m ;tsminst=;logIactm ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a
logname=K/H</HK
crfs ,v Rfs1 ,d logIarclv ,m ;tsminst=;logIarc ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a logname=K/H</HK
crfs ,v Rfs1 ,d logIarcflv ,m ;tsminst=;logIarcf ,pKrwK ,a options=KcioK ,a ag%l>siLe=K(2A6K ,a logname=K/H</HK
crfs ,v Rfs1 ,d optItsm ,m ;opt;tivoli;tsm ,pKrwK ,a ag%l>siLe=K(2A6K ,a logname=K/H</HK
#pgrading the server manually using utilities
==============================================
#se the utilities to upgrade the server using a command interface.
4efore %eginning the upgrade procedure, you must complete all preceding steps to prepare for the upgrade,
to install the upgrade utilities, to install the "6.1 server program, and to create the directories and user /8 for
the server instance.
Complete the following stepsE
@tracting the data to media
==================================

Fou can e@tract the data from the original server data%ase to sequential media. 5he sequential media can
%e tape, or dis> space that is defined with the 9/< device class.
=. <og in using the root user /8 on the system that has the original server. <og on with the administrator /8
on a 'indowsD system.
1. nsure that the device that you want to use to store the e@tracted data is availa%le. 5he server data%ase
and the device configuration file must contain a valid device class definition for the device.
Crawford
3. 9rom the instance directory for the server that you are upgrading, issue the command to start the
e@traction. 8irect the output of the process to a file for monitoring. 9or e@ample, issue the following
command, on one lineE
./0 operating systems
nohup ;usr;tivoli;tsm;upgrade;%in;dsmupgrd e@tractd% devclass=lto( manifest=.;manifest.t@t Me@tract.out
1MO= O
;usr;tivoli;tsm;upgrade;%in;dsmupgrd e@tractd% devclass=lto manifest=.;manifest.t@t Me@tract.out 1MO= O
ipE 7essages that are issued during the e@tract operation are not saved in the server activity log. 8irect the
output of the utility to a file, as shown in the e@amples, to record the messages.
(.7onitor the process for errors and warning messages, and for items that you might need to ta>e action
on.
. message near the end of the process output indicates success or failure of the operationE
: 6uccess messageE .HR=3B1/ 05R.C584E Process =, data%ase e@tract, has completed.
: 9ailure messageE .HR=3A6 05R.C584E Process =, data%ase e@tract, has completed with errors.
9or e@ample, from the instance directory for the server that you are upgrading, issue the following command
to monitor the processE
tail ,f e@tract.out
5he length of time that the process runs depends on the siLe of the data%ase. 5he time will %e appro@imately
as much as the time required for a full %ac>up of the data%ase.
Creating and formatting the new data%ase
==============================================
Create the server instance and format files for an empty "6.1 data%ase.
=. <og on to the system where you installed the "6.1 program.
./0 operating systems
<og in using the root user /8. Complete the following chec>sE
=. "erify that the home directory e@ists for the user /8 that owns the server instance. 9or e@ample,
if the user /8 is tsminst=, the home directory is ;home;tsminst=.
1. "erify that a configuration profile e@ists for the user /8 in its home directory.
Crawford
/f necessary, create the configuration profile. 9or e@ample, create a .profile file if you are using the Jorn shell
+>sh-.
5he .profile file can %e empty.
1. Create a 5ivoliD 6torage 7anager instance using the d%1icrt command.
./0 operating systems $P,#0 operating systems <inu@ operating systems 6un 6olaris operating systems
nter the following command on one line. 9or the instance name, specify the user /8 that you created to
own the instance.
;opt;tivoli;tsm;d%1;instance;d%1icrt ,a 6R"R S
,u instanceIname instanceIname
9or e@ample, if the user /8 for this instance is tsminst=, use the following command to create the instance.

Remem%erE 9rom this point on, use this new user /8 when configuring your 5ivoli 6torage 7anager server.
<og out of the root user /8,
and log in using the user /8 that is the instance owner.
3. <og on to the system using the user /8 that owns the "6.1 server instance +the instance user /8-.
(. Copy the configuration files to the instance directory that you created for the new server. 5he files are the
configuration files that you saved from the original "! serverE
: 8evice configuration
: 6erver options file +typically named dsmserv.opt-
9or e@ample, if you created the instance directory that is shown in the e@ample in the step to create
directories for the "6.1 server,
copy the files into the following directoryE
: ./0 operating systems
;home;tsminst=;tsminst=
#
Crawford
nsure that the user /8 that owns the "6.1 server +the instance user /8- has ownership or read;write
permission to the files that you copied.
!. dit the server options file.
=. Remove any options that are not supported for "6.1. 9or the list of deleted options, see 5a%le 3 .
1. nsure that the server options file contains at least one "&<#7$/65&RF option and at least one
8"C&H9/3 option. 4ecause a volume history file and a device configuration file are required when you
must restore the data%ase, generate copies of these files automatically to help ensure that the files are
availa%le when needed.
3. Chec> whether the server options file includes the 50H3R&#P7.0 option with a value, and if it does,
what the value is. Fou might want to change the current value %ecause the default value for this option
changes from 1!6 to (2A6 with "6.1. 5he increased value can improve the performance for data movement
operations such as storage pool migration and storage pool %ac>up.
: /f the server options file does not include this option, the server automatically uses the new default
value of (2A6.
: /f the server options file includes a value for this option, the server uses that specified value. /f the
specified value is less than (2A6, consider increasing the value, or removing the option so that the server
uses the new default value.
6. Change the default path for the data%ase.
./0 operating systems
Change the default path for the data%ase to %e the same as the instance directory for the server. /ssue the
commandE
d%1 update d%m cfg using dftd%path instanceIdirectory
9or e@ampleE
d%1 update d%m cfg using dftd%path ;home;tsminst=;tsminst=
* Change to the instance directory that you created for the server.
B Create and format the data%ase and recovery logs. /n the command, specify the directories that you
created for the data%ase and logs.
5he directories must %e empty.
./0 operating systems
9or e@ample, to get an active log siLe of =6 34 +=63B( 74, the default siLe-, issue the following
command, on one lineE
Crawford
;opt;tivoli;tsm;server;%in;dsmserv loadformat S
d%dir=;tsmd%22=,;tsmd%221,;tsmd%223,;tsmd%22( S
activelogsiLe==63B( activelogdir=;tsmlog S
mirrorlogdir=;tsmlogmirror archlogdir=;tsmarchlog
A. 7onitor the process for errors and warning messages. 5he final message indicates success or failure of
the operation.
<oading the e@tracted data into the new data%ase
====================================================
.fter you have formatted an empty data%ase using the 8676R" <&.89&R7.5 utility, load the data that
you e@tracted from the original server data%ase.
5he following requirements must %e metE
: 5he manifest file from the 867#P3R8 05R.C584 operation must %e availa%le.
: 5he server options file must contain an entry for the device configuration file.
: 5he device configuration file must have information a%out the device class that is specified in the
manifest file.
: 5he media that contains the e@tracted data%ase must %e availa%le to the "6.1 server. 5he device must
%e physically attached to the system, and the permissions must %e set to grant access to the media for the
user /8 that owns the "6.1 server instance.
Perform the following stepsE
=. "erify that the "6.1 server can access the e@tracted data.
: /f the e@tracted data is on tape, the tape drive must %e physically attached to the system.
: /f the e@tracted data was stored using a 9/< device classE
=. <og on to the system using the root user /8.
1. Change the ownership of the files to the user /8 that owns the "6.1 server +the instance user /8-.
1. 9or the manifest file that was created %y the e@traction process, ensure that the user /8 that owns the
"6.1 server +the instance user /8- has
ownership or read;write permission.
3. <og on with the server instance user /8.
(. nsure that the device configuration file from the original server is availa%le.
=. "erify that the server option file includes the 8"C&H9/3 option, and that the option specifies the
full path of the device configuration file.
1. "erify that the device configuration file is availa%le in the location specified %y the 8"C&H9/3
option.
Crawford
3. "erify that the permissions on the device configuration file allow read access for the user /8 that
owns the "6.1 server instance.
!. "erify that the contents of the device configuration file are correct. 5he device class that was used for the
e@traction step is recorded in the manifest file, and that device class must e@ist and %e valid on the "6.1
system.
=. "erify entries for 9/< device classes. 9or e@ample, paths might %e different on the system.
1. "erify entries for tape and other devices. 9or e@ample, the device names might have changed.
6. "erify that the contents of the manifest file are correct. 5he manifest file contains a list of volumes to %e
used when loading the e@tracted data into the new data%ase. 9or e@ample, if the manifest file contains a list
of volumes %elonging to a 9/< device class, ensure that the fully qualified path to the volumes is correct for
the system.
*. /ssue the 8676R" /H6R584 command to load an e@tracted server data%ase into the prepared,
empty "6.1 data%ase. 8irect the output of the process to a file for monitoring. 9or e@ample, enter the
following command on one lineE
./0 operating systems
nohup ;opt;tivoli;tsm;server;%in;dsmserv insertd% S
manifest=.;manifest.t@t Minsert.out 1MO= O
B. 7onitor the process for errors and warning messages, and for items that you might need to ta>e action
on. 5he system displays interim statistics a%out the operation. . message near the end of the process output
indicates success or failure of the operationE
: 6uccess messageE .HR=3A!/ /H6R584E Process =, data%ase insert, has completed.
: 9ailure messageE .HR=3A6 /H6R584E Process =, data%ase insert, has completed with errors.
9or e@ample, issue the following command to monitor the processE
tail ,f insert.out
5he length of time that the process runs depends on the siLe of the data%ase.

A. /f you used a tape device, after the insertion operation is complete remove or chec> out from the li%rary
the tape that holds the e@tracted data. Prevent the tape from %eing reused until you are sure that you do not
need to run the insertion operation again
Configuring the system for data%ase %ac>up
=============================================
5he data%ase manager and the 5ivoliD 6torage 7anager .P/ must %e configured so that the data%ase
manager can %ac> up the server data%ase. 5he configuration is completed for you automatically if you use
the upgrade wiLard +dsmupgd@-. /f you do not use the wiLard, you must complete the configuration manually.
Crawford
Configuring the system for data%ase %ac>up on ./0
/f you did not use the upgrade wiLard, you must complete the configuration for the data%ase %ac>up
manually.
/n the following steps, the e@amples use tsminst= for the server instance user /8 and
;home;tsminst=;tsminst= for the 5ivoliD 6torage 7anager server instance directory.
=. 6et the 867/I api environment,varia%le configuration for the data%ase instanceE
=. <og in using the tsminst= user /8.
1. 'hen user tsminst= is logged in, ensure that the 841 environment is properly initialiLed. 5he 841
environment is initialiLed %y running the ;home;tsminst=;sqlli%;d%1profile script, which normally runs
automatically from the user /8Ks profile. /f ;home;tsminst=;.profile does not run the d%1profile script, add the
following lines to ;home;tsminst=;.profileE
if T ,f ;home;tsminst=;sqlli%;d%1profile UV then
. ;home;tsminst=;sqlli%;d%1profile
fi
3. .dd or update the following lines to the userprofile file in the ;home;tsminst=;sqlli% directoryE
./0 operating systems
e@port 867/IC&H9/3=;home;tsminst=;tsminst=;tsmd%mgr.opt
e@port 867/I8/R=;usr;tivoli;tsm;client;api;%in6(
e@port 867/I<&3=;home;tsminst=;tsminst=
1. <og out and log in again as tsminst=, or issue this commandE
. W;.profile
3. Create a file called tsmd%mgr.opt in the ;home;tsminst=;tsminst= directory and add the following lineE
6R"RH.7 5678473RI567/H65=
(. .dd the following lines to the 5ivoli 6torage 7anager .P/ dsm.sys configuration file. 5he dsm.sys
configuration file is in the following default locationE
Crawford
: ./0 operating systems ;usr;tivoli;tsm;client;api;%in6(

.void placing the server name, 5678473RI567/H65=, first in dsm.sys %ecause it should not %e the
system,wide default. /n this e@ample, the added lines are after the stanLa for serverIa.
6ervername serverIa
C&777ethod 5CPip
5CPPort =!22
5CP6erveraddress node.domain.company.C&7
servername 5678473RI567/H65=
commmethod tcpip
tcpserveraddr localhost
tcpport =!22
passwordaccess generate
passworddir ;home;tsminst=;tsminst=
errorlogname ;home;tsminst=;tsminst=;tsmd%mgr.log
nodename XXI5678473RIXX
!. 6top and start the data%ase instanceE
=. 6top 841E
d%1stop
1. 6tart 841E
d%1start
6. 6et the .P/ passwordE
=. nsure that the 5ivoli 6torage 7anager server is started. 6ee 6tarting the server on ./0, $P,#0,
<inu@, and 6un 6olaris systems for the details.
1. <og in using the root user /8.
3. 6ource the data%ase manager %y running the following command.
/mportantE 6un 6olaris operating systems 6witch to the Jorn shell +;%in;>sh- %efore running the
following command.
. ;home;tsminst=;sqlli%;d%1profile
Crawford
(. Change the .P/ password, using this commandE
;home;tsminst=;sqlli%;adsm;dsmapipw
!. 'hen prompted %y the dsmapipw command, specify 5678473R as %oth the original and new
password.
6. nter this operating system commandE
rm ;home;tsminst=;tsminst=;tsmd%mgr.log
5he data%ase manager and the 5ivoliD 6torage 7anager .P/ must %e configured so that the data%ase
manager can %ac> up the server data%ase.
5he configuration is completed for you automatically if you use the upgrade wiLard +dsmupgd@-.
/f you do not use the wiLard, you must complete the configuration manually.
Post /mplementation 6teps
==============================
"erifying access to storage pools on dis>
9or all dis> space that was used for storage pools +device types of 9/< or 8/6J- %y the "! server, verify that
the user /8 that owns the upgraded
5ivoliD 6torage 7anager server instance has ownership or read;write permission.
6tarting the server instance after the upgrade
==================================================
"erify that the server instance is correctly set up %y starting the server instance.
Remem%erE 6tarting the server is an operating system,level operation and has certain restrictions.
/f you do not have the permissions to use the 8676R" program, you cannot start it. /f you do not have
authority to read or write files in the
instance directory, you cannot start that instance of the server.
: ./0 operating systems
Fou can start the server when logged in to the system with the user /8 that you created for the server
instance.
Crawford
Fou can also start the server instance when logged in as the root user.
Registering licenses
=======================
/mmediately register any 5ivoliD 6torage 7anager licensed functions that you have purchased so that you do
not lose any data after you
%egin using the server. #se the R3/65R </CH6 command for this tas>.
4ac>ing up the data%ase after upgrading the server
====================================================
.fter successfully upgrading the server, perform a full %ac>up of its data%ase as soon as possi%le. 4efore
performing the %ac>up, you must first select the device class for %ac>ups of the data%ase.
=. Complete the following stepsE
=. /f you did not use the upgrade wiLard +dsmupgd@- to upgrade the server, ensure that you have
completed the steps to manually configure the system for data%ase %ac>ups.
1. /f you used the media method for upgrade and used a tape device, remove or chec> out from the
li%rary the tape that was used to hold the e@tracted data. Prevent the tape from %eing reused until you are
sure that the upgraded server is running properly and you do not need to repeat the data%ase insertion step.
1. 6elect the device class to %e used for automatic %ac>ups of the data%ase. /ssue the following command
from a /47D 5ivoliD 6torage 7anager administrative command line.
set d%recovery deviceIclassIname
5he device class that you specify is used %y the data%ase manager for all automatic data%ase %ac>ups.
3. 4ac> up the data%ase.
%ac>up d% devclass=deviceIclassIname type=full
5he device class can %e the same as or different from the device class that you specified with the 65
84RC&"RF command. /f the device class is different, you receive a warning message, %ut the %ac>up
operation continues.
"erifying the upgraded server
================================
"erify the operation of the server. /f the server was installed on a new system as part of the upgrade, chec>
and update connections to storage devices and other components.
Crawford
=. 7onitor the messages that the server issues as it starts. 'atch for error and warning messages.
1. /f the server is running on a new system as a result of the upgrade, chec> the following itemsE
=. nsure that all of the original serverKs storage devices are accessi%le to the upgraded server.
1. Compare the device names on the new system with the names for the devices on the original
system. #pdate definitions for the devices on the server if needed. 9or e@ample, update path definitions.
3. #pdate the networ> address that is used %y %ac>up,archive clients, storage agents, li%rary client
servers, and other servers for communicating with the upgraded server.
&ptionally, instead of ma>ing these updates, consider whether you can use the networ> address of
the original system as the address of the new system. Fou might also %e a%le to update domain name
service +8H6- to point to the new system instead of the original system. Consult your networ> administrator.
3. "erify that you can connect to the server using an administrative client as you did for the earlier version
of the server.
(. Run commands to get a summary of information in the data%ase. Compare the summary with the results
for the same commands %efore the upgrade.
!. Perform %ac>ups for typical client nodes and verify that the %ac>ups wor> as e@pected.
6. "erify that operations such as <.H,free data movement and li%rary sharing wor> correctly.
*. .fter you are satisfied that the server is performing as e@pected and you will not need to revert to the
previous version of the server, remem%er to return any settings that you changed to prepare for the upgrade
%ac> to the original values.
#pdating automation
===============================
.fter an upgrade, administrative schedules that were defined in "! might not wor> without modification
%ecause of changes in command synta@. /mplement and verify changes to any automation or scripts that
were identified as needing modification in the planning process.
/mportantE nsure that automation includes a %ac>up of the data%ase. 4ac> up the data%ase at least once
per day.
7onitoring the upgraded server
=================================
'hen you start using the upgraded server in production operation, monitor the space used %y the server to
ensure that the amount of space is adequate. 7a>e adRustments as needed.
=. 7onitor the active log, to ensure that the siLe is correct for the wor>load that is handled %y the server
instance.
'hen the server wor>load is up to its typical e@pected level, and the space that is used %y the active log
is B2 , A2Y of the space that is availa%le to the active log directory, you might need to increase the amount of
Crawford
space. 'hether you need to increase the space depends on the types of transactions in the serverKs
wor>load, %ecause transaction characteristics affect how the active log space is used.
5he following transaction characteristics can affect the space usage in the active logE
: 5he num%er and siLe of files in %ac>up operations
o Clients such as file servers that %ac> up large num%ers of small files can cause large num%ers of
transactions that complete during a short period of time. 5he transactions might use a large amount of space
in the active log, %ut for a short period of time.
o Clients such as a mail server or a data%ase server that %ac> up large chun>s of data in few
transactions can cause small num%ers of transactions that ta>e a long time to complete. 5he transactions
might use a small amount of space in the active log, %ut for a long period of time.
: Hetwor> connection types
o 4ac>up operations that occur over fast networ> connections cause transactions that complete
more quic>ly. 5he transactions use space in the active log for a shorter period of time.
o 4ac>up operations that occur over relatively slower connections cause transactions that ta>e a
longer time to complete. 5he transactions use space in the active log for a longer period of time.
/f the server is handling transactions with a wide variety of characteristics, the space that is used for the
active log might go up and down %y a large amount over time. 9or such a server, you might need to ensure
that the active log typically has a smaller percentage of its space used. 5he e@tra space allows the active log
to grow for transactions that ta>e a very long time to complete, for e@ample.
1. 7onitor the archive log to ensure that space is always availa%le.
Remem%erE /f the archive log %ecomes full, and the archive failover log %ecomes full, the active log can
%ecome full and the server will stop. 5he goal is to ma>e enough space availa%le to the archive log so that it
never uses all its availa%le space.
Fou are li>ely to notice the following patternE
=. /nitially, the archive log grows rapidly as typical client,%ac>up operations occur.
1. 8ata%ase %ac>ups occur regularly, either as scheduled or done manually.
3. .fter full data%ase %ac>ups occur, log pruning occurs automatically. 5he space used %y the archive
log decreases when the pruning occurs.
(. Hormal client operations continue, and the archive log grows again.
!. 8ata%ase %ac>ups occur regularly, and log pruning occurs as often as full data%ase %ac>ups occur.
'ith this pattern, the archive log grows initially, then decreases, then might grow again. &ver a period of
time, as normal operations continue, the amount of space used %y the archive log should reach a relatively
constant level.
/f the archive log continues to grow, consider ta>ing one or %oth of these actionsE
: .dd space to the archive log. 5his might mean moving the archive log to a different file system.
: /ncrease the frequency of full data%ase %ac>ups, so that log pruning occurs more frequently.
3. /f you defined a directory for the archive failover log, determine whether any logs get stored in that
directory during normal operations. /f the failover log space is %eing used, consider increasing the siLe of the
archive log. 5he goal is that the archive failover log is used only under unusual conditions, not in normal
operation.
Crawford
4ac>outplan
==================
Reverting from "6.1 to the previous "! server version
====================================================
/f you need to revert to the previous version of the server after an upgrade, you must have a full data%ase
%ac>up from your original version, the server installation media for your original version, and >ey
configuration files. 4y carefully following the preparation steps %efore upgrading the server, it might %e
possi%le to revert to the previous version of the 5ivoliD 6torage 7anager server with minimal loss of data.
Fou must have the following items from the earlier version of the serverE
: 6erver data%ase %ac>up
: "olume history file
: 8evice configuration file
: 6erver options file
: 5he dsmserv.ds> file
5he value of the R#68<.F parameter for storage pools compared to the length of time that you were
running the "6.1 server can affect whether client data is affected %y reverting to the earlier server version.
6teps for reverting to the previous server version
,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
=. 4ac> up the "6.1 data%ase and save the contents of the instance directory, including the volume history
file, the device configuration file, and server options file. Jeep these files in case you need to return to the
"6.1 version of the server.
1. Remove the data%ase from the data%ase manager, then delete the data%ase and recovery log
directories.
=. 7anually remove the data%ase. /ssue the commandE
dsmserv removed% tsmd%=
Fou can also use the following command to remove the data%aseE
d%1 drop d% tsmd%=
1. /f you need to reuse the space that is occupied %y the data%ase and recovery log directories, you
can now delete these directories.
3. #se the installation program to uninstall the "6.1 server. #ninstallation removes the server and the
data%ase manager code, with their directories.
6ee #ninstalling 5ivoli 6torage 7anager for details.
Crawford
(. Reinstall the version of the server program that you were using %efore the upgrade to "6.1. 5his version
must match the version that your server was running when you created the data%ase %ac>up that you will
restore in a later step.
9or e@ample, if the server was at version !.(.(.2 %efore the upgrade, and you intend to use the data%ase
%ac>up that was in use on this server, you must install the "!.(.2.2 server program and then the "!.(.(.2 fi@
pac> to %e a%le to restore the data%ase %ac>up.
=. Reinstall the %ase version of the server that was in use %efore the upgrade to "6.1.
1. Reinstall any fi@ pac>s that had %een installed on the %ase server version %efore the upgrade to
"6.1.
!. Copy the following files, which were %ac>ed up %efore the upgrade of the original server, to the directory
for server information.
: 8evice configuration file
: "olume history file
: 5he dsmserv.ds> file
: 5he server options file +typically dsmserv.opt-
6. 9ormat the data%ase %y using the 8676R" 9&R7.5 utility. 9or details see the information for the
version of the server that you are reinstalling. /nformation for "!.! is availa%le at this information centerE
httpE;;pu%li%.%oulder.i%m.com;infocenter;tivihelp;v=r=
/nformation for "!.( and "!.3 is availa%le in the same information center. /n the navigation pane, scroll
down and e@pand Previous versions.
*. Restore the data%ase using the %ac>up that was created in the preparation steps %efore the upgrade.
B. /f you ena%led data deduplication for any 9/<,type storage pools that e@isted %efore the upgrade, or if
you moved data that e@isted %efore the upgrade into new storage pools while using the "6.1 server, you
must perform additional recovery steps. 6ee .dditional recovery steps if you created new storage pools or
ena%led data deduplication.
A. /f the R#68<.F setting on storage pools was less than the age of the data%ase that you restored,
then restore volumes on any sequential,access storage pools that were reclaimed after that data%ase
%ac>up. #se the R65&R "&<#7 command.
/f you do not have a %ac>up of a storage pool, audit the reclaimed volumes using the .#8/5 "&<#7
command, using the 9/0=F6 parameter to resolve inconsistencies. #se the commandE
audit volume volumeIname fi@=yes
=2. /f client %ac>up or archive operations were performed using the "6.1 server, you might need to audit the
storage pool volumes on which the data was stored.
==. /f you were using active,data pools %efore upgrading to "6.1, you must recreate them after reverting to
the earlier version of the server.
5he amount of time required to recreate the active,data pools might %e significant, depending on the
num%er and siLe of the active,data pools to %e recreated.
Crawford
So after setting up numerous TSM 6.1 and 6.2 servers here are a few of the things that have been
little gotchas. They were never upgrade stoppers but they did cause some headaches as we
determined what was causing the errors.
Check the T!" version #recommend 11.$%
Check your $lC C&& runtime level #recommend '.(.(.) or greater%
*ith +, you must have IOCP set to available or else you-ll have to update the .S
setting and reboot the server.
Crawford
Make sure the user id that the TSM 6.$ instance is running under has ulimit set to
unlimited. /eal pain when you go to create disk volumes and you forgot to set the ulimit. +t
was my absentminded moment0
1on-t forget that the tsmdbmgr.log file ownership needs to be the new +1 not root.
lso when using /* disk volumes for TSM diskpools chown the device file #e$ample2
3dev3rtsmdata(1% to the new user id or TSM will say it-s unavailable.
*ith a recent upgrade we could not get the TSM 14 backup to e$ecute without an error. +t
turned out the TSM client-s dsmtca file ownership had been accidentally changed to the
TSM server-s user +1 and it MUST BE O!E" B# $OOT for the backup of the TSM 14
to e$ecute successfully.
+f you have anything you-ve e$perienced you consider a 56.TC75 8 whether it be 9:+, or
*indows8 then leave a comment and help others who might run across the same issue#s%.
Crawford