HP NetServer AA 4000 HP Netserver AA Solution Administrator's Guide v - Page 21

Benefit, Description, Table 1-1

Page 21 highlights

Table 1-1 Endurance Server Benefits Benefit Description Redundant, fault tolerant processing and I/O subsystem SplitSite Support Continuous network connectivity Support for multiple network connections Industry-standard hardware platform Run unmodified, shrink-wrapped applications Automatic mirroring Automatic fault detection and reporting Transparent switchover The Endurance server uses redundant hardware and Endurance software to ensure that your server remains operational even in the event of a failed processor, a memory failure, an I/O failure (even those associated with I/O controllers), a disk drive failure, or a failed Ethernet adapter. The Endurance server implements SplitSite technology that enables you to locate your server across different geographic locations. This real-time "hot site" provides a complete range of data protection from minimal business interruptions (such as power failure) to maximum disaster protection. The Endurance server maintains continuous network connectivity by detecting any network adapter or connectivity failures. If a failure occurs, the redundant network connection continues processing all network traffic. This ensures that Endurance server network connections are maintained without loss of network traffic or client connectivity. The Endurance server can support multiple Ethernet connections or connections to multiple networks to provide additional network redundancy and network traffic control. The Endurance server uses industry-standard Pentium-based system hardware. This reduces the cost of initial ownership and enables you to redeploy these systems if you upgrade your server. The Endurance server can execute any Windows-compatible application. This means that you do not have to generate support for any special APIs or scripts to enable your application to run on an Endurance server. In an Endurance server, the data on mirrored devices are automatically maintained, ensuring that data are current. The Endurance server detects, isolates, and reports all events, including general status, state changes, and faults. Most messages are logged to the Windows event logs, while others are displayed as they occur in Windows blue screens, pop-up windows, or in a window in the Endurance Manager. The Endurance software constantly monitors the Endurance server for events. If an Endurance server component fails, the Endurance server transparently uses that component's redundant counterpart. This maintains data and user access without any loss of service to applications. Introduction 1-3

  • 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
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272

Introduction
1-3
Table 1-1
Endurance Server Benefits
Benefit
Description
Redundant, fault tolerant
processing and I/O subsystem
The Endurance server uses redundant hardware and Endurance
software to ensure that your server remains operational even in the
event of a failed processor, a memory failure, an I/O failure (even
those associated with I/O controllers), a disk drive failure, or a
failed Ethernet adapter.
SplitSite Support
The Endurance server implements SplitSite technology that
enables you to locate your server across different geographic
locations. This real-time ±hot site² provides a complete range of
data protection from minimal business interruptions (such as power
failure) to maximum disaster protection.
Continuous network connectivity
The Endurance server maintains continuous network connectivity
by detecting any network adapter or connectivity failures. If a failure
occurs, the redundant network connection continues processing all
network traffic. This ensures that Endurance server network
connections are maintained without loss of network traffic or client
connectivity.
Support for multiple network
connections
The Endurance server can support multiple Ethernet connections
or connections to multiple networks to provide additional network
redundancy and network traffic control.
Industry-standard hardware
platform
The Endurance server uses industry-standard Pentium-based
system hardware. This reduces the cost of initial ownership and
enables you to redeploy these systems if you upgrade your server.
Run unmodified, shrink-wrapped
applications
The Endurance server can execute any Windows-compatible
application. This means that you do
not
have to generate support
for any special APIs or scripts to enable your application to run on
an Endurance server.
Automatic mirroring
In an Endurance server, the data on mirrored devices are
automatically maintained, ensuring that data are current.
Automatic fault detection and
reporting
The Endurance server detects, isolates, and reports all events,
including general status, state changes, and faults. Most messages
are logged to the Windows event logs, while others are displayed
as they occur in Windows blue screens, pop-up windows, or in a
window in the Endurance Manager.
Transparent switchover
The Endurance software constantly monitors the Endurance server
for events. If an Endurance server component fails, the Endurance
server transparently uses that component³s redundant counterpart.
This maintains data and user access without any loss of service to
applications.