Adaptec 412R User Guide - Page 128

and a number of other features differentiate cluster

Get Adaptec 412R - DuraStor Storage Enclosure PDF manuals and user guides
UPC - 760884139691
View all Adaptec 412R manuals
Add to My Manuals
Save this manual to your list of manuals

Page 128 highlights

DuraStor 412R/6320SS/7320SS Installation and User's Guide more than 43 hours of downtime per year. In contrast, 99.99 percent uptime translates into less than one hour (52 minutes) of downtime per year. Availability figures relate primarily to unplanned downtime. But the advantages of clusters in terms of planned or scheduled downtime are even more significant. If you figure two to sixteen hours per month for a server in a large shop. Planned downtime requires shutting down stand-alone systems entirely. Result: 100 percent loss of processing for the duration of the downtime. But, with cluster, you can shut down one node and off-load the processing to other nodes in the cluster with no interruption of processing. High availability is not the only benefit of clustering. In some cases, users may see advantages in the areas of performance, scalability, and manageability. In reality, you can expect a 1.6x (80 percent efficiency) to 1.8x (90 percent efficiency) performance increase as you go from one node to two nodes. Going from one node to a four node cluster generally yields a 2.5x or 3x performance boost. However, the cluster performance is application dependent. For example, READ operations may yield a 1.8x performance increase going from one to two nodes, but in a WRITE intensive application, you may only see a 1.4-1.6x improvement. Although clusters seem to be relatively simple, they involve complex technology that can be implemented in a variety of ways. The number of nodes supported and type of interconnection used, and a number of other features differentiate cluster implementations. One area of implementation is the manner in which distributed lock manager is implemented. Some perform this at the user level and others in the kernel, with the latter enhancing performance. In addition to the differing features you should consider if the cluster: I has the ability to hot load new nodes without bringing down the whole cluster? I provides automatic or manual failover? I loads balance? I uses a journalized file system? I provides a fast cluster failover? A-26

  • 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-26
DuraStor 412R/6320SS/7320SS Installation and User’s Guide
more than 43 hours of downtime per year. In contrast, 99.99 percent
uptime translates into less than one hour (52 minutes) of downtime
per year.
Availability figures relate primarily to unplanned downtime. But
the advantages of clusters in terms of planned or scheduled
downtime are even more significant. If you figure two to sixteen
hours per month for a server in a large shop.
Planned downtime requires shutting down stand-alone systems
entirely. Result: 100 percent loss of processing for the duration of
the downtime. But, with cluster, you can shut down one node and
off-load the processing to other nodes in the cluster with no
interruption of processing.
High availability is not the only benefit of clustering. In some cases,
users may see advantages in the areas of performance, scalability,
and manageability. In reality, you can expect a 1.6x (80 percent
efficiency) to 1.8x (90 percent efficiency) performance increase as
you go from one node to two nodes. Going from one node to a four
node cluster generally yields a 2.5x or 3x performance boost.
However, the cluster performance is application dependent. For
example, READ operations may yield a 1.8x performance increase
going from one to two nodes, but in a WRITE intensive application,
you may only see a 1.4-1.6x improvement.
Although clusters seem to be relatively simple, they involve
complex technology that can be implemented in a variety of ways.
The number of nodes supported and type of interconnection used,
and a number of other features differentiate cluster
implementations. One area of implementation is the manner in
which distributed lock manager is implemented. Some perform
this at the user level and others in the kernel, with the latter
enhancing performance.
In addition to the differing features you should consider if the
cluster:
■
has the ability to hot load new nodes without bringing down
the whole cluster?
■
provides automatic or manual failover?
■
loads balance?
■
uses a journalized file system?
■
provides a fast cluster failover?