Note the following general points on cluster operation:
Do not set 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, refer to "Chapter 2 Starting and Stopping Daemons".
For volumes for which to perform backup and replication, configure their device names, mount points and logical unit numbers on the ETERNUS Disk storage system so that they are the same on all the nodes making up a cluster.
For a Managed Server daemon (or 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 Management Server transaction, note that the logical IP address you specify in the cluster setup command must be the logical IP address of the Management Server transaction. Specifying the physical IP address or logical IP address of a server in scalable operation results in incorrect setting.
Do not register any cluster resource of a transaction in scalable operation as a cluster resource of a Managed Server transaction (Management Server transaction).
When specifying the Managed Server's IP address for the execution of AdvancedCopy Manager commands, specify the logical IP address for the Managed Server transactions. Specifying the physical IP address or logical IP address of a server in scalable operation results in an incorrect setting.
When specifying the Managed Server's port number for the execution of AdvancedCopy Manager commands, specify the port number for the Managed Server transaction communication daemon (the name of the stgxfws logical node). Specifying a port number besides those applicable to server transaction communication daemons results in an incorrect setting.
Add backup-use volume with the transaction volume for scalable operation transactions which operate backup and replication.
You can make a backup or replication on a node operating a Managed Server transaction (Management Server transaction) if it is the active node. You cannot make a backup or replication on any standby node of a Managed Server transaction (Management Server transaction).
If a transaction (in scalable operation) running on a node operating a Managed Server transaction (Management Server transaction) stops for some reason, you must manually switch the Managed Server transaction (Management Server transaction) over to a node running in scalable operation. The Managed Server transactions (Management Server transactions) are not linked with scalable operation transactions, thus stopping scalable operation transactions does not cause a Managed Server transaction (or Management Server transaction) to fail over.
