Tivoli Storage Manager for Windows: Administrator's Guide
Task
| Required Privilege Class
|
Start, halt, and restart the server
| System or operator
|
The following events occur when you start or restart the TSM server:
- The server invokes the communication methods specified in the server
options file.
- Note:
- By default, TCP/IP and Named Pipes communication methods are enabled in
the server options file. To adjust the TSM communication method value
or to disable a communication method, select Edit Options File from the
Service Information panel in the TSM Console.
- If the ADREGISTER server option is set to YES, the TSM server is
registered in the Active Directory. The information published under the
server's name includes the server's communication protocol
information and its registered nodes.
- The server uses the volumes specified in the dsmserv.dsk file for
the database and recovery log to record activity. It also identifies
storage pool volumes to be used.
- The server starts a TSM server console session that is used to operate and
administer the server until administrative clients are registered to the
server.
You can start the TSM server as one of the following:
- Windows service (recommended method).
OR
- Console application.
Windows requires that all applications be closed before you log off.
As a production server, TSM must be available to clients 24 hours a
day. At many sites, it is a security exposure to leave an administrator
ID logged on at an unattended computer. The solution is to run the
server as a Windows service.
You can start the server as a console application during configuration, or
when you use it in a test environment. When starting the server as a
console application, TSM provides a special administrator user ID named
SERVER_CONSOLE. All server messages are displayed directly on the
screen. The console can be useful when debugging start-up
problems.
When TSM is installed, a database and recovery log is created. Only
one server at a time can access a particular database and recovery log.
If you have installed a single TSM server on a computer and start it as a
console application, you cannot start the server as a service until you have
first stopped the console application. Similarly, if you start the
server as a Windows service, you must stop the server before you can
successfully start it as a console application.
If you have more than one TSM server installed and configured on a
computer, you can run multiple servers because each server has its own
database and recovery log. However, multiple servers cannot use the
same device because possible data loss may occur.
Because the TSM server can issue a number of requests that require
action, it is important to monitor server activity with the administrative
client using the console monitor.
To start the console monitor, do the following:
- Double-click the TSM Console icon on the desktop.
- Expand the tree until the TSM server you want to work with is
displayed. Expand the server, and then expand the Reports
tree under the selected server.
- Select Monitor, and then Start.
To start the TSM server as a Windows service, do the
following:
- Double-click the TSM Console icon on the desktop.
- Expand the tree until the TSM server you want to work with is
displayed. Expand the server, and then expand the Reports
tree under the selected server.
- Select Service Information.
- Select the server in the right pane.
- Click on Start.
At this time you can also set up the TSM server start mode and
options by doing the following:
- Double-click the TSM Console icon on the desktop.
- Expand the tree until the TSM server you want to work with is
displayed. Expand the server, and then expand the Reports
tree under the selected server.
- Select Service Information.
- Select the server in the right pane.
- Click Properties...
- Select the Automatic radio button.
- Select the Log on as account information as appropriate.
The default selection is the System account.
- Check the Log output to file check box using the default
console.log file name or you can specify another file name.
To view start and stop completion messages that are logged in the Windows
Application log, you can use the Windows Event Viewer in Administrative
Tools.
If you plan to use the ADSMSCSI device driver, you may also need to start
the driver at this time. For more information, see Starting and Stopping the Tivoli Storage Manager Device Driver (ADSMSCSI).
To start the server console from the command line prompt, change to the
directory where the server is installed. An example would be:
c:\program files\tivoli\tsm\server.
Enter:
dsmserv
TSM displays the following information when the server is started:
- Product licensing and copyright information
- Processing information about the server options file
- Communication protocol information
- Database and recovery log information
- Storage pool volume information
- Server generation date
- Progress messages and any errors encountered during server initialization
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 complete. Any in-progress
transactions are rolled back when the server is restarted.
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:
- Disable the server to prevent new client node sessions from starting by
issuing the DISABLE SESSIONS command. This command does not cancel
sessions currently in progress or system processes like migration and
reclamation.
- 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.
- Cancel any existing administrative or client node sessions by issuing the
CANCEL SESSION command and the associated session number. To obtain
session numbers and determine if any sessions are running, use the QUERY
SESSION command. If a session if running, a table will appear showing
the session number on the far left side of the screen.
- 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.
- Note:
- If the process you want to cancel is currently waiting for a tape volume to
be mounted (for example, a process initiated by EXPORT, IMPORT, or MOVE DATA
commands), the mount request is automatically cancelled. If a volume
associated with the process is currently being mounted by an
automated library, the cancel may not take effect until the mount
is complete.
- Halt the server to shut down all server operations by using the HALT
command.
To stop the TSM Server from the TSM Console, complete the following
steps:
- Double-click the TSM Console icon on the desktop.
- Expand the tree until the TSM server you want to work with is
displayed.
- Expand Reports.
- Click on Service Information.
- Select the server, and click on Stop.
- 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.
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]