Co-StandbyServer for Windows NT/2000 Microsoft Windows

Your High-Availability Solution

Co-StandbyServer NT has earned industry recognition as the standard for others to aspire to (winner of several "Product of the Year" awards). For Windows 2000, Co-StandbyServer 2000 with its impressive list of new features and enhancements is setting out to continue that trend and leadership role.

Co-StandbyServer 2000 enables two fully functioning Windows 2000/Advanced servers to act as hot spares for each other in the case of application or server failure. If a failure occurs, Co-StandbyServer 2000 ensures a complete and reliable switchover. It transparently migrates the applications, data and users from the failed server to the mirroring server.



New features for Co-StandbyServer 2000

Supports Windows 2000

Improved Mirroring Engine - Greater data integrity (additional acknowledgement), partition-level mirror.

Intelligent Resources - Resources can be configured to trigger failover.

Intuitive Application Modules - Proactive Management of Application Services (true "Application" switchover).

Powerful New GUI - Single Console Management, multiple instances.



Solution Overview

Co-StandbyServer NT/2000 (Co-SBS NT/2000) ensures local high availability of applications and related data. Co-StandbyServer's block-level mirroring technology, and the use of a dedicated mirroring link, allows writes to be written to both servers at the same time. Unlike other solutions, this is done without adding additional traffic to the users production network. Co-StandbyServer does not require manual intervention after a server failure. Co-StandbyServer utilizes block-level synchronous mirroring vs. asynchronous replication at the file-level. The data is always in a known state avoiding problems associated with latency.

Co-Standby Server is the only block level mirroring solution for Microsoft NT/2000 that offers configuration flexibility (servers can be separated up to 10km through a designated link) and ensures true availability (99.99+%, 24/7) and access to mission-critical data and applications. COSBS's simplified implementation and management environment provides the ideal solution for small businesses or enterprise branch offices with limited or no on-site support. Existing industry standard hardware (does not require identical systems) can be utilized.

Co-StandbyServer NT/2000 for Windows NT/2000 is a clustering system that assures high-availability of critical network resources. Data, applications, shares, IP addresses, and printers are covered by this pure protection solution. Legato's new data mirroring technology operates at the device driver level on individual I/O requests. Data is synchronized between the cluster servers. Mirroring traffic uses a separate, dedicated inter-server link that keeps your LAN bandwidth free for client/server applications.

Co-StandbyServer NT/2000 protects critical SQL 7.0/2000 data by mirroring components from an SQL server to the secondary server in the clustered pair. The server not running SQL can be used as a redundant server or it can run other applications. In the event of a failure on the SQL Server, the surviving server quickly takes on the messaging responsibilities of the primary server. Co-StandbyServer ensures access to a complete and reliable application and data environment.

Co-StandbyServer NT/2000 protects Microsoft Exchange 5.5 by mirroring components from an Exchange Server to the secondary server in the clustered pair. The server not running Exchange can be used as a redundant server or it can run other applications. In the event of a failure on the Exchange Server, the surviving server quickly takes on the messaging responsibilities of the primary server. Co-StandbyServer always ensures a complete and reliable application and data environment.

Co-StandbyServer 2000 provides high availability for Microsoft Operations Manager 2000 by protecting the Microsoft Operations Manager events and performance data that are stored in a SQL 2000 database. Through the use of the SQL 2000 Application Module, Co-StandbyServer 2000 has the ability to move all necassary SQL 2000 resources from one machine to another in a matter of seconds. In the event the Microsoft Operations Manager database fails, Co-StandbyServer 2000 will quickly and automatically activate the database on a secondary machine, allowing all Microsoft Operations Manager procedures to continue. By ensuring the availability of Microsoft Operations Manager 2000, Co-StandbyServer 2000 provides the assurance that your critical data will be available as well as reducing the costs associated with down time. This is the latest in a series of solutions that provide true high availability for Microsoft's Windows environments.



Features & Benefits

Unparalleled Windows NT/2000 Applications Support

    Synchronize commonly used Windows NT/2000 applications between clustered servers

    All application-related registry entries are mirrored and dynamically updated when they change on either server


Maintenance Without Downtime

    Move resources between clustered servers using an easy drag-and-drop interface

    End-users retain continuous access to the server


Automatic Application Monitoring and Repair

    Routine server maintenance takes place without losing network productivity


Bi-Directional Failover

    Either node can take over the functions and identity of the failed server

    Nodes do not sacrifice their own identity during failover process


Hardware Independence

    Matching hardware or software configurations are not required

    Uses TCP/IP protocols and industry-standard network cards for mirroring traffic between clustered servers



Requirements

Co-StandbyServer NT:

Two Intel-based servers. The hardware in each does not need to be identical but it should be as similar in RAM, processor and disk technology as possible.

30 MB of free space on the system hard disk for the Co-Standby Server files on each server.

An active/active configuration requires a minimum of two additional disks (total of three) per server as seen by Windows NT Disk Administrator.

An active/passive configuration requires at least one additional disk (total of two) per server as seen by Windows NT Disk Administrator.


Co-StandbyServer 2000:

Two Intel-based servers with 133 MHz or higher Pentium-compatible CPU.

256 MB of RAM recommended minimum (128 MB minimum supported; 8 GB maximum).

Windows 2000 Server/Advanced Server

30 MB free disk space

Additional network cards in each machine.