Progress
Database Administration
Guide and Reference
Progress Database Server Considerations and Configuration
On the server side, think of the cluster as one node. Although from a management viewpoint, you will still have nodes onto which you must install, configure, and update the product.
The original setup is the most time consuming because you must install, configure, and maintain the Progress environment in addition to updating and maintaining the TCP/IP
services
file on each node. However, from a user’s or an application’s viewpoint there is only one host and one service.For TCP/IP, the service name you associate with your database server is a name that will be used cluster-wide. Therefore, you must edit the TCP/IP
services
file on both nodes and also add the same service name and socket number on each node. You must use the same names and numbers, because in a failover, the secondary node starts the database server and your clients must reconnect to your service by node and service number.After Progress is installed on both nodes, you must determine which cluster shared disks will hold your database. Next, use the Cluster Administrator to create a new Progress Failover Group. Place the stored disk objects into the group. Doing this places the disks online on the node that you have chosen to be the primary node. From the primary node, use the Progress Database Administration tools to create or copy a database onto the shared disks.
Next, use ProControl to configure the database server information, using a cluster TCP/IP alias for the Host (-
H
) parameter name and the “cluster-wide” service name from theservices
file for the Service (-S
) parameter name.You must duplicate this effort on both nodes, so you should have a ProControl screen visible on both nodes so you can be sure the duplication is exact.
Within ProControl you can choose to have the database server started automatically or not. If you have only one cluster shared disk, you should allow ProControl to start the database servers automatically when ProControl starts ProService.
However, if you have multiple cluster shared disks and you have chosen to have each node act as the primary node for specific database servers, this approach is not recommended. At this time, ProControl only knows three commands, Start, Stop, and Status. Therefore, if you have database servers running on both nodes and if one node fails and those database servers failover to the secondary node, you would have to Stop and Start ProControl in order to start the automatic database server startup. Doing this disrupts current users of the secondary node.
In the single cluster shared disk model, ProControl should not be already running on the nonprimary node. So, in a failover, you start ProControl with automatic database server startup set and your database servers will be started for you.
Continue creating Failover Groups and adding/modifying ProControl for each database server on each shared disk.
After this is done, use the Cluster Administrator to create Script Failover Objects to be placed in your Progress Failover Groups. These script objects can be either actual scripts or the direct command-line interface into ProControl. In either case, you must use the ProControl command-line interface. The following sections describe the command-line interface and give you some examples for scripts.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |