Progress
Version 9
Product Update Bulletin
Required Cluster Components
Figure P–1 shows the components of a typical cluster. For Failover Clusters, Progress 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 P–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 Progress into the cluster not only by making use of the pre-existing cluster manager software, but by also augmenting Progress feature functionality. When you use Clusters, you no longer use the PROSERVE or PROSHUT commands and their equivalents, you use PROCLUSTER to start and stop the database so that the operating system cluster manager software knows about Progress, and will handle it properly in the event of a fail over. See the "The PROCLUSTER Command-line Interface" for information on using PROCLUSTER.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |