This section describes the range of support of PRIMECLUSTER in an AWS environment.
Number of cluster nodes: 1 to 2 nodes
Operation mode of the cluster system: 1:1 Standby operation, Mutual standby, Single-node cluster, Scalable operation (only when using Symfoware Server (Native) Hot Standby feature)
Network configurations: Instances in the cluster system must communicate with the API endpoints.
Configurations to take over volume data: Data takeover by the mirroring among servers of GDS using EBS
Error of AZ (cluster system in multiple Availability Zones)
The cyclic monitoring of the cluster interconnect detects a fault of the AZ and the service is automatically switched to the standby system.
Error of the guest OS and the cluster interconnect
The cyclic monitoring of the cluster interconnect detects a hang-up of the guest OS or an error of the cluster interconnect, and the service is automatically switched to the standby system.
Error of the disk access
By combining the volume management function of GDS, an error of the disk access can be detected (monitored by the Gds resource), and the service is automatically switched to the standby system when the disk access is disabled.
Error of the cluster application
When a resource error of the cluster application occurs, the service is automatically switched to the standby system.
Note
The snapshot of the instance can be acquired only when the OS is stopped.
The following functions for PRIMECLUSTER are not available:
GFS
GLS
GDS Snapshot
Root class and local class of GDS
Single volume of GDS, and disk groups of GDS other than the netmirror type (mirror, stripe, concatenation, and switch)
Easy Design and Configuration Feature
The console cannot be used in the instance in an AWS environment. Do not set the single user mode.
AWS features that involve node operations (Auto Scaling, Auto Recovery, etc.) are not available.
When using the asynchronous forcible stop method, a shared file system service cannot be used.
