Compaq Offers New Windows NT Cluster Solution

Compaq Computer Corp. today announced the Compaq ProLiant Cluster HA/F500, a two-node Microsoft Cluster Server (MSCS) cluster which provides enterprise customers with high levels of availability for business-critical applications, such as Enterprise Resource Planning (ERP), Online Transaction Processing (OLTP), database applications, E-mail and Web servers.

The Compaq ProLiant Cluster HA/F500 is aimed to eliminate single points of failure and automatically detect and recover from failures in hardware, operating systems and applications.

Compaq reports that the HA/F500 provides the highest levels of data availability when configured in a dual loop connection between the server and the storage sub-system. The new storage devices used are the StorageWorks RAID Array 8000 and Enterprise Storage Array 12000 high-end Optical Fibre Channel External storage subsystem, high capacity storage subsystems with redundant RAID controllers. Integrated with Compaq Insight Manager and SmartStart, the StorageWorks Command Console provides a graphical user interface to set up, configure, monitor and troubleshoot storage subsystems.

The two-node cluster configuration will support two pairs of controllers and 144 disks for a maximum storage capacity configuration of 2.6 TB per cluster. The dual ported RAID controllers in the storage subsystems can also be configured to support two independent clusters on a single dual-controller storage subsytem.

The HA/F500 also provides secure data management and cluster administration to prevent data corruption and make it easy to manage. The Compaq ProLiant Cluster HA/F500 can be configured with up to two Compaq ProLiant servers.

"Customers can configure HA/F500 Clusters with a variety of ProLiant servers and storage options to meet their specific requirements for performance, capacity, availability and budget," says Paul Gottsegen, director of industry standard server marketing, Compaq North America. "This redundancy eliminates single points of failure across the cluster to reduce the risk of downtime that could be caused by failure of an individual component." -- Brian Ploskina, Assistant Editor

About the Author

Scott Bekker is editor in chief of Redmond Channel Partner magazine.

comments powered by Disqus
Most   Popular