Adaptec 412R User Guide - Page 127

Clustering, Minimizing Downtime for Maximum Data Availability

Page 127 highlights

Theory of Controller Operation Note: When Clear Configuration is selected in the Flash Utility menu, both the local Flash configuration and the other controller's mirrored configuration image are cleared. Also, there is an option (J) in the Flash Utility menu that can be used to tell a booting controller to temporarily ignore the mirrored configuration. This can be used, if for whatever reason, the mirrored configuration should not be used by a booting controller. This is primarily a safeguard, because a retrieved mirrored configuration is checked extensively before it is used. Clustering Minimizing Downtime for Maximum Data Availability So-called open systems, such as Windows NT servers, just don't provide the level of availability that IS managers are familiar with on mainframes. A partial solution to this problem is server clustering. Clusters consist of two or more loosely coupled systems with a shared-disk subsystem and software that handles failover in the case of a node (host) failure. In most cases, hardware/software failover is performed automatically and is transparent to users, although users will experience performance degradation as processing is shifted to another cluster node. In some cases this failover can occur in a matter of seconds. High availability of data and applications is by far the most compelling reason to go with clustering technology. For example, the accepted rule is that stand-alone UNIX systems can provide 99.5 percent uptime. Adding a RAID subsystem can increase the uptime to 99.9 percent. The goal of clustering is 99.99 percent availability. Beyond clustering, fault-tolerant systems can provide 99.9999 percent uptime. At the high end, continuous-processing systems offer virtually 100 percent uptime. Although the increase from 99.5 percent to 99.99 percent availability may seem insignificantly small, it adds up in terms of minutes per year of downtime. For example, assuming a 7x24 operation, 99.5 percent uptime translates into 2,628 minutes, or A-25

  • 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

A-25
Theory of Controller Operation
Note:
When Clear Configuration is selected in the Flash Utility
menu, both the local Flash configuration and the other controller’s
mirrored configuration image are cleared. Also, there is an option
(J) in the Flash Utility menu that can be used to tell a booting
controller to temporarily ignore the mirrored configuration. This
can be used, if for whatever reason, the mirrored configuration
should not be used by a booting controller. This is primarily a
safeguard, because a retrieved mirrored configuration is checked
extensively before it is used.
Clustering
Minimizing Downtime for Maximum Data Availability
So-called open systems, such as Windows NT servers, just don’t
provide the level of availability that IS managers are familiar with
on mainframes. A partial solution to this problem is server
clustering.
Clusters consist of two or more loosely coupled systems with a
shared-disk subsystem and software that handles failover in the
case of a node (host) failure. In most cases, hardware/software
failover is performed automatically and is transparent to users,
although users will experience performance degradation as
processing is shifted to another cluster node. In some cases this
failover can occur in a matter of seconds.
High availability of data and applications is by far the most
compelling reason to go with clustering technology. For example,
the accepted rule is that stand-alone UNIX systems can provide
99.5 percent uptime. Adding a RAID subsystem can increase the
uptime to 99.9 percent. The goal of clustering is 99.99 percent
availability.
Beyond clustering, fault-tolerant systems can provide 99.9999
percent uptime. At the high end, continuous-processing systems
offer virtually 100 percent uptime.
Although the increase from 99.5 percent to 99.99 percent
availability may seem insignificantly small, it adds up in terms of
minutes per year of downtime. For example, assuming a 7x24
operation, 99.5 percent uptime translates into 2,628 minutes, or