Tivoli Header
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 Tivoli Storage
Manager server:
- The server invokes the communication methods specified in the server
options file.
- 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 Tivoli Storage Manager server console session that is
used to operate and administer the server until administrative clients are
registered to the server.
- Uses the STANDARD policy that is shipped with Tivoli Storage
Manager.
You can start the server in console mode, in background mode, or specify
other modes as part of the dsmserv command.
To start the server from the console, complete the following steps:
- Change to the /opt/adsmserv/bin directory from an HP-UX
session.
Enter:
cd /opt/adsmserv/bin
- Start the server.
Enter:
./dsmserv
Tivoli Storage Manager 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
If Tivoli Storage Manager 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 can be one of the following:
- Earlier than the server installation date and time
- More than one hour earlier than the last time the date was checked
- More than 30 days later than the last time the date was checked
You may choose to run the server in the background. When the server
runs in the background, you control the server through your administrative
client.
- Attention:
- Before running the server in the background, ensure the following conditions
exist:
- An administrative node has been registered and granted system
authority. See Registering Administrators.
- The administrative client options file has been updated with the correct
SERVERNAME and TCPPORT options.
- The administrative client can access the Tivoli Storage Manager
server.
If you do not follow these steps, you cannot control the server.
When this occurs, you can only stop the server by canceling the process, using
the process number displayed at startup. You may not be able to take
down the server cleanly without this process number.
To start the server running in the background, enter the following:
nohup dsmserv quiet &
You can check your directory for the output created in the nohup.out
file to determine if the server has started. This file can grow
considerably over time.
The following Tivoli Storage Manager 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.
- options filename
- Specifies an explicit options file name when running more than one
server.
If you want to run the Tivoli Storage Manager 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/adsmserv/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=/users/myserver/filename.opt
where filename is the name you assigned your server options
file (dsmserv.opt).
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.
- Note:
- Each Tivoli Storage Manager server requires approximately 100 kernel
semaphores. If you wish to run more than one Tivoli Storage Manager
server, you may need to increase the number of semaphores in the kernel
configuration parameter semmns. You may increase this
parameter by using System Administration Manager (SAM), and selecting the
Kernel Configuration option. Refer to Quick Start for more
information.
The following example shows how you can set up an additional Tivoli Storage
Manager server:
- Determine the directory where you want the server files created, for
example: /users/myserver.
- Change to the newly created directory, for example:
cd /users/myserver
- Copy the dsmserv.opt file to your directory, for example:
cp /opt/adsmserv/bin/dsmserv.opt dsmserv.opt
- Note:
- Ensure that the TCPPORT option in the dsmserv.opt file is unique from
all other Tivoli Storage Manager servers.
- Define your environment variables, for example:
- To define the DSMSERV_DIR, enter:
DSMSERV_DIR=/opt/adsmserv/bin
export DSMSERV_DIR
- To define the DSMSERV_CONFIG to point to the server options file,
enter:
DSMSERV_CONFIG=/users/myserver/dsmserv.opt
export DSMSERV_CONFIG
- Format the database and recovery log files, for example:
/opt/adsmserv/bin/dsmfmt -m -db dbvol2 5
/opt/adsmserv/bin/dsmfmt -m -log logvol2 9
- Create the database and recovery log in the desired directory for the new
server, for example:
/opt/adsmserv/bin/dsmserv format 1 logvol2 1 dbvol2
- You must be in the correct subdirectory to start the appropriate server
with the dsmserv command. Enter:
dsmserv
Notes:
- You will need additional license authorizations to run additional
servers. See Registering Licensed Features for more information.
- When you are running multiple servers and have more than one server
options file, you can specify which options file to use by starting the server
with the following command:
dsmserv -options filename
where filename is the name of the server options file.
- 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, an error message (ANR0212E) is issued and server initialization
stops.
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.
- 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 Tivoli Storage Manager 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 ]