Daemons must be running on the 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.
If starting daemon fails, confirm that IP address and name of the local server in /etc/hosts file are validate.
When the 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:
You must start the daemon for each AdvancedCopy Manager transaction (including local transactions) using the following procedure for the respective transactions.
Execute the following command.
# ps -ef | grep stgxfws
Confirm that the command execution does not display the following strings. If the strings are displayed, the daemon(s) has already started.
/opt/FJSVswstf/bin/stgxfws <logical-node-name>For environment variable SWSTGNODE, specify the name of the logical node on which the transaction is to be performed.
Start the communication daemon.
For the startup command, refer to "8.5.1 Starting and stopping the communication daemon".