mercoledì 6 novembre 2013

TSM: Upgrading server from V5 to V6.3



Modifying the server before the upgrade
From a Tivoli® Storage Manager administrative command line, issue the command:
convert ussfilespace
Important: Do not skip this step. If your database has the problem and you do not run this command now, the DSMUPGRD PREPAREDB utility fails when you run it. You must then restart the V5 server and run the CONVERT USSFILESPACE command before continuing with the upgrade process.

For each sequential-access storage pool, set the REUSEDELAY parameter to the number of days during which you want to be able to revert to the original server, if that becomes necessary.

ReuseDELAY 5
For example, if you want to be able to revert to the original server for up to 30 days after upgrading to V6.3, set the REUSEDELAY parameter to 31 days.

For each copy storage pool, set the RECLAIM parameter to 100 (meaning 100%).

If you typically use a DELETE VOLHISTORY command to delete database backups, ensure that the command does not delete database backups for at least the same number of days that you set for the REUSEDELAY period for sequential-access storage pools.
DELETE VOLHISTORY 5
For important clients that use the server, check that the value for the schedlogretention client option is set to retain the client schedule log for a long enough time

Disabilitare le sessioni client e server
disable sessions client
disable sessions server
qsess
cancel sess all
q proc
cancel proc all
q mount
dismount volume
Checkout all volumes without verify label

Copia del DB -LOG e server 1
Deleting or renaming the NODELOCK file
  1. Scenario 4: Installing the upgrade utilities on the system where the V5 server is located.

Download upgrade 5.5.x , must be the same version of TSM srv
Run executable package
Do not install the utilities in the same directory as the original server that is to be upgraded. Install the utilities package in its own directory.
C:\Program Files\Tivoli\TSM\upgrade
  1. Upgrading the server, by using one of the following methods:

The systems must have one of the following protocols enabled. Ensure that the port that the protocol uses is not blocked by a firewall.
Secure shell (SSH). Ensure that the port is set to the default value, 22.
Also ensure that the SSH daemon service has access rights for connecting to the system by using localhost.
Remote shell (RSH).
Remote Execution Protocol (REXEC).
Windows server message block (SMB)

SMB is the interface used by File and Print Sharing (also known as CIFS). To use the SMB protocol, you must ensure that File and Print Sharing is enabled, and that port 445 is not blocked by your firewall. If you are running on Windows Server 2008 or Windows Vista, you might also need to disable User Account Control (at least while running this wizard). If you choose not to disable User Account Control, you must ensure that one of the other protocols is configured to allow the wizard to run.
You must be able to log on to the system using a protocol that is enabled on the system, using either the user ID that you created for the server instance, or some other user ID that exists on the system. When using the wizard, you must provide the user ID and password to access the system.

TSM6.3.x

Installare 6.3.x
Creo le nuove cartelle per la nuova istanza
C:\TSMDATA\DB
E:\TSMDATA\Actlog
E:\TSMDATA\Arclog


Se possibile eseguire snapshot

Con la wizard inizalizzare una...

Start the upgrade wizard, dsmupgdx, from the V6.3 server installation directory.

Start the upgrade wizard, dsmupgdx, from the V6.3 server installation directory.
c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"

    The following tasks are completed after the upgrade:


//////

UPGRADE FROM 5.X TO 6.3

The major steps in the upgrade process from V5 to V6.3 are as follows:

Plan system hardware and software, and estimate the upgrade time.

Use information about the Tivoli Storage Manager upgrade process together with operational requirements for your existing servers to decide how and when to perform the upgrade.
Tip: If you are introducing new hardware or changes in the storage system infrastructure, plan the zoning for the storage area network (SAN). Allow time to create device statements and paths, and to check in tape volumes following the upgrade. For IBM® tape devices, no multipathing driver is available for tape drives that are distributed over more than one adapter. Use zoning and device definitions to balance the workload.
Back up the Tivoli Storage Manager server database and configuration files.
Optional: Verify your system environment by running the prerequisite checker. Make any changes that are required before proceeding with the installation.
Install the server code. Installation tasks include the following:
  • Installing the new server code, which includes the server and its database manager program. Configure a user ID for the new server instance.
  • Installing the upgrade utilities package on the system where the existing V5 server is located.
  • Upgrade the database. This task includes preparing the database, and then moving the database. Use the upgrade utilities or the upgrade wizard to complete these tasks.

The upgrade utilities or upgrade wizard extracts data from an existing database and inserts the data into a new V6.3 database. Media or the network can be used for the data movement.

As a database is moved into the new database structure, the validity of the data is checked against constraints that are enforced in the new database. The upgrade tools automatically correct some errors in the database. Other errors might require manual correction.

If you use the wizard, you are guided to complete the upgrade steps in the correct order. If you are performing the upgrade manually by using utilities from a command line, follow the procedure carefully.
Verify the upgrade by running basic operations and querying information about the system to confirm that all information transferred correctly.
Moving the server to a new system when upgrading to the V6.3 server gives you more flexibility in how to perform the upgrade, but with some additional costs.
. You can use the upgrade wizard to run the utilities with guidance.
The DSMUPGRD upgrade utilities
The upgrade utilities prepare and extract data from a version 5.3, 5.4, or 5.5 server database for insertion into an empty version 6.3 server database.

Verifica HW & SW


Than install su new platform Running the prerequisite checker
prereqcheck.exe

DB
Ideally, use multiple directories for database space and
locate them across as many physical devices or logical unit numbers (LUNs) as
there are directories.


Su TSM origine v5.5
Halt Tsm server
dsmupgrd querydb Verifica la situazione attuale del DB

A command must be run on the server to prevent one type of problem during the upgrade process.
From Command Line
convert ussfilespace
This command fixes a problem that might exist in older Tivoli Storage Manager databases. If the problem does not exist in your database, the command completes quickly and you might see error ANR2034E. This error can be ignored


Per poter ritornare al server iniziale
For each sequential-access storage pool, set the REUSEDELAY
if you want to be able to revert to the original server for up to
30 days after upgrading to V6.3, set the REUSEDELAY parameter to 3 days.

For each copy storage pool, set the RECLAIM parameter to 100

If you typically use a DELETE VOLHISTORY today-3 command to delete database
backups, ensure that the command does not delete database backups for at
least the same number of days that you set for the REUSEDELAY period for

For important clients that use the server, check that the value for the
schedlogretention client option is set to retain the client schedule log for a
long enough time.

disable sessions client
disable sessions server
Back up primary storage pools to copy storage pools by using the BACKUP STGPOOL command
query session
cancel session all
q mount
dismount volume (volume name)


Stop Tsm server
Copia Cartella DB -Log e la cartella Server1
delete or rename the NODELOCK file before starting theupgrade process

Installing the upgrade utilities 5.5.6.0-TIV-TSMUPG-Windows in
C:\Program Files\Tivoli\TSM\upgrade


The V6.3 server must be installed, and directories and the user ID must be created before starting the upgrade wizard
When the server is started as a Windows service, this is the account that the service will log on to. The user account must have administrative authority on the system.
Creare prima account e poi installare tsm6.3.1.0
C:\Users\Administrator>net user Tivoli /add
C:\Users\Administrator>net localgroup Administrators tivoli /add
C:\Users\Administrator>net localgroup DB2ADMNS Administrators /add
C:\Users\Administrator>net localgroup DB2USERS Administrators /add


Log in to your system, using the new user ID and password. Tivoli Logitech550

The system must have one of the following protocols enabled. Ensure
that the port that the protocol uses is not blocked by a firewall.
Secure shell (SSH). Ensure that the port is set to the default value,
22. Also ensure that the SSH daemon service has access rights for
connecting to the system by using localhost.
Remote shell (RSH).
Remote Execution Protocol (REXEC).
Windows server message block (SMB)
SMB is the interface used by File and Prin

Open a new Command Prompt window, and issue the command:
"c:\Program Files\Tivoli\TSM\server\dsmupgdx.exe"

Taking the first steps after upgrade

- Verify License compliance
REGISTER LICENSE file=tsmee.lic
Verificare la devclass pe copia del DB ed eventualmente crearla

  • For all disk space that was used for storage pools (device types of FILE or DISK) by the V5 server, verify that the user ID that owns the upgraded server instance has ownership or read/write permission. Also ensure that the instance user ID has access to all devices that are used, including raw logical devices
  • Before starting the server for production use, set server options to control when reorganization runs. If you plan to use deduplication, ensure that the option to run index reorganization is enabled

On new TSM srv 6.3
Verfy Options file
If you plan to use deduplication, enable the ALLOWREORGINDEX server option.
Add the following option and value to the server options file:
allowreorgindex yes
Set the time for reorganization to start by using the REORGBEGINTIME server option. Specify the time using the 24-hour system. For example, to set the
start time for reorganization as 8:30 p.m., specify the following option and value in the server options file:
reorgbegintime 20:30
Set the interval during which the server can start reorganization. Forexample, to specify that the server can start reorganization for 4 hours after the time set by the REORGBEGINTIME server option, specify the following
option and value in the server options file:
reorgduration 4

Changing the host name for a server running on Windows pag. 299 upgrade 6.3

Removing GSKit Version 7 after upgrading to Tivoli Storage ManagerV6.3 pag. 302