2.2 Starting Daemons

Daemons must be running on the Management Server and Managed Servers.

If for whatever reason daemons stop, the daemons must restarted on each server.

# /opt/swstorage/bin/startacm

Note

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

Confirm that /var/tmp directory as a work directory exists.
If the message below is displayed when trying to start the daemon, then stop it and start it again:
"Symfoware/RDB for AdvancedCopy Manager failed to start !!(version missing)"

If starting daemon fails, confirm that IP address and name of the local server in /etc/hosts file are validate.

When the Management Server or Managed Server is in a clustered system, start up the daemon(s) from the clustered system. For the start procedure, refer to the relevant cluster software manual.

To start the daemon separately

To start the daemon separately on AdvancedCopy Manager transactions in a clustered system, follow the steps described below:

Communication daemon:
You must start the daemon for each AdvancedCopy Manager transaction (including local transactions) using the following procedure for the respective transactions.
1. Execute the following commands depending on the communication daemon to be operated and check if it is activated. If it is activated, step 2 and subsequent steps are not necessary to be performed.
  1. When the communication daemon is in the global zone and operation uses Oracle Solaris Zones Support Function.
```
ps -z globale -f | grep stgxfws
```
  2. When the target communication daemon is other than "a" described above.
```
# ps -ef | grep stgxfws
```
  Confirm the command execution. If the strings are displayed as below, the daemon(s) has already been activated.
```
/opt/FJSVswstf/bin/stgxfws <logical-node-name>
```
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, refer to "8.5.1 Starting and stopping the communication daemon".
For daemons other than the communication daemon:
1. For environment variable SWSTGNODE, specify the name of the logical node on which the transaction is to be performed.
2. Refer to the following sections to start the daemon.
  - RMI daemon: "8.5.2 Starting and stopping the RMI daemon"
  - RDB daemon: "8.5.3 Starting and stopping the RDB daemon"