HP NetServer AA 4000 HP NetServer AA 6200 Solution Release 3.0 Administrator&a - Page 19

Chapter 1 Introduction Table 1-1 HP NetServer AA Server Benefits Benefit 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 Description The 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 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 CE 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 server network connections are maintained without loss of network traffic or client connectivity. The server can support multiple Ethernet connections or connections to multiple networks to provide additional network redundancy and network traffic control. The server uses industry-standard Pentium II and Pentium III-based system hardware. This reduces the cost of initial ownership and enables you to redeploy these systems if you upgrade your server. The server can execute any Windows NT-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 the server. In a server, the data on mirrored devices is automatically maintained, ensuring that data are current. The server detects, isolates, and reports all events, including general status, state changes, and faults. Most messages are logged to the Windows NT event logs, while others are displayed as they occur in Windows NT blue screens, pop-up windows, or in a window in the Endurance Manager. The software constantly monitors the server for events. If a server component fails, the server transparently uses that component's redundant counterpart. This maintains data and user access without any loss of service to applications. 3