Starting and stopping the storage agent, Automating the storage agent startup, Manually starting and stopping the storage agent – IBM TIVOLI SC32-0129-00 User Manual
Page 61: Appendix, Administration, Configuration, Reference, Starting, Stopping, Storage
Appendix
A.
Administration
and
Configuration
Reference
This
section
provides
information
about
administering,
monitoring,
tuning,
and
connecting
the
storage
agent.
Starting
and
Stopping
the
Storage
Agent
The
storage
agent
can
be
configured
to
start
automatically
upon
system
reboot.
It
can
also
be
started
and
stopped
manually.
The
following
is
a
description
of
these
tasks.
Automating
the
Storage
Agent
Startup
The
storage
agent
is
configured
to
start
automatically
at
the
time
of
installation.
An
entry
is
made
to
the
inittab
to
enable
automatic
start
up.
The
storage
agent
automatically
restarts
and
runs
in
the
background
when
the
operating
system
is
rebooted.
During
the
installation
process,
the
etc/inittab
is
updated
with
the
following
command
to
enable
automatic
startup:
mkitab
autostgagnt:2:once:"/usr/tivoli/tsm/StorageAgent/bin/rc.tsmstgagnt
>/dev/console
2>&1
#Start
the
Tivoli
Storage
Manager
storage
agent"
If
you
decide
that
you
do
not
want
the
storage
agent
to
start
automatically,
you
can
issue
the
following
command
to
remove
the
statement
from
the
/etc/inittab.
rmitab
"autostgagnt"
Manually
Starting
and
Stopping
the
Storage
Agent
Start
the
storage
agent
by
accessing
the
storage
agent
directory
and
issue
the
following
command:
dsmsta
Stop
the
storage
agent
by
typing
the
following
command
at
the
command
line
prompt:
halt
Note
that
you
can
also
use
an
administrative
client
to
issue
commands
supported
by
the
storage
agent.
In
most
cases
it
is
not
necessary
to
halt
and
restart
a
LAN-free
storage
agent
to
pick
up
changes
from
the
data
manager
server.
However,
restarting
the
storage
agent
may
be
necessary
if
an
attempt
was
made
to
change
storage
pool,
library,
device
class,
or
drive
information
while
LAN-free
data
movement
was
in
process.
The
effects
on
LAN-free
storage
pools
resulting
from
such
an
attempted
change
are
not
critical
enough
to
create
serious
problems.
The
storage
agent
keeps
a
list
of
storage
pools,
libraries,
and
device
classes
in
memory
to
determine
potential
LAN-free
destinations.
Target
volume
selection
occurs
on
the
data
manager
server.
Certain
storage
pool
attributes
can
result
in
failed
requests
rather
than
the
desired
LAN
failover
by
the
storage
agent.
If
the
storage
agent
accurately
identifies
a
LAN-free
destination,
the
LAN-free
operation
will
most
likely
be
successful.
©
Copyright
IBM
Corp.
2000,
2007
43