Tivoli Storage Manager for Sun Solaris Administrator's Guide


Starting, Halting, and Restarting the Server


Task Required Privilege Class
Start, halt, and restart the server System or operator

Starting the Server

The following events occur when the TSM server is started:

You can start the server in console mode, as a background mode, or specify other modes as part of the dsmserv command. To start the server from the Sun Solaris window prompt, change to the /opt/tivoli/tsm/server directory, and enter the following command:

./dsmserv

TSM displays the following information when the server is started:

If TSM detects an invalid system date and time, the server is disabled, and expiration, migration, reclamation, and volume history deletion operations are not allowed. An error message (ANR0110E) is displayed and you may either change the system date if it is in error, or issue the ACCEPT DATE command to force the server to accept the current system date as valid. After the system date is resolved, you must issue the ENABLE SESSIONS command to re-enable the server for client sessions.

The date and time check occur when the server is started and once each hour thereafter. An invalid date is one that is:

Starting the Server in Other Modes

The following TSM command options specify how you can start the server in other modes as part of the dsmserv command. For example:

dsmserv option

Where option can be any one of the following:

quiet
Starts the server as a daemon program. The server runs as a background process, and does not read commands from the server console. Output messages are directed to the SERVER_CONSOLE.
Note:Before issuing this command, you must have an administrative client registered and authorized with system authority. The administrative client must be started. Otherwise, the server will run in the quiet mode and you will not be able to access the server.

-o filename
Specifies an explicit options file name when running more than one server.

Defining Environment Variables

If you want to run the TSM server from a directory other than the default directory or to run multiple servers, you may have to define environment variables.

An environment variable describes the operating environment of a process, such as the home directory or the terminal in use. It provides the path that the server requires to find and create files.

For example, to define the DSMSERV_DIR environment variable to point to the directory so that the server can find various files, such as dsmreg.lic or the message file (dsmameng.txt) enter:

     export DSMSERV_DIR=/opt/tivoli/tsm/server/bin

You can also define an environment variable to point to the server options file. For example, to define the DSMSERV_CONFIG environment variable to point to the server options file, enter:

     export DSMSERV_CONFIG=/opt/myserver/bin/filename.opt

where filename is the name you assigned your server options file (dsmserv.opt).

Running Multiple Servers on a Single Machine

To have multiple servers running on a single machine, issue the DSMSERV FORMAT command from different directories to create multiple pairs of recovery log and database files. Do not attempt to install the server executable files in more than one directory.

The following procedure shows how you can set up an additional TSM server:

  1. Determine the directory where you want the server files created, for example: /opt/myserver, and create that directory.
    	   mkdir /opt/myserver
    
  2. Copy the dsmserv.opt file to your directory (myserver).
    	   cp /opt/tivoli/tsm/server/bin/dsmserv.opt dsmserv.opt
    

    Note:Ensure that the TCPPORT option is unique from all other TSM servers.
  3. Define your environment variables, for example:
    1. To define the DSMSERV_DIR, enter:
      	   DSMSERV_DIR=/opt/tivoli/tsm/server/bin
      	   export DSMSERV_DIR
      
    2. To define the DSMSERV_CONFIG to point to the server options file, enter:
      DSMSERV_CONFIG=/opt/myserver/bin/dsmserv.opt
      export DSMSERV_CONFIG
      
  4. Format the database and recovery log files, for example:
    	   /opt/tivoli/tsm/server/bin/dsmfmt -m -db dbvol2 5
    	   /opt/tivoli/tsm/server/bin/dsmfmt -m -log logvol2 9
    
  5. Create the database and recovery log in the desired directory for the new server, for example:
    	   /opt/tivoli/tsm/server/bin/dsmserv format 1 logvol2 1 dbvol2
    
  6. You must be in the correct subdirectory to invoke the appropriate server with the dsmserv command.

Notes:

  1. You will need additional license authorizations to run additional servers.

  2. When the server is started, it searches the current directory for the existence of the DSMSERV.DSK file. If the file is found, the names of the recovery log and database files are used for server operation. If the DSMSERV.DSK file is not found in the current directory, TSM issues an error message (ANR0212E) and server initialization stops.

Halting the Server

You can halt the server without warning if an unplanned operating system problem requires the server to be stopped.

When you halt the server, all processes are abruptly stopped and client sessions are canceled, even if they are not completed. Any in-progress transactions are rolled back when the server is restarted. When the server is halted, administrator activity is not possible.

If possible, halt the server only after current administrative and client node sessions have completed or canceled. To shut down the server without severely impacting administrative and client node activity with the server, you must:

  1. Disable the server to prevent new client node sessions from starting, as described in Disabling or Enabling Access to the Server.
  2. Query for session information to identify any existing administrative and client node sessions, as described in Displaying Information about Tivoli Storage Manager Sessions.
  3. Notify any existing administrative and client node sessions that you plan to shut down the server. The server does not provide a network notification facility; you must use external means to notify users.
  4. Cancel any existing administrative or client node sessions, as described in Canceling a Tivoli Storage Manager Session.
  5. Find out if any other processes are running, such as server migration or inventory expiration, by using the QUERY PROCESS command. If a database backup process is running, allow it to complete before halting the server. If other types of processes are running, cancel them by using the CANCEL PROCESS command.
  6. Halt the server to shut down all server operations by using the HALT command.

Note:The QUIESCE option on the HALT command is recommended only if you plan to do a database dump by using the DSMSERV DUMPDB command immediately after halting. Because TSM supports online database backup (BACKUP DB command), the DSMSERV DUMPDB command should be rarely, if ever, needed.

Restarting the Server

To start the server after it has been halted, follow the instructions in Starting the Server.

When you restart the server after it has been halted, TSM rolls back any operations that had been in process to ensure that the database remains in a consistent state.


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