This section describes the range of support of PRIMECLUSTER in an Azure 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: The virtual machines 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 Azure managed disks
Error of AZ (cluster system in multiple Availability Zones)
The cyclic monitoring of the cluster interconnect detects an error of the AZ, and the node becomes LEFTCLUSTER.
Error of the guest OS and the cluster interconnect
The cyclic monitoring of the cluster interconnect detects a hang-up of the guest OS, 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.
Operating cloud: Microsoft Azure
Operating region: East Japan, West Japan
Operating OS: Red Hat Enterprise Linux 7.2 (for Intel64) or later, Red Hat Enterprise Linux 8.1 (for Intel64) or later
Note
The snapshot of the virtual machine 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
Azure features that involve node operations (Auto Scaling, etc.) cannot be used.
