ETERNUS SF AdvancedCopy Manager Operator's Guide 13.0 -Solaris-

Chapter 2 Starting and Stopping Daemons

This chapter explains how to activate and stop different daemons provided by AdvancedCopy Manager.

For more information on how to activate and stop the daemons described in this chapter, see "Start/Stop Daemon Commands."

2.1 Daemons that Configure AdvancedCopy Manager

Manager of AdvancedCopy Manager is configured with the following daemons:

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

Daemon type	Description
The communication daemon	Communicates with the Storage server
The RMI daemon	Manages the GUI display
The RDB daemon	Accesses the repository
The authentication daemon	Manages the authentication feature

Agent of AdvancedCopy Manager is configured with the following daemons:

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

Daemon type	Description
The communication daemon	Communicates with the Storage management server and other storage servers

When the storage management server is in cluster operation, the following daemons compose storage management server transactions:

[Table 2.3 Types of daemons composing storage management server transactions]

Daemon type	Description
Transaction-intended communication daemon	Daemon for communication with storage servers
RMI daemon	Daemon for controlling GUI windows
RDB daemon	Daemon for accessing the repository
Authentication daemon	Daemon for controlling the authentication mechanism

The following daemon composes a AdvancedCopy Manager agent:

[Table 2.4 Type of daemon composing storage server transactions]

Daemon type	Description
Transaction-intended communication daemon	Daemon handling communication with storage management servers and other storage servers

The following daemon cannot compose a storage management server transaction or storage server transaction:

Communication daemon (local daemon)

2.2 Starting a Daemons

Daemons must be activated on the Storage management server, Storage server, and SP server.

Normally, they are automatically activated. However, if activation fails or the daemon is stopped, activate the daemon on each server by executing the following command:

# /opt/swstorage/bin/startacm

Before executing the startacm command, confirm that the SWSTGNODE environment variable is not defined.
Information about starting the daemon for the cluster operation can be seen in Chapter 6, "Starting and Stopping a Daemon," in the AdvancedCopy Manager Operator's Guide for cluster environment.

When the storage management server or storage server is in cluster operation, start up the daemon(s) from the cluster system. For the start procedure, see the relevant cluster software manual.

To start the daemon separately of certain AdvancedCopy Manager transactions for some reason, follow the steps described below.

As for the communication daemon:

You must start the daemon for each AdvancedCopy Manager transaction (including storage local transactions). Take the following steps for the respective transactions.
1. Execute the following command on the command line:
  # ps -elf | grep stgxfws
  Confirm that command execution does not display:
  /opt/FJSVswstf/bin/stgxfws logical-node-name
  If the message above is displayed, the daemon has already started.
2. For environment variable SWSTGNODE, specify the name of the logical node on which the transaction is to be performed.
3. Start the communication daemon.
  
  For the startup command, see "Start/Stop Daemon Commands" in this manual.
As for a daemon other than the communication daemon:

Start the daemon by referencing "Start/Stop Daemon Commands" in this manual. However, specify the logical node name in environment variable SWSTGNODE, and then execute the daemon startup command.

2.3 Stopping a Daemons

Stop daemons from the Storage management server and the Storage server. Normally, they are automatically stopped when the system stops.

To stop a daemon on a server, execute the following command on the server:

# /opt/swstorage/bin/stopacm

Before executing the stopadacm command, confirm that the SWSTGNODE environment variable is not defined.
Information about stopping the daemon for the cluster operation can be seen in Chapter 6, "Starting and Stopping a Daemon," in the AdvancedCopy Manager Operator's Guide for cluster environment.

When the storage management server or storage server is in cluster operation, stop the daemon(s) from the cluster system. For the stop procedure, see the relevant cluster software manual.

To stop the daemon separately of certain AdvancedCopy Manager transactions for some reason, follow the steps described below.

As for the communication daemon:

You must stop the daemon in each AdvancedCopy Manager transaction (including storage local transactions). Take the following steps for the respective transactions.
1. Execute the following command on the command line:
  # ps -elf | grep stgxfws
  Confirm that command execution displays:
  /opt/FJSVswstf/bin/stgxfws logical-node-name
  If the message above is not displayed, the daemon has already stopped.
2. For environment variable SWSTGNODE, specify the name of the logical node on which the transaction is to be performed.
3. Stop the communication daemon.
  
  For the stop command, see "Start/Stop Daemon Commands" in this manual.

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

As for a daemon other than the communication daemon:

Stop the daemon by referencing "Start/Stop Daemon Commands" in this manual. However, specify the logical node name in environment variable SWSTGNODE, and then execute the daemon stop command.

Contents Index