Note the following general points on cluster operation:
Do not make a SWSTGNODE registration that configures an environment variable to the entire system.
AdvancedCopy Manager does not monitor daemons of an active server. If the daemon of a transaction stops for some reason, AdvancedCopy Manager does not automatically restart it, so you must restart it manually. Moreover, the stopping of an active server daemon of AdvancedCopy Manager does not cause the cluster to fail over.
For details on the daemons of AdvancedCopy Manager active servers and how to start these daemons, see "Chapter 2 Starting and Stopping Daemons".
For a Storage Server daemon (or Storage Management Server daemon) operating together with a daemon in a scalable operation, note the following points that do not apply to regular operation or cluster operation:
For a Storage Management Server transaction, note that the logical IP address you specify in the cluster setup command must be the logical IP address of the Storage Management Server transaction. Specifying the physical IP address or logical IP address of a server in scalable operation will result in incorrect setting.
Do not register any cluster resource of a transaction in scalable operation as a cluster resource of a Storage Server transaction (Storage Management Server transaction).
On the input screen shown in "Registering a new Storage Server" in the "ETERNUS SF AdvancedCopy Manager GUI User's Guide", enter the logical IP of the Storage Server transaction in the IP address field. Entering a physical IP or logical IP of a server in scalable operation will result in incorrect setting.
On the input screen shown in "Registering a new Storage Server" in the "ETERNUS SF AdvancedCopy Manager GUI User's Guide", enter the port number that was registered when the Storage Server transaction was customized and dedicated to the active server communication daemon (stgxfws_logical-node-name) in the port number field. Entering a port number other than that dedicated to the active server communication daemon will result in incorrect setting.
Refer to "Device management" in the "ETERNUS SF AdvancedCopy Manager GUI User's Guide", add a transaction volume and backup volume for the transaction in scalable operation to be placed in backup/replication operation
You can make a backup or replication on a node operating a Storage Server transaction (Storage Management Server transaction) if it is the active node. You cannot make a backup or replication on any standby node of a Storage Server transaction (Storage Management Server transaction).
If a transaction (in scalable operation) running on a node operating a Storage Server transaction (Storage Management Server transaction) stops for some reason, you must manually switch the Storage Server transaction (Storage Management Server transaction) over to a node running in scalable operation. Storage Server transactions (Storage Management Server transactions) are not linked with scalable operation transactions, thus stopping scalable operation transactions does not cause a Storage Server transaction (or Storage Management Server transaction) to fail over.
