Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
 Continentalclusters Version A.06.00 Release Notes: > Chapter 1 Continentalclusters Version A.06.00 Release Notes

What’s In this Version
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

spacerspacerspacer
spacer
spacer
  		 
 

Continentalclusters employs semi-automatic failover of Serviceguard packages from one cluster to another following a cluster event that indicates serious disruption of service on one of the clusters. The product consists of a set of configuration, management commands, and a set of daemons that monitors and sends notification of cluster events.

The A.06.00 version includes the following enhancement:

  • Recovery of application packages configured with Veritas Cluster File System (CFS) or Veritas Cluster Volume Manager (CVM) version 4.1.

Continentalclusters Product Features

The Continentalclusters product has the following basic features:

  • Continentalclusters works with any type of data replication. A set of guidelines for integrating your data replication technology can be found in Chapter 4 of the Designing Disaster Tolerant HA Clusters Using Metrocluster and Continentalclusters user’s guide on: www.docs.hp.com -> High Availability -> Continentalclusters

    Continentalcluster provides a pre-integrated data replication solution using HP StorageWorks Continuous Access XP, Continuous Access EVA or EMC SRDF with the separately purchased products Metrocluster Continuous Access XP, Metrocluster Continuous Access EVA, and Metrocluster with EMC SRDF. An alternative to using the pre-integrated data replication solution a customer-selected data replication solution can be chosen by following the integration guidelines.

  • A recovery pair in a Continentalclusters consists of one primary cluster and one recovery cluster. One or more recovery pairs can be configured in a continental cluster with a common recovery cluster. Failover of a specific package occurs in one direction from the primary cluster to the recovery cluster. Each data center can serve as both primary and recovery cluster for different packages. In the cascading failover configuration, the primary cluster can be a metropolitan cluster using EMC SRDF or Continuous Access XP.

  • Logical data replication is also possible using the Oracle Standby Database. Template files and additional information are included in the Oracle Standby Database portion of the Enterprise Cluster Master Toolkit product (a separately purchased product). Other customer-selected logical data replication solutions can be implemented as well.

  • Cluster monitoring is carried out over LAN or WAN connections. Use any LAN or WAN connection; however, some data replication methods may require high speed connections such as T1, T3, E3/ES or ATM leased lines or switched lines.

NOTE: Continentalclusters can co-exist with the Advanced Tape Services (ATS) feature of Serviceguard. However, an ATS package must not be configured as a Continentalclusters package. With ATS, a single tape drive (or set of tape drives) is shared between two nodes within a cluster of up to four nodes. All of the tape drives are located within a single data center. If the power were to be lost, the tape drives would not be accessible even if the package were to be failed over to the other data center with a Continentalclusters package. Therefore, using ATS in a Continentalclusters package is not practical.

Support for Cluster File System and Cluster Volume Manager Recovery

Continentalclusters environment now supports recovering applications running as Serviceguard packages that use Veritas Cluster File System (CFS) 4.1 or Veritas Cluster Volume Manager (CVM) 4.1 from Symantec for storage management. The application package must have dependencies defined with the corresponding CFS Mount Point Multi-node package (MNP) or CVM Disk Group MNP. This feature is implemented using the /etc/cmconcl/ccrac/ccrac.config file.

Prior to Continentalcluster A.06.00, the ccrac.config file was used for Oracle RAC configurations with SLVM or CVM 3.5 for storage management. Starting with Continentalcluster A.06.00, the ccrac.config file can also be used to configure Oracle RAC configuration with CVM 4.1 or CFS 4.1 for storage management. In addition, as a workaround, the ccrac.config file can be used to configure single instance application with CVM 4.1 and CFS 4.1. For more information on configuring single instance applications using CFS or CVM, in Continentalclusters, refer to the Configuring Single Instance Applications in CFS/CVM Environments in Continentalclusters whitepaper, available at

www.docs.hp.com

This feature requires HP-UX 11i v2 and the selected HP Serviceguard Storage Management Suite bundle which includes Serviceguard A.11.17, CVM or CFS 4.1 support, and SGeRAC A.11.17 (if you need to configure Oracle RAC).

IMPORTANT: This feature is not supported in HP StorageWorks EVA disk array based replication environment.

Other Changes

Following are the other changes in this release:

  • If /etc/cmconcl/ccrac/ccrac.config file is configured, you must specify the CCRAC_CLUSTER parameter for every recovery pair in the ccrac.config file. If you do not specify this parameter, the recovery process does not complete and the following error message is displayed:

    Cluster name is not specified as a set.

  • When using TEXTLOG type notification, you must specify the destination log file in the monitoring definition under /var/opt/resmon/log.

    If you specify any other location for logging, the following error message appears:

    The target after textlog ““ is not valid.

    Please specify a file under /var/opt/resmon/log directory.

    If you upgraded Continentalclusters but are still using the old configuration file, the TEXTLOG location is still specified as /var/adm/cmconcl. As a result, the following error message appears:

    The file path “s” specified for textlog is invalid.

    The destination file must be under /var/opt/resmon/log directory. Please change the path and restart the ccmon package.

  • The default eventlog is changed to /var/opt/resmon/log/cc/eventlog. Prior to Continentalclusters A.06.00, this eventlog was under /var/adm/cmconcl/eventlog.

  • When using CVM, the CVM activation must be done through the CVM Disk group MNP and the application package must be dependent on all its corresponding CVM Disk Group MNPs. The previous method of configuring CVM disk groups in the application package control script is not supported.

    IMPORTANT: The 3 Data Center functionality provided by the HP StorageWorks XP disk arrays is not supported with CFS or CVM configurations in Continentalclusters.


Announcements
  		 


Compatibility Information and Installation Requirements  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.