Show TOC

 Database HA / Failover: OS Level Cluster (Cold Standby) Locate this document in the navigation structure

 

In the cold standby setup of SAP Sybase ASE, you use two database servers, a primary database server and a standby database server ("cold standby"). The database is located on a disk that is shared by the two database servers. Since the database servers share a disk, this setup is sometimes also referred to as "shared disk scenario". The cold standby setup uses operating system clustering to ensure high availability. The secondary ASE host is started when the primary host is not available. It takes over the complete database from the shared disk. The database software and configuration files can either be installed on the shared disk or on a local disk if the access path is the same on all cluster nodes. The advantage of the local software and configuration installation is that it is possible to configure ASE differently on each cluster node and to reduce database downtime in case of software maintenance. This solution requires the same hardware for the primary and secondary hosts to avoid a mismatch in the configuration of the Adaptive Server.

This graphic is explained in the accompanying text.

OS Level Cluster – Cold Standby

Challenges:

  • System not available during failover and database recovery

  • In-flight transactions are lost

  • Risk of I/O level corruption

  • Database software maintenance requires downtime

The following partner solutions support this scenario:

Platform:

High Availability Offering:

All OS Platforms

Symantec VCS: White Paper available for each supported platform

(http://eval.symantec.com/mktginfo/enterprise/white_papers/b-ha_for_sybase_db_with_vcs_hadr_WP_14179510.en-us.pdf)

Red Hat Cluster Suite

Solution based on Open Cluster

(https://www.redhat.com/resourcelibrary/reference-architectures/Deploying-Highly-Available-SAP-Servers-using-Red-Hat-Clustering)

In collaboration with Red Hat, SAP has started to develop the official integration of Sybase ASE.

HP Serviceguard Solutions for HP-UX

The HP Serviceguard Extension for SAP B.05.10 on HP-UX 11iv3 supports easy-deployment, modular-style SAP NetWeaver clusters with SAP Sybase 15.7 ASE RDBMS on HP Integrity servers after installation of patch PHSS_42569 or any superseding patch. For general information about HP's high availability clustering solutions for SAP, refer to: www.hp.com/go/sgesap. For technical information, including an up-to-date support matrix, refer to the latest release note documents available from Hewlett Packard on:

http://www.hp.com/go/hpux-SGeSAP-docs

http://www.hp.com/go/hpux-serviceguard-docs

Microsoft

MS Cluster Solution support

SAP installations for SAP Sybase ASE include HA installation options for the Microsoft Cluster environment.

SUSE Linux Cluster Solution

No support for Sybase ASE 15.7 yet, but customers can add their own live check scripts for SAP Sybase ASE.

In collaboration with Novel, SAP has started to develop the official integration of SAP Sybase ASE. For more information, refer to the white paper "SAP Made High-Available on SUSE Linux Enterprise Server for SAP Applications" on http://www.novell.com/sap.

HP Serviceguard Solutions for Linux

Serviceguard extension for SAP for Linux

SGeSAP/LX automates and accelerates SAP application failover:

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?lang=en=us=101=10008=SupportManual=64255=18964=4181640