Solutions

SageGuard

Thinking about high availability solutions for your production environment?  Consider SageGuard for your enterprise class database clustering and disaster recovery needs utilizing Oracle Data Guard.

SageGuard Datasheet PDF

 

SageGuard Features

 Feature
1Automated detection of a failed primary database with automated failover capability.
2Disaster Recovery (DR) support.
3Logical data corruption protection.
4Operating System (OS) cluster virtual IP support.
5Process maintenance and extended monitoring.
6Automated creation of data guard databases.
7Small footprint.
8Open API.
9SageTools compatible.

Supported Platforms

  • Linux Red Hat
  • HP-UX
  • Solaris
  • AIX

SageGuard and DR

A typical Sage Guard environment would consist of at least two servers running one primary database and one standby database (Data Guard database). An optional DR database could also be utilized in case of a true disaster (e.g. the complete loss of a data center). The servers must have the same O/S architecture, though they do not have to be identical hardware. For example, the standby database server could be sized with less capacity than the production server.

SageGuard and Recovery

A dedicated network link, i.e. a crossover link, is strongly recommended between the two servers participating in the failover cluster to ensure that the "who-is-the-master status" can be properly communicated in case of a network link failure on the primary server. This also prevents the potential situation of two different hosts having the same IP (a.k.a. "split-brain"), resulting in the misrouting of database traffic. To be able to recover from a logical corruption, Sage Guard can also be utilized to maintain an additional standby database. This allows for intentional transactional latency from the primary server, reducing the possibility of data corruption and providing for point-in-time recovery, prior to data corruption. Sage Guard seamlessly brings the standby database online in case of a primary database failure, allowing your users to continue work with little or no data loss. Using Sage Guard with a second standby database on a time-differential provides a simple way to recover from data corruption.

 

SageGuard Overview

Sage Guard extends the functionality of Oracle Data Guard and automates the operation of a complex Data Guard environment and greatly reduces maintenance and total cost of ownership. Sage Guard offers the ability to keep databases running on different servers synchronized for the purpose of redundancy and/or for the purpose of running off-line reports, data warehouse extracts, etc. In addition, Sage Guard offers O/S Clustering functionality, such as Cluster IP Address Failover.  Built on top of Oracle's DataGuard, Sage Guard provides many clustering benefits without the drawbacks of high cost and single point-of-failure (e.g. storage.)

SageGuard Advantage

Because SageGuard was developed as a Database Aware cluster, the advantage over traditional O/S clusters is that it knows the state of the database when making failover decisions. This offers a more robust alternative to traditional O/S clusters. Sage Guard can also be integrated with an existing O/S clustering solution through the use of an open API. The SageLogix Database Architecture team built and recognized the need for Sage Guard based on years of experience working with Standby and Data Guard Databases and from SageLogix Enterprise customer feedback.