Release 10.1A: OpenEdge Data Management:
Database Administration

> ## Required cluster components

> Figure 11–1 shows the components of a typical cluster. For Failover Clusters, OpenEdge requires at least a two-host configuration utilizing a common storage architecture such as SCSI, and systems with redundant network and cluster interconnections. Your database must reside on one or more shared devices, also known as common storage.

> Figure 11–1: Cluster component configuration

> If the database structure changes or the database is moved to a new common storage device, the Clusters command-line interface, PROCLUSTER, makes it very easy to ensure that the database is still protected if a fail over event occurs. If the shared device in the cluster needs to change, use PROCLUSTER to stop the database and enable it on the new shared device once it is moved. If extents are added, Clusters provides for making this change, and you only need to start the database once the changes are automatically applied.

> Clusters integrates OpenEdge into the operating system cluster not only by making use of the pre-existing cluster manager software, but by also augmenting OpenEdge feature functionality. When you enable a database for failover, the master block is updated to reflect this fact. When you have a cluster-enabled or cluster-protected database, commands are then funneled through the underlying `pscluster` executable to the operating system cluster manager. Figure 11–2 shows this relationship. The cluster manager software must know about OpenEdge to handle it properly in the event of a failover. See the "Using the PROCLUSTER command-line interface" section for information on using PROCLUSTER to cluster-enable a database.

> Figure 11–2: Relationship between database commands and utilities and the cluster manager

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095