Adaptec 2074700-R User Guide - Page 197

A.1.4, Releasing the Cluster Channels, A.1.5, The Microsoft Cluster Server Concept

Page 197 highlights

Optional Features A.1.4 Releasing the Cluster Channels Those channels which are used as shared channels for Clustering have to be released and marked as Clustering channels within the ICP RAID Console (press + at system boot level when the ICP RAID BIOS is displayed.).This applies to all ICP RAID controllers participating in the shared channel(s). Figure A-1. Cluster Channels A.1.5 The Microsoft Cluster Server Concept A Cluster Server is always made up of 2 individual Windows NT/2000 Servers, called Nodes. Both of these Nodes should at least be linked to a commonly used Shared Storage Bus. There must be a Quorum Resource on the shared storage bus. This can be a drive, a partition or a subdirectory. This resource is a kind of information exchange area which are used by both Nodes. An MSCS can not be configured or started without this kind of Quorum Resource. In addition to this resource, other or more disk arrays are normally configured as shared user data hard disks. These disks must be NTFS formatted. If one of the Nodes fails, the remaining server can take over its tasks. The application which is being carried out on the failed node is then restarted on the second node. The application has to be installed on both server systems. Possible temporary data or information are stored on the Quorum Resource. Corresponding cluster supporting applications can carry on the tasks from the point where the failed Node has stopped via these data and a corresponding API (Application Programming Interface). Other applications can simply be started anew. Software Installation and User's Guide 197

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214

Software Installation and User’s Guide
197
Optional Features
A.1.4
Releasing the Cluster Channels
Those channels which are used as shared channels for Clustering have to be released and
marked as Clustering channels within the ICP RAID Console (press <Ctrl>+<G> at
system boot level when the ICP RAID BIOS is displayed.).This applies to all ICP RAID
controllers participating in the shared channel(s).
Figure A-1. Cluster Channels
A.1.5
The Microsoft Cluster Server Concept
A Cluster Server is always made up of 2 individual Windows NT/2000 Servers, called
Nodes. Both of these Nodes should at least be linked to a commonly used Shared Storage
Bus.
There must be a Quorum Resource on the shared storage bus. This can be a drive, a
partition or a subdirectory. This resource is a kind of information exchange area which are
used by both Nodes. An MSCS can not be configured or started without this kind of
Quorum Resource. In addition to this resource, other or more disk arrays are normally
configured as shared user data hard disks. These disks must be NTFS formatted.
If one of the Nodes fails, the remaining server can take over its tasks. The application
which is being carried out on the failed node is then restarted on the second node. The
application has to be installed on both server systems. Possible temporary data or
information are stored on the Quorum Resource. Corresponding cluster supporting
applications can carry on the tasks from the point where the failed Node has stopped via
these data and a corresponding API (Application Programming Interface). Other
applications can simply be started anew.