Shop News Jobs WorldWide Contact Us Search C-Byte Home Page Big Open Systems That Work
      Data Center Ready/  
C-Byte Delivers High-Availability

High Availability Whitepapers  

High Availability

High Availability in Practice
Here are three high-availability approaches, real-world examples of successful installations by C-Byte. While the following mainly describes the architecture of each example, please keep in mind that each of these customers recognized the value and implemented the people and process components of their high availability solutions.

Single Node Availability
Used as a centralized database server running a custom application, this system regularly averages 99.93% availability for months at a time. Users connect via a number of different desktop devices. A separate, duplicate machine is maintained as a hot spare for new hardware components and for testing new versions of system and application software. This enables the staff to restore service as soon as possible rather than troubleshoot a problem with the system down.

Product (Technology): C-Byte systems are standard. Inherently reliable, the basic system mitigates some failures rapidly and allows easy online repair for others. CPU failures, for example, immediately halt the system to prevent the errors from propagating. When the system reboots, the failed components are automatically configured out of the system.

Clustered Node Availability
Another C-Byte customer—whose success depends on fast delivery and low overhead—maintains its core operational manufacturing system on a C-Byte cluster.

This system achieves a 99.98% availability through the replication of certain components and the excellent support of a well-trained staff using policies and procedures developed jointly with C-Byte.

Product (Technology): The computing system is a three-node C-Byte cluster in a data center supporting manufacturing users connected via SQLNet over TCP/IP. They use a dual-ring FDDI connection between their applications servers and RDBMS servers for network redundancy; the cluster provides data server integrity. The production environment is replicated in a lab environment at C-Byte headquarters where application and systems software testing is completed before installation on the production machines. The lab is also used to validate operational procedures in a controlled environment. A disaster recovery machine sits at a customer site in the Eastern U.S., periodically replicating the database over a high-speed network connection.

Back to Top

Replicated Node Availability
In this example, a pair of clusters separated by several hundred miles, replicate data to protect against data center disasters. Each serves its own user community, but can pick up the additional load for the other if one fails.

Product (Technology): The two C-Byte 2-node clusters are essentially identical. Users connect to application servers running a custom application. The application servers, in turn, connect to a DBMS running on one of the clusters via a wide area network. The databases are replicated with Oracle Symmetric Replication, a facility that allows two (or more) Oracle databases to stay in close synchronization even though they are completely separate. This design achieves failover in approximately 90 seconds with no transaction loss and can reconnect to the other site in less than 60 seconds when necessary.

Previous | Table of Contents


C-Byte Company, Inc.
  Good Morning it is 4:09 am in Las Vegas, Nevada, United States.    E-mail This Page  |  Digg This  |  Facebook  |  Twitter  |  Delicious

Ask Us a Question - Call Inside US 1-800-393-5804, Outside US 1-403-770-7818, or Contact Us
Copyright © 1989 - 2017 C-Byte Company, Inc.  ::  C-Byte Privacy Statement   ::   P.R.O. Program ::  RSS 1.0 Feed
This site is protected by copyright and trade mark laws under U.S. and International law. All rights reserved.
SecurityGroup Audits Systems at C-Byte Tackling...