This section explains how to customize the Linux-version PRIMECLSTER.
The primary node is an active node in a userApplication performing Storage Management Server transactions, and the secondary node is the standby node in the same group.
The secondary node A is the node which creates the environment of Storage Management Server transactions and Storage Server transactions first in the secondary nodes in this userApplication. The secondary node B is the remaining standby node and is not the active node in this userApplication.
The customizing work of the primary node and secondary node A is executed as a 1:1 standby system, mutual standby system, and n:1 standby system.
The customizing work of the primary node, secondary node A and secondary node B is executed as a cascade topology system and priority transfer system.
Example:
When creating a cascade with three sets of nodes, one set is a primary node, one set is the secondary node A, and one set is the secondary node B. When creating a cascade with four sets of nodes, one set is a primary node, one set is the secondary node A, and two other sets are the secondary node B.
