This install is a TSM 6 by hedongchenchen

VIEWS: 15 PAGES: 23

									This install is a TSM 6.1 UPGRADE of a TSM 5.5 environment on the same machine.
The below steps explain and illustrate each step.

Assumptions: 64bit OS w/ a minimum of 8Gb of RAM.




Once you get the code from PartnerWorld, it should be zipped into a self-extracting
executable (as seen above) that is roughly 1.4Gb in size. The other file (the highlighted
one) is for the database upgrade that is used later on during the install. The preferred
method of extraction is to place the file into its own directory off of a root drive
(Preferably not the C drive). DO NOT execute this file from the desktop, it WILL FAIL.




Once the file is executed, it will begin extracting the files into two newly created
subdirectories.
When the extraction is finished, the folder should look similar to the above.




At this point we need to STOP the existing TSM services and completely uninstall the
application. There CANNOT be a TSM 5.x instance and a TSM 6.x instance on the same
machine. From the “Start” -> “Run” menu, type in “services.msc” and press enter to get
to the services window. Select both the TSM server service and the TSMReptSvc and
stop them by right-clicking and choosing “Stop”.




Next, we need to uninstall everything that relates to TSM 5.x from the OS. Go into “Add
or Remove Programs” from the Control Panel and select the TSM apps and click
“Remove” for each one. This includes the TSM Device Driver. This process will
uninstall all of the application binaries but leave the TSM DB and Log data intact so that
they can be converted to 6.x.

The install.exe in our TSM6 upgrade folder is the next file that you need to run for the
TSM 6.1 upgrade. Double-click the install.exe.




Once this is done you are prompted to select a language to use for the installation. I
chose English, but if you’re up to the challenge, select something different.




Now we’re at the initial splash screen for the install. Once you hit “Next” you get to the
Software License Agreement screen. Select the “I accept” option and proceed to the next
screen.
On this screen, select the Server (first option) to install. Additional languages aren’t
typically needed so leave that option blank. You’ll need the TSM License and Device
Driver, so select those. If your site takes advantage of the SAN storage agent, then you
can select that to be installed. The last option pertains to where the ISC should be
installed. If you’d like for the ISC to be installed on the TSM server, select this option,
otherwise it can be installed on the TSM Reporting server.
On the next screen you are prompted to enter in the DB2 username and password. Keep
the default username and database name and enter in the password a couple times. Hit
“Next” when you’re done.
 At this point the installed begins to do some preliminary configuration. It sits on this
screen for a bit but eventually changes to another screen where it begins to configure
TSM. It’ll remain on that wait screen for a while as well.
Eventually, you’ll end up on the Summary screen. Review the information and when
you’re ready to take the plunge… hit it.
The install takes a while to complete and will remain on this screen.
After about 20minutes or so, the install will finish and you’ll be presented with the screen
above. Hit “Done” and the program will close out and you’ll be back at the desktop.




Now it’s time to launch the other file that actually performs the upgrade. Launch this
executable and answer “Next” a couple times so that it will begin to extract the remainder
of the files needed for the upgrade.




This self-extracting executable will flash through a couple screens as it unpacks files and
then will finish.
Browse to the TSM server directory and launch the dsmupgdx.exe file. This is the
upgrade Wizard.




You’re going to get to a similar screen as before where you have to select your language.
Once you hit “Next” you’ll get to the Welcome screen. Click “Next” again to get to the
above-pictured screen. Since we’re upgrading the TSM 5.x environment on the same
server, be sure to select the first option, “…on this system”.
Since this is a fresh upgrade we’re doing (and not continuing an older upgrade), the only
available option should be “Begin a new upgrade…” Select this option and click “Next”.
Since we haven’t started the upgrade yet, the only enabled option should be, “Prepare the
database for the upgrade”. Select it and click “Next”.
The installer should automatically detect any available TSM instances to upgrade. Select
the instance to upgrade and click “Next”. This will take you to a verification screen
where you need to make sure the paths are correct to the DB and LOG files. Once
verified, click “Next”.
The database preparation phase takes a few minutes to complete. Once it’s finished,
you’ll see the message “Preparation completed with return code 0” and the “Next” button
will be enabled. Once you click “Next”, you’ll be brought back to the Select Upgrade
Phase screen where you can perform the next step in the upgrade.
For the method type, select “Use media” and click “Next”. This takes you back to the
Select Upgrade Phase screen. From there, choose “Extract the existing database…” and
click “Next”
On this screen you’ll have to select whichever device class that was used for database
backups in the previous configuration. Type in specific volumes to use if you’d like to
target them, otherwise leave the default value for scratch volumes.
This extraction will take just a few minutes and will end with the message “Extraction
completed with return code 0”. At this point, the “Next” button will become enabled.
You’ll be sent back to the Select Upgrade Phase screen and be prompted to make a
selection. The next step is to “Configure the new server instance”. Select this option and
click “Next” a couple times.
This screen is asking for an operating system username and ID for the TSM services to
run as. At this point you can create a specific OS user for the services or enter in the
administrator account. Clicking “Next” brings you to the following screen where you
select the directory where the TSM instance should reside. Make your selection and click
“Next”.
On this screen, TSM wants you to specify the directories where the database volumes
will be located. According to the tuning guide, IBM recommends the database be spread
over 3+ spindles for performance reasons. Either create a file that has all of the
directories listed (1 per line) or choose the second option and list them in the box
provided, as seen above. Click “Next” when finished.
This next screen prompts you for log locations. The first 3 values are required (as
indicated by the asterisk), the active log size, active log directory, and the archive log
directory. The remaining two options are for an active log mirror directory and
secondary archive log directory. Create these directories and enter them in being sure to
spread them across spindles for performance reasons. Click “Next” when finished and
you’ll be brought to the Summary screen where you can review your entries. Click
“Next” once more if you’re satisfied with the values.
This format takes a little while, approximately 20min, and will finish with the message
“Format completed with return code 0”. Once it’s done, the “Next” button will become
enabled and will bring you back to the Select Upgrade Phase screen when pressed. From
that screen, select the last option “Insert the data into the new service instance” and click
“Next” a couple times.
This is the process that takes a long time to run. When this process completes, the TSM
6.1 upgrade is, for the most part, finished. Step through any remaining screens to
complete the installer program. Several steps should be done to confirm that the upgrade
was successful, beginning with verifying that the new TSM service has been created and
started.




Don’t confuse the old TSM service “TSM Server 1” with the newly created service
“TSM Server – Server 1”. If the old TSM service remains and is not currently disabled,
then be sure to right-click and change the startup property to “Disabled”. If the new
service has not already been started, then right-click and start the service.




One way to verify that the TSM instance has been upgraded is to launch the
dsmadmc.exe CLI and login with a valid username and password. The dsmadmc
executable can be found in the server directory as pictured above.




Once you’ve logged into the server, check the Server Version line for the current release
information. It should say “Version 6, Release 1” if you’ve been successful in the
upgrade.

								
To top