expresscluster d product introduction · cloud platform - aws vpc (monitoring for availability...
TRANSCRIPT
EXPRESSCLUSTER D Product Introduction
October, 2016
EXPRESSCLUSTER Team,
Cloud Platform Division,
NEC Corporation
Index
1. What is HA Cluster
2. Market Share of EXPRESSCLUSTER
3. EXPRESSCLUSTER D Series
4. Use Scene
5. Cluster Configuration
6. Variety of Operation
7. Feature / Function
8. Additional Option
9. Product Lineup
10. License Scheme
11. Configuration Examples
12. System Requirement
13. Remarks
14. Related Products
1. What is HA Cluster
Overview
Position of HA cluster system
5 © NEC Corporation 2016
1. What is HA Cluster Overview
HA cluster is used for achieving high availability of the system
▌Protection from every failure, avoiding IT system stop.
Redundancy for business system including Hardware, OS, etc.
Monitoring for failure of Hardware, application, OS, etc.
Takeover of the application and data to the stand-by server when failure occurs
▌EXPRESSCLUSTER is the software to realize HA cluster
Failure Failure
Business stops until the server recovers
Business continues by using stand-by server
Failover
6 © NEC Corporation 2016
1. What is HA Cluster Position of HA cluster system
HA cluster is superior solution to backup
▌Support for wide-range failure achieving business continuity
BCP, storage mirroring, remote clustering
Clustering software
Backup software
Hardware
Data
Application
Site
Measure for failure
Measure for disaster and terrorism
Stand-by machine
(Cold stand-by)
Scale of failures and measures
2. Market Share of EXPRESSCLUSTER
8 © NEC Corporation 2016 Reproduction Prohibited
2. Market Share of EXPRESSCLUSTER
Revenue
22.3%
A
19.1%
B
11.6%
C 6.8%
D 6.6%
E 6.3%
F 5.7%
G 5.0%
H 4.8% Others 12.0%
No.1
6 years No.1
Source:IDC Japan, July 2015 “Japan System Software 2015-2019 Forecast and 2014 Analysis” (J15380103) IDC AP, August 2015 “Asia/Pacific (Excluding Japan) Availability and Clustering Software Market Update 2015” (AP251101)
33.8%
B
12.3% G
11.7% D 7.5%
C 6.2%
F 5.9%
I 4.2%
E 3.9% Others 14.5%
21.6%
A
46.9%
E
11.7%
C 5.2%
D 3.9%
H 3.0%
Others 7.7%
Linux
Windows
Breakdown of market share by OS
Revenue
Revenue
*ACS : Availability and Clustering Software
No.1
No.2
APAC (including Japan)
3. EXPRESSCLUSTER D Series
Product concept
10 © NEC Corporation 2016
3. EXPRESSCLUSTER D Series Product concept
Why “D” ?
Diversity Dynamic
Data Protection
Deployment
Robust data protection with snapshot and multi-stage configuration
Intuitive GUI. Easy cluster configuration with Chef
With intelligent mirroring, mirror method is dynamically switched to appropriate setting
Disaster Recovery
Double Decade
Various way of disaster recovery by adding stand-by nodes in remote / cloud location
Sync.
Async.
Snapshot
X
20-year rich experience of product development
4. Use Scene
Continuous operation in case of failure
Planned maintenance
Minimized RPO and RTO
Disaster recovery by remote cluster
Support for HA function of hypervisor
Ensured HA for cloud environment
12 © NEC Corporation 2016
▌Solution by EXPRESSCLUSTER
4. Use Scene
Measure for failure and disaster as well as planned maintenance
▌Customer’s challenges
Continuous working environment without disruption
Secure of system service time to customer
Rapid data recovery to the status just before failure
Data protection and continuous working environment in case of disaster
High availability in virtual environment
High availability in cloud environment
Detection of system anomaly achieving automatic business continuity
Continuous system operation in case of planned maintenance
Minimized RPO and RTO in case of failure
Disaster recovery with remote cluster
Support for HA function of hypervisor
Ensured HA for cloud environment
13 © NEC Corporation 2016
4. Use Scene Continuous operation in case of failure
Ensured detection of system anomaly. Failover of system operation
Operation stops until maintenance
Loss of business opportunity
Loss of “reputation”
Auto recovery in another server*
Minimized loss of business opportunity
For the safe business operation
*: Takes over IP address, but connected session is once disrupted.
Failure
Failure=Business stop
Failure
Failover
Failure -> Auto recovery
▌Single configuration
▌Cluster configuration
Access to the same address
14 © NEC Corporation 2016
4. Use Scene Planned maintenance
Maintenance from stand-by server without operation stop*
37%: OS upgrade / OS reboot due to
service pack and hot fix 13%: Application installation and application maintenance 12%: OS reboot to apply updated OS setting 7%: OS reboot to enable new hardware connection and setting 7%: OS reboot by other reasons
Stop due to failure 24%
9%: OS / driver panic 6%: Application error 5%: Hardware failure 4%: Other failures
Single server
Planned maintenance
76%
(Reference: June 2005, Microsoft. ”Windows Server 2003, EE reliability” document
Cause of system stop - Security patch - Service pack etc.
Maintenance
- Security patch - Service pack etc.
Maintenance
Active
System
Active
System
Server Switch
Active
System
Server Switch
Active
System
*: System stop time is required time for failover
15 © NEC Corporation 2016
4. Use Scene Minimized RPO and RTO
Shortened RPO and RTO
▌Data protected up to the point of failure*(Minimized RPO)
▌Recovery only requires time of failure detection and failover (Minimized RTO)
System Recovery Restart
Time
RTO (Recovery Time Objective) RPO (Recovery Point Objective)
Failure Normal Operation
Restart Data up to the point of failure remains
After failure detection at primary server, operation is switched to stand-by server
Restore data and system by using backup data
(Restart after operation check)
Suspension
In case of backup software
In case of EXPRESSCLUSTER D
Data Recovery
Data after periodical backup loses
RTO RPO
*: Only mirror disk type
16 © NEC Corporation 2016
4. Use Scene Disaster recovery by remote cluster
Measure for disaster such as earthquake, flood, fire, blackout, etc ▌Remote cluster and intelligent mirroring
Remote backup site reduces risk of system stop due to disaster
By industry’s first* intelligent mirroring function, data mirroring among remote locations is enabled with unstable network
*:NEC research as of Oct 3rd, 2016
Mirroring (Sync - snapshot)
Sync
Async
Snapshot
Failover
Dynamic and automatic switch of data mirroring method according to network status and data quantity
Active Stand-by
Node group A Node group B
17 © NEC Corporation 2016
4. Use Scene Support for HA function of hypervisor
Detects software failure which HA function of hypervisor cannot do
▌EXPRESSCLUSTER D supports HA function of hypervisor
Monitors virtual machine to solve application failure or hardware failure
Virtualization platform Virtualization platform
HW anomaly
Virtualization platform
HW anomaly
No failover in case of application failure Reboot VM on another host
Virtualization platform Virtualization platform
HW anomaly
Virtualization platform
HW anomaly
Reboot VM on another host Failover
HA function of virtualization platform only
With EXPRESSCLUSTER D
18 © NEC Corporation 2016
4. Use Scene Ensured HA for cloud environment
EXPRESSCLUSTER solves issue on cloud environment
▌Availability of VMs and storage needs to fulfill SLA requirement that cloud vendor defines
Solves by redundancy configuration
▌Users are responsible for application’s availability
Avoids business loss by monitoring application
▌Needs to consider planned stop by cloud vendor
Availability Set Availability Zone A
Availability Zone B
Microsoft Azure Amazon Web Services
EC2 EC2
What is SLA? Target of working
rate on certain condition.
5. Cluster Configuration
Shared disk configuration
Mirror disk configuration
Mirror disk configuration (Multi-stage configuration)
Mirror disk configuration (Object storage configuration)
Disk-less configuration
20 © NEC Corporation 2016
5. Cluster Configuration Shared disk configuration
Shared disk configuration ▌For high performance, high reliability and large capacity system
▌No hardware dependency because access control to shared disk is not managed by hardware
Failover
Failure
Active
Application
Stand-by
Application •Maximum 32 nodes configuration*
•M:N multi node configuration
*: Standard enables maximum 32 nodes. Core, Core Plus is maximum 2 nodes.
21 © NEC Corporation 2016
5. Cluster Configuration Mirror disk configuration
▌Mirroring of virtual volume using built-in disk of node
▌Data mirroring via network enables low-cost and space saving
•Maximum 32 nodes configuration *1
•Mirror disk size for saving date is maximum 64TB *2
Failover
Failure
Active
Application
When data is updated, data is written in each server’s built-in disk
*1: Standard enables maximum 32 nodes. Core Plus is maximum 2 nodes.
*2: Standard enables maximum 64TB. Core Plus is maximum 1TB.
Stand-by
Application
Mirror disk configuration
22 © NEC Corporation 2016
5. Cluster Configuration Mirror disk configuration
Multi-stage configuration*1
▌Load of active node is reduced by mirroring from stand-by node
Failure
Failure
1. Failure at node A Failover
Node A
Node B
Node C
2. Failure at node B Failover
•Maximum 32 nodes configuration *1
•Mirror disk size to save date is maximum 64TB *2
*1: Standard enables maximum 32 nodes. Core Plus is maximum 2 nodes.
*2: Standard enables maximum 64TB. Core Plus is maximum 1TB.
Mirroring (Sync)
Mirroring (Async)
23 © NEC Corporation 2016
5. Cluster Configuration Mirror disk configuration
Object storage configuration
▌Data mirroring to object storage on cloud service
▌Operation cost reduction by stopping stand-by node
Differential data stored in object storage
Mirroring (Object mirror)
Synchronize differential data when stand-by node boots
Active
Stand-by
• System configuration: Creates stand-by node on cloud, and configure HA cluster with on-premise server. Then, adds object storage between on-premise server and virtual machine.
• Operation: Stops stand-by node, and stores the differential data of on-premise server to object storage.
• Failure: Boots stand-by node, get differential data from object storage, and synchronize data.
HA clustering
Node stops after clustering
Adds object storage
24 © NEC Corporation 2016
5. Cluster Configuration Disk-less configuration
Disk-less configuration
▌Cluster not necessary for data synchronization between nodes.
▌Redundancy for hardware, OS, and application
Failover
Failure
Active
Application
Stand-by
Application •Maximum 32 nodes configuration*
•M:N multi-node configuration
*: Standard enables maximum 32 nodes. Core, Core Plus is maximum 2 nodes.
6. Variety of Operation
26 © NEC Corporation 2016
6. Variety of Operation
Active - Stand-by Active - Active (Mutual stand-by)
Active - On-demand Stand-by
Active Stand-by
Failover
Active Stand-by Stand-by Active Active
The most popular cluster configuration.
When anomaly is detected in active node, failover to stand-by node is executed.
With 3 or more servers, expanded system such as active - stand-by - stand-by can be configured.
N : 1 stand-by configuration is enabled to avoid risk of active - active configuration
Cluster configuration with different application in each node to create several active - stand-by configurations.
Failover from failure server to healthy node
In case of failure, one server needs to operate two applications.
By linkage with object storage, stand-by node operation time is minimized and it leads to cost reduction.
Failover
Failover
Stand-by
Failover
Mirroring (object storage)
Mirroring (object storage)
Application Application App A Application Application App B App A App B
7. Feature / Function
Rapid failover
Detectable failure
Snapshot
User Experience
Multi-platform support
28 © NEC Corporation 2016
7. Feature / Function Rapid failover
Node switch in around 1 minute
2. Application stop
4. Virtual IP resource stop
3. Mirror resource stop
1. Failure detection
1. Failure detection
2. Application stop
4. Virtual IP resource stop
3. Mirror resource stop
7. Application start
5. Virtual IP resource start
6. Mirror resource start
Around 1 minute Required to this step
Resource group stop
7. Application start
5. Virtual IP resource start
6. Mirror resource start
Resource group start
What is resource group? Container to manage more than 1 resources. Failover between nodes is executed based on resource group.
Active Stand-by
29 © NEC Corporation 2016
7. Feature / Function Detectable failure
Failure detection with various monitoring to ensure operation
▌Only EXPRESSCLUSTER can monitor stand-by node*
Cloud platform
- AWS VPC (Monitoring for Availability Zone)
Network path
Shared storage
DNS server
DNS record (Including cloud service)
Process
DataBase
File sharing
Mirroring System
Active Stand-by
OS
Registry synchronization
Virtual IP
- Azure DNS - AWS Route53
Process
Built-in disk
NIC (Monitoring for user environment)
Monitors both active and stand-by nodes
*: NEC research as of October 3rd, 2016
30 © NEC Corporation 2016
EXPRESSCLUSTER can create snapshot of mirror data
▌EXPRESSCLUSTER can create snapshot linked to rest point of DB
▌In case of data loss or data destruction, data can be recovered to the point of snapshot creation
7. Feature / Function Snapshot
DataBase*
Creates rest point
Selects and mounts snapshot (rest point)
Rest point#1 Rest point#2
Snapshot
・・・
Rest point#1 Rest point#2
Snapshot
・・・
* Supported DB (As of October 2016) Windows: Oracle Database, SQLServer Linux: Oracle Database, MySQL, MariaDB
31 © NEC Corporation 2016
7. Feature / Function User Experience
Easy configuration and setting
Easy to check procedure
Clear status visualization
Left click only for each operation
Setting in wizard format with confirmation function
32 © NEC Corporation 2016
Support for both Windows and Linux. No dependency on environment
7. Feature / Function Multi-platform support
Hardware Virtualization platform* Cloud*
OS
Windows Server 2012 R2 Hyper-V Windows Server 2012 Hyper-V
Windows Server 2008 R2 Hyper-V
VMware vSphere 6.0, 5.5, 5.1
X86 server Amazon Web Services
NEC Cloud IaaS
Microsoft Azure
Windows Server 2016
Red Hat Enterprise Linux 7.2, 7.1, 6.8, 6.7, 6.6
CentOS 7.2, 7.1, 6.8, 6.7, 6.6
Asianux Server 7 == MIRACLE LINUX V7 SP1 Asianux Server 7 == MIRACLE LINUX V7 Asianux Server 4 == MIRACLE LINUX V6 SP6 Asianux Server 4 == MIRACLE LINUX V6 SP5 Asianux Server 4 == MIRACLE LINUX V6 SP4
Windows Server 2012 R2, 2012
Linux Windows
*: Validated by NEC (As of October 2016)
8. Additional Option
EXPRESSCLUSTER D DR Option
EXPRESSCLUSTER D Media Kit
34 © NEC Corporation 2016
Failover policy control for each site in case of remote cluster*
▌Enables to define node group for remote cluster configuration. In local site, failover is automatically done. In case of failover to remote site, following operation is available.
Administrator can choose manual failover between different sites in appropriate timing.
In case of local site crash, automatic failover to the remote site is executed.
8. Additional Option EXPRESSCLUSTER D DR Option
Node group A Node group B
Failure
Node 1 Node 2 Node 3
Failover
e.g.: Failover within node group A
Failure
No automatic failover. Manual failover available by administrator’s choice.
*: In this slide, site and node group are same meaning
35 © NEC Corporation 2016
8. Additional Option EXPRESSCLUSTER D Media Kit
“Parameter sheet” for cluster configuration, “sample code” compliant with RESTful API, “Cookbook” of Chef etc
2. API reference of EXPRESSCLUSTER D and sample code
1. Parameter sheet
3. Chef user guide and Cookbook
Generates setting file by single click on parameter sheet to reduce effort to create setting file. Parameter information can be copied to use for specification form.
Executes API on user application to get cluster information or operate cluster. Sample code compliant to API specification is attached.
4. Manual
5. Installer
Cookbook for EXPRESSCLUSTER D is included. Automated HA cluster configuration is enabled with Chef. This reduces human error and effort during HA cluster configuration. Setting files created by parameter sheet can be combined and utilized.
EXPRESSCLUSTER D user’s guide
EXPRESSCLUSTER D module
36 © NEC Corporation 2016
8. Additional Option EXPRESSCLUSTER D Media Kit
▌HA cluster can be configured in short-time, leading cost reduction
▌Anyone can configure the same environment without mistake
*1: Chef is the tool of automation framework of server configuration and its management.(https://www.chef.io/) This enables to automate server configuration that is normally done in manual. *2: Parameter sheet and Cookbook for EXPRESSCLUSTER D is included in EXPRESSCLUSTER D Media Kit.
Chef server
Parameter sheet*2
2
Server name IP address Resource
…
Setting file
1
Engineer
Installation Firewall setting Setting file distribution Server restart Cluster start …
recipe
Cookbook*2
Uploads the setting file
Chef command execution
Server
Brief, easy, and automated HA cluster configuration with Chef*1
9. Product Lineup
38 © NEC Corporation 2016
Product Name Overview
Base Product EXPRESSCLUSTER D 1.1 EXPRESSCLUSTER D Base Product
Main Product
EXPRESSCLUSTER D Standard 1.1 EXPRESSCLUSTER D Core Plus 1.1 EXPRESSCLUSTER D Core 1.1
EXPRESSCLUSTER D CPU License
Function Overview:
- Cluster configuration: Shared disk, mirror disk, diskless
- Application monitoring: DB, file sharing, general purpose resource
- Email alert
* Specification of each edition is described at next page.
EXPRESSCLUSTER D Standard 1.1 for VM EXPRESSCLUSTER D Core Plus 1.1 for VM EXPRESSCLUSTER D Core 1.1 for VM
EXPRESSCLUSTER D VM License
Function Overview:
- Cluster configuration: Shared disk, mirror disk, diskless
- Application monitoring: DB, file sharing, general purpose resource
- Email alert
* Specification of each edition is described at next page.
Option Product
EXPRESSCLUSTER D DR Option 1.1 EXPRESSCLUSTER D option product for remote cluster
- Failover policy management among each node group
Product Media EXPRESSCLUSTER D Media Kit 1.1 EXPRESSCLUSTER D Media for Windows and Linux
Contents:
- Parameter sheet
- EXPRESSCLUSTER D API reference and sample code
- Chef user guide and Cookbook
- Manual
- Installer
9. Product Lineup
39 © NEC Corporation 2016
Standard edition is recommended
Edition Standard Core Plus Core
Overview Full function available (shared disk, mirror disk)
For small capacity system (mirror disk configuration)
For small scale system (Shared disk configuration)
Maximum cluster node 32 2 2
Shared disk cluster config Supported Supported Supported
Mirror disk cluster config Supported Supported
Mirror disk capacity 64TB 1TB
On demand stand-by (Object storage linkage)
Supported
Cloud environment Supported
Email alert Supported
DataBase monitoring Supported
File sharing monitoring Supported
General purpose resource monitoring*
Supported Supported Supported *: Script needs to be created
9. Product Lineup
10. License Scheme
41 © NEC Corporation 2016
10. License Scheme
License count
Product Name Description
Based on cluster
EXPRESSCLUSTER D 1.1 EXPRESSCLUSTER D base product. EXPRESSCLUSTER D CPU license or VM license is also mandatory.
Based on CPU number
EXPRESSCLUSTER D Standard 1.1 EXPRESSCLUSTER D Core Plus 1.1 EXPRESSCLUSTER D Core 1.1
EXPRESSCLUSTER D CPU license. EXPRESSCLUSTER D base product is also required. Required number of license is equal to the total number of each server’s CPU.
* Both Primary server and stand-by server are counted. * Idle slot of CPU is not counted. * Core (dual core etc) / hyper-threading are not doubly counted * In case of ft server and virtual machine, CPU number is counted based on OS’s recognition, but core and thread are not counted.
Based on server number
EXPRESSCLUSTER D Standard 1.1 for VM EXPRESSCLUSTER D Core Plus 1.1 for VM EXPRESSCLUSTER D Core 1.1 for VM
EXPRESSCLUSTER D VM license dedicated to virtual machine. EXPRESSCLUSTER D base product is also required. Required number of license is based on the number of virtual machines that EXPRESSCLUSTER D is implemented.
* Both Primary node and stand-by node are counted.
EXPRESSCLUSTER D DR Option 1.1 EXPRESSCLUSTER D option product for remote cluster. - Failover policy management among each node group EXPRESSCLUSTER D base license and main license (CPU or VM) are mandatory. Required number of license is equal to the number of servers that EXPRESSCLUSTER D is implemented. (Same count method for both physical and virtual server) * Both Primary node and stand-by node are counted.
(Not mandatory)
EXPRESSCLUSTER D Media Kit 1.1 EXPRESSCLUSTER D Media for Windows and Linux
Contents:
- Parameter sheet
- EXPRESSCLUSTER D API reference and sample code
- Chef user guide and Cookbook
- Manual
- Installer
11. Configuration Examples
2 node shared disk configuration (1CPU server x2)
2 node mirror disk configuration (Virtual server x2)
3 node mirror disk configuration (1CPU server x1, Virtual server x2)
2 node mirror disk object storage configuration (1CPU server x1, virtual server x1)
Other configurations
43 © NEC Corporation 2016
2 node shared disk configuration (1CPU server x2)
11. Configuration Examples Shared disk configuration
Failover
Active
Application
Stand-by
Application
1CPU 1CPU
Mandatory Product Name Quantity
✓ EXPRESSCLUSTER D 1.1 (1 cluster license) 1
✓ EXPRESSCLUSTER D Standard 1.1 (1CPU license) 2
EXPRESSCLUSTER D Media Kit 1.1 1
44 © NEC Corporation 2016
11. Configuration Examples Mirror disk configuration
2 node mirror disk configuration (Virtual server x2)
Failover
Active
Application
Stand-by
Application
1VM 1VM
Mandatory Product Name Quantity
✓ EXPRESSCLUSTER D 1.1 (1 cluster license) 1
✓ EXPRESSCLUSTER D Standard 1.1 for VM (1 node license) 2
EXPRESSCLUSTER D Media Kit 1.1 1
45 © NEC Corporation 2016
11. Configuration Examples Mirror disk configuration
3 node mirror disk configuration (1CPU server x1, Virtual server x2)
Failover
Active
Application
Stand-by
Application
1CPU 1CPU
Failover
Stand-by
Application
1VM
Mandatory Product Name Quantity
✓ EXPRESSCLUSTER D 1.1 (1 cluster license) 1
✓ EXPRESSCLUSTER D Standard 1.1 (1CPU license) 2
✓ EXPRESSCLUSTER D Standard 1.1 for VM (1 node license) 1
EXPRESSCLUSTER D Media Kit 1.1 1
46 © NEC Corporation 2016
2 node mirror disk object storage configuration (1CPU server x1, virtual server x1)
Mandatory Product Name Quantity
✓ EXPRESSCLUSTER D 1.1 (1 cluster license) 1
✓ EXPRESSCLUSTER D Standard 1.1 (1CPU license) 1
✓ EXPRESSCLUSTER D Standard 1.1 for VM (1 node license) 1
✓ EXPRESSCLUSTER D DR Option 1.1 (1 node license) 2
EXPRESSCLUSTER D Media Kit 1.1 1
1CPU 1VM
Active Stand-by
Mirroring (Asynchronization)
VPN
11. Configuration Examples Mirror disk configuration
47 © NEC Corporation 2016
Low price Core / Core Plus edition
▌Core: 2 node shared disk configuration (virtual servers x2)
▌Core Plus: 2 node mirror disk configuration (1CPU server x2)
11. Configuration Examples Other configurations
Mandatory Product Name Quantity
✓ EXPRESSCLUSTER D 1.1 (1 cluster license) 1
✓ EXPRESSCLUSTER D Core Plus 1.1 (1CPU license) 2
EXPRESSCLUSTER D Media Kit 1.1 1
Mandatory Product Name Quantity
✓ EXPRESSCLUSTER D 1.1 (1 cluster license) 1
✓ EXPRESSCLUSTER D Core 1.1 for VM (1 node license) 2
EXPRESSCLUSTER D Media Kit 1.1 1
12. System Requirement
49 © NEC Corporation 2016
12. System Requirement
Windows Linux*1
OS Architecture x86_64 x86_64
Windows Server 2016 Windows Server 2012 R2 Windows Server 2012
Asianux Server 7 == MIRACLE LINUX V7 SP1 Asianux Server 7 == MIRACLE LINUX V7 Asianux Server 4 == MIRACLE LINUX V6 SP6 Asianux Server 4 == MIRACLE LINUX V6 SP5 Asianux Server 4 == MIRACLE LINUX V6 SP4 Red Hat Enterprise Linux 7.2, 7.1 Red Hat Enterprise Linux 6.8, 6.7, 6.6 CentOS 7.2, 7.1 CentOS 6.8, 6.7, 6.6
Required memory 2GB or higher 2GB or higher
Required disk size 300MB or higher*2 550MB or higher*2
Supported browser Internet Explorer 11 (Japanese/English/Simplified Chinese) Internet Explorer 10 (Japanese/English/Simplified Chinese) Mozilla Firefox 45 or later (Japanese/English/Simplified Chinese) *3
Details are on product website http://www.nec.com/en/global/prod/expresscluster/d/system_requirements/index.html
*1: Depends on Kernel version due to its original driver module. Supported Kernel version is described in the user’s guide. *2: In case of mirroring, capacity equivalent to the mirrored data's directory size is additionally required. *3: Target version of Firefox ESR (extended support for enterprise) is supported.
13. Remarks
51 © NEC Corporation 2016
13. Remarks
▌The cases that failover cannot solve the failure
In following cases, system stops after the failover
• In case same failure occurs at stand-by node (e.g. failure caused by corrupt data, virus infection, etc)
• In case performance shortage causes the failure, and stand-by node also has performance shortage
▌Shared disk
Partition for control is required.
RAW cannot be used in Linux edition.
▌Mirroring
Mirroring is done in units of virtual volumes. (No mirroring of physical partition)
Virtual volume is automatically generated by EXPRESSCLUSTER function.
Mirror volume size cannot be changed dynamically.
Supported file systems are NTFS (Windows) and ext4(Linux) only.
Mirrored data's directory size needs to be designed in advance.*
▌Others
ODBC driver needs to be installed for database monitoring.
Virtual IP address (floating IP address) can be used only in case of same subnet.
DR Option license is required to set up node group.
*: Standard size Mirror volume size + data quantity + maximum size possibly to be used by operating mirror resource (mirror volume size + 10GB)
14. Related Products
53 © NEC Corporation 2016
14. Related Products EXPRESSCLUSTER X
Previous generation product of EXPRESSCLUSTER D
▌Rich function from long-year experience Many clustering configuration (mirror disk, shared disk, hybrid disk)
Smart failover enabling failure prediction and failover to appropriate server
Host-guest linkage enabling close integration in virtual environment by linking with EXPRESSCLUSTER X SingleServerSafe
VPN
Hybrid disk configuration
Virtualization platform
Failover request after anomaly detection
Failure
SingleServerSafe SingleServerSafe
Virtualization platform
Host-guest linkage “Down” tendency of
resource usage
Predicts resource shortage in near future
Present Future
“UP” tendency of resource usage
Smart failover
54 © NEC Corporation 2016
▌Business continuity by detecting OS / application hang up and service abnormal termination, and rebooting.
14. Related Products EXPRESSCLUSTER X SingleServerSafe
Experience of EXPRESSCLUSTER X is applied to single server
OS (user space)
Loss of process
Application
NIC
Built-in disk
Detection of hang up
Anomaly of application and service
Business continuity by rebooting application and service
Business continuity by OS reboot
Business continuity by switch to spare NIC (Windows only)