ETERNUS SF AdvancedCopy Manager Operator's Guide for Tape Backup Option 13.0 -Microsoft(R) Windows(R) 2000/Microsoft(R) Windows Sever(TM) 2003-, -Solaris-, -HP-UX-, -Linux-, -AIX-

Contents Index

Chapter 2 Starting and Stopping Daemons

This chapter explains how to start and stop various daemons provided by Tape Backup of AdvancedCopy Manager.

2.1 Daemons that Configure Tape Backup of AdvancedCopy Manager

Manager of AdvancedCopy Manager is configured with the following daemons.

[Table 2.1 Types of daemons that configure Manager of AdvancedCopy Manager]

Agent of AdvancedCopy Manager is configured with the following daemons.

[Table 2.2 Types of daemons that configure Agent of AdvancedCopy Manager]

Storage Manager Server is configured with the following daemons, when the Storage Management Server is operated with the cluster system.

[Table 2.3 Types of daemons that configure Storage Manager Server transaction]

Storage Server is configured with the following daemons, when the Storage Management Server is operated with the cluster system.

[Table 2.4 Types of daemons that configure Storage Server transaction]

The following daemons cannot become a Storage Management Server transaction or Storage Server transaction.

• The Communication Daemon for local node

Tape Manager of AdvancedCopy Manager is configured with the following daemons.

[Table 2.5 Types of daemons that configure Tape Manager of AdvancedCopy Manager]

2.2 Starting Daemons

2.2.1 Starting daemons while the operating system is stopped state

The daemons on the Storage Management Server, Storage Server, and Tape Server are all automatically started when the operating system is started.
When the operating system is started from the stopped state, therefore, you need not intentionally start daemons.

2.2.2 Starting daemons while the operating system is active state

When you want to start a daemon if starting the daemon has failed or after you stopped the daemon intentionally, you can perform on the respective server the action explained below.

+Storage Management Server and Storage Server

For details, see "Starting and Stopping Daemons" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server and Storage Server.

+Tape Server

To start daemons, execute the following commands as the root user.

# /opt/swstorage/bin/startacm
# /etc/init.d/FJSVswstm start
# /etc/init.d/initTSM start

If you need to start the daemon on the Tape Server individually, you can start the daemon as follows.

• In the case of the Communication Daemon
  1. The following commands are executed at a command line.

     # ps -ef | grep stgxfws

     
     

     This result

     /opt/FJSVswstf/bin/stgxfws Logical-Node-Name

     What is not displayed is checked. When displayed, the daemon has already started.

  2. The logical node name which performs applicable transaction to an environment variable SWSTGNODE is set up.
  3. Start the Communication Daemon.
     For the daemon starting command, see "Starting and Stopping Daemons" in the chapter "Commands".

• In the case of daemons other than the Communication Daemon

  Please start with reference to "Starting and Stopping Daemons" in the chapter "Commands". However, a logical node name is set as an environment variable SWSTGNODE, and a daemon starting command is executed.

2.3 Stopping Daemons

Before executing the command, make sure that environment variable SWSTGNODE has not been set.

2.3.1 Stopping daemons by stopping the operating system

The daemons on the Storage Management Server, Storage Server, and Tape Server are all automatically stopped when the operating system is stopped.
When the operating system is stopped, therefore, you need not intentionally stop daemons.

2.3.2 Stopping daemons without stopping the operating system

If you want to stop a daemon without stopping the operating system, you can perform on the respective server the action explained below.

+Storage Management Server and Storage Server

For details, see "Starting and Stopping Daemons" in the "ETERNUS SF AdvancedCopy Manager Operator's Guide" for the operating system of the target Storage Management Server and Storage Server.

+Tape Server

To stop daemons, execute the following commands as the root user.

# /etc/init.d/initTSM stop
# /etc/init.d/FJSVswstm stop
# /opt/swstorage/bin/stopacm

Before executing the stopadacm command, confirm that the SWSTGNODE environment variable is not defined.

If daemons are stopped while backup or restoration is in progress, the backup or restoration terminates with an error. If necessary, restart daemons and execute the backup or restoration again.

If you need to stop the daemon on the Tape Server individually, you can stop the daemon as follows.

• In the case of the Communication Daemon
  1. The following commands are executed at a command line.

     # ps -ef | grep stgxfws

     
     

     This result

     /opt/FJSVswstf/bin/stgxfws Logical-Node-Name

     What is displayed is checked. When not displayed, the daemon has already stopped.

  2. The logical node name which performs applicable transaction to an environment variable SWSTGNODE is set up.
  3. Stop the Communication Daemon.
     For the daemon stopping command, see "Starting and Stopping Daemons" of the chapter "Commands".

     

  If you execute the command to stop the communication daemon while it is running, the command may take up to 10 seconds to complete.

• In the case of daemons other than the Communication Daemon

  Please stop with reference to "Starting and Stopping Daemons" of the chapter "Commands". However, a logical node name is set as an environment variable SWSTGNODE, and a daemon stopping command is executed.

Contents Index