ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

More documents

Recommendations

Info

Chapter 1 What is a cluster system?Normal OperationOccurrence of FailureFailoverOperationOperationServer FailureOperation TransferFailbackRecovering ServerOperationOperationFigure 1-2: From occurrence of a failure to recoveryWhen the specification of the failover destination server does not meet the system requirements oroverload occurs due to multi-directional stand-by, operations on the original server are preferred.In such a case, a failback takes place to resume operations on the original server.A stand-by mode where there is one operation and no operation is active on the stand-by server, asshown in Figure 1-3, is referred to as uni-directional stand-by. A stand-by mode where there aretwo or more operations with each server of the cluster serving as both active and stand-by servers isreferred to as multi-directional stand-by.Normal OperationNormal OperationActiveServerStand-byServerActive Server forOperation AStand-by Server forOperation BActive Server forOperation BStand-by Server forOperation AOperationOperation AOperation BFigure 1-3: HA cluster topology18ExpressCluster X 3.1 for Linux Getting Started Guide
High Availability (HA) clusterData mirror typeThe shared disk type cluster system is good for large-scale systems. However, creating a systemwith this type can be costly because shared disks are generally expensive. The data mirror typecluster system provides the same functions as the shared disk type with smaller cost throughmirroring of server disks.The data mirror type is not recommended for large-scale systems that handle a large volume of datasince data needs to be mirrored between servers.When a write request is made by an application, the data mirror engine not only writes data in thelocal disk but sends the write request to the stand-by server via the interconnect. Interconnect is anetwork connecting servers. It is used to monitor whether or not the server is activated in thecluster system. In addition to this purpose, interconnect is sometimes used to transfer data in thedata mirror type cluster system. The data mirror engine on the stand-by server achieves datasynchronization between stand-by and active servers by writing the data into the local disk of thestand-by server.For read requests from an application, data is simply read from the disk on the active server.Active ServerNormal OperationStand-by ServerApplicationFile SystemNICLAN (Interconnect)NICData MirrorEngineClusterData MirrorEngineDiskDiskWriteReadFigure 1-4: Data mirror mechanismSnapshot backup is applied usage of data mirroring. Because the data mirror type cluster systemhas shared data in two locations, you can keep the disk of the stand-by server as snapshot backupwithout spending time for backup by simply separating the server from the cluster.Failover mechanism and its problemsThere are various cluster systems such as failover clusters, load distribution clusters, and highperformance computing (HPC) clusters. The failover cluster is one of the high availability (HA)cluster systems that aim to increase operational availability through establishing server redundancyand passing operations being executed to another server when a failure occurs.Section I Introducing ExpressCluster19
Page 1 and 2: ExpressCluster ® X 3.1 for LinuxGe
Page 3: © Copyright NEC Corporation 2011.
Page 6 and 7: Section II Installing ExpressCluste
Page 8 and 9: Shutdown and reboot of individual s
Page 10 and 11: ExpressCluster X Documentation SetT
Page 12 and 13: Contacting NECFor the latest produc
Page 15 and 16: Chapter 1What is a cluster system?T
Page 17: High Availability (HA) clusterShare
Page 22 and 23: Chapter 1 What is a cluster system?
Page 29 and 30: Chapter 2Using ExpressClusterThis c
Page 31 and 32: Software configuration of ExpressCl
Page 33 and 34: Software configuration of ExpressCl
Page 35 and 36: Network partition resolutionNetwork
Page 37 and 38: Failover mechanismFailover resource
Page 39 and 40: Failover mechanismDifferent Applica
Page 41 and 42: Failover mechanismHardware configur
Page 43 and 44: Failover mechanismWhat is cluster o
Page 45 and 46: What is a resource?NAS resource (na
Page 47 and 48: What is a resource?Websphere monito
Page 49: Section IIInstallingExpressClusterT
Page 52 and 53: Chapter 3 Installation requirements
Page 68 and 69:
Chapter 3 Installation requirements
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 79 and 80:
Chapter 4Latest version information
Page 81 and 82:
System requirements for WebManager
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Chapter 5Notes and RestrictionsThis
Page 109 and 110:
Designing a system configurationHar
Page 111 and 112:
Designing a system configurationHar
Page 113 and 114:
Designing a system configurationNet
Page 115 and 116:
Designing a system configuration4.
Page 117 and 118:
Designing a system configurationThe
Page 119 and 120:
Installing operating systemIt is po
Page 121 and 122:
Installing operating systemsoftdogT
Page 123 and 124:
Before installing ExpressClusterSer
Page 125 and 126:
Before installing ExpressClusterCha
Page 127 and 128:
Before installing ExpressClusterUse
Page 129 and 130:
Notes when creating ExpressCluster
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
After start operating ExpressCluste
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151:
Updating ExpressClusterUpdating Exp
Page 154 and 155:
Chapter 6 Upgrading ExpressClusterH
Page 157:
Appendix• Appendix A Glossary•
Page 160 and 161:
Appendix A GlossaryNodeHeartbeatPub
Page 162:
Appendix B Indexmonitorable and non
show all

ExpressCluster X 3.1 for Linux Getting Started Guide - Nec

Create successful ePaper yourself

Delete template?

Save as template?