IBM Tivoli Storage Manager, Version 7.1

Scenario 4: Moving the server database over a network

Move the database by starting the insertion process for the V7.1 server to accept the server database. Then, start the extraction process for the V5 server to extract and send the database.

Before you begin

Ensure that the V5 server and the V7.1 server are not running.

Procedure

  1. Verify that there is a good network connection between the two systems.
  2. Start the insertion process on the V7.1 server to accept the database. To monitor the process, direct the output of the process to a file. For example, start the server, allowing 60 minutes (the default time) for the other server to contact the V7.1 server and directing the process output to insert.out, by using this command:

    AIX operating systems HP-UX operating systems Linux operating systems Oracle Solaris operating systems
    nohup /opt/tivoli/tsm/server/bin/dsmserv insertdb \
    sesswait=60 >insert.out 2>&1 &
    Windows operating systems
    "c:\Program Files\Tivoli\TSM\server\dsmserv" insertdb 
    sesswait=60 1>>insert.out 2>&1
    The server starts and waits up to 60 minutes to be contacted by the original server. Some time might pass during which no messages are issued. During this time, DB2® operations are running in the background. Optional: To verify that operations are continuing as expected, monitor the CPU and I/O usage for the server process and the corresponding DB2 process.
  3. Monitor the output of the DSMSERV INSERTDB process. Verify that the DSMSERV INSERTDB process has issued the following message before continuing to the next step:
    ANR1336I INSERTDB: Ready for connections from the source server
    Issue the following command to monitor the process output in the insert.out file:
    tail -f insert.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.
  4. Start the extraction from the original server. Specify the TCP/IP address and port for the V7.1 server. Direct the output of the process to a file for monitoring. For example, enter the following command on one line:

    AIX operating systems
    nohup /usr/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \
    hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &
    HP-UX operating systems Linux operating systems Oracle Solaris operating systems
    nohup /opt/tivoli/tsm/upgrade/bin/dsmupgrd extractdb \
    hladdress=127.0.0.1 lladdress=1500 >extract.out 2>&1 &
    Windows operating systems
    "c:\Program Files\Tivoli\TSM\upgrade\dsmupgrd" extractdb hladdress=127.0.0.1
      lladdress=1500 1>>extract.out 2>&1
  5. Monitor the processes for errors and warning messages, and for items that you might need to act on. From the instance directory for the server that you are upgrading, issue the following command to monitor the extraction process:
    tail -f extract.out
    The length of time that the process runs depends on the size of the database, the hardware being used, and the network.
  6. Examine the process outputs for the extraction and insertion processes to find the messages that indicate the success or failure of the operations.
    Process Success message Failure message
    Extraction ANR1382I EXTRACTDB: Process 1, database extract, has completed. ANR1396E EXTRACTDB: Process 1, database extract, has completed with errors.
    Insertion ANR1395I INSERTDB: Process 1, database insert, has completed. ANR1396E INSERTDB: Process 1, database insert, has completed with errors.


Feedback