Scenario 4: Preparing the database of a V5 server for upgrade

Before you extract the data from the database, you must prepare the server database by using the DSMUPGRD PREPAREDB utility. If you have multiple servers on a single system, you must repeat this task for each server.

1. Ensure that you have completed all preparation steps.
2. Log in using the root user ID on the system that has the original server. Log on with the administrator ID on a Windows system.
3. Change to the instance directory for the server that you are upgrading. The instance directory is the directory that contains the files such as dsmserv.dsk for the server.
   Important: The dsmserv.dsk file is not available in Tivoli® Storage Manager V7.1. Save a copy of the dsmserv.dsk file in case you must revert to V5.5.
4. Prepare the database. Direct the output of the process to a file for monitoring.

   

   From the instance directory for the server that you are upgrading, issue the following command to run the process in the background and direct the output to the file called prepare.out:

   nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

   

   From the instance directory for the server that you are upgrading, issue the following command to run the process in the background and direct the output to the file called prepare.out:

   nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd preparedb >prepare.out 2>&1 &

   

   From the instance directory for the server that you are upgrading, issue the following command to run the process and direct the output to the file called prepare.out:

   "c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" 
       preparedb 1>>prepare.out 2>&1

   If multiple servers exist on the system, issue the command from the instance directory for the server that you want to prepare. Specify the registry key for that server. For example, if the server is SERVER2:

   "c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" -k server2
       preparedb 1>>prepare.out 2>&1

5. Monitor the process for errors and warning messages. The final message indicates success or failure of the operation. From the instance directory for the server that you are upgrading, issue the following command to monitor the process:

   tail -f prepare.out

   Tip: On Windows systems, use the tail command or an equivalent utility with which you can monitor the contents of a file as it changes. For example, the Windows Server 2003 Resource Kit Tools includes the tail command, which can be used as shown in the preceding example.
6. Ensure that the prepare operation is completed successfully before you continue to the next step. If the prepare operation fails, you might need to restart the V5 server to fix the problem and run the prepare operation again. If the server that is being upgraded is a V5.3 or V5.4 server, you might need to restore the database by using a backup before you can restart the server to correct the problem.