Quick Start


Migrating from ADSM

You can install TSM over previous versions of ADSM. Follow the instructions in this section to prevent loss of data from your system if you are migrating from a previous version.


Figure AB0CT107 not displayed.

Migration will not normally create new database, recovery log, and storage pool volumes. However, if the dsmserv.dsk file is not in the /opt/tivoli/tsm/server/bin or /opt/adsmserv/bin directories, the install creates the following volumes in the directory:

  • Database volume (db.dsm)

  • Recovery log volume (log.dsm)

  • Storage pool volumes (sbkup00.dsm, and sarch00.dsm)

To use your existing database, recovery log, and storage pool volumes, ensure that a copy of the dsmserv.dsk file is in /opt/tivoli/tsm/server/bin or /opt/adsmserv/bin and the filesystem is mounted before you do a migrate install.

To migrate to Tivoli Storage Manager do the following:

  1. Back up the full ADSM Version 3.1 database. For example, if you have a tape device class named TAPECLASS, do a full backup of your database by issuing the following command:

    Figure AB0CT124 not displayed.

    	backup db type=full devclass=tapeclass
    

  2. Store the output volumes in a safe location. You will need these volumes if you want to return to the previous version of the server.

  3. Stop the server if it is running by entering:

    Figure AB0CT124 not displayed.

    halt
    

  4. Remove the previous version server software by entering:
    +--------------------------------------------------------------------------------+
    | swremove ADSM                                                                  |
    +--------------------------------------------------------------------------------+

  5. Install the TSM software. See Installing Tivoli Storage Manager.

  6. Start the server.

    Specify the UPGRADEDB parameter with the DSMSERV command if you are starting TSM over a database that was written by a previous version of ADSM:

    +--------------------------------------------------------------------------------+
    | dsmserv -upgradedb                                                             |
    +--------------------------------------------------------------------------------+
    Note:You need to issue this command only one time. Therefore, do not include the UPGRADEDB in any automated programs that start your server.

  7. Reregister your licenses. See Registering Licenses.

    Notes:

    1. Until the new version is installed and any required licenses are re-registered (step 7), clients will not be able to connect to the server.

    2. The TIVsm.license fileset is required to register licenses. This fileset is installed when you install the TSM server package.

  8. To use the administrative web interface, halt the TSM server and issue this command to load the definition file:
    +--------------------------------------------------------------------------------+
    | dsmserv runfile dsmserv.idl                                                    |
    +--------------------------------------------------------------------------------+

    Notes:

    1. You must have at least 4MB of available database to run the DSMSERV RUNFILE DSMSERV.IDL command.

    2. Your browser must have Java 1.1.6 support.

    3. To use the administrative web interface, the fileset TIVsm.server_webadmin must first be installed. This subcomponent includes the dsmserv.idl file and all of the image files needed to use the administrative web interface. This fileset is installed with the server if the entire server program is installed ('swinstall TIVsm').

    4. You must also configure the HTTP communication method in your dsmserv.opt server options file to use this interface.
      +--------------------------------------------------------------------------------+
      |commmethod          http                                                        |
      |   httpport         1580                                                        |
      +--------------------------------------------------------------------------------+

  9. Tivoli Storage Manager is shipped with sample command scripts that can be loaded into the database and run from an TSM administrative client, administrative web interface, or server console. They can also be included in TSM administrative command schedules. The sample scripts, in scripts.smp, are primarily SELECT queries, but also include scripts that define volumes for and extend the database and recovery log and that backup storage pools.

    To load the sample scripts into the TSM database, issue the following command:

    +--------------------------------------------------------------------------------+
    |dsmserv runfile scripts.smp                                                     |
    +--------------------------------------------------------------------------------+
    Note:The sample scripts may have been loaded when ADSM Version 3.1 was installed. Loading the sample scripts again at this point will overlay any existing scripts of the same name and any modifications made to those scripts will be lost.

  10. Restart the server. See Starting and Stopping the Server.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]