Perform the following on your primary server:
- Select Edit > Server > Create Resource Hierarchy.
- The “Select Recovery Kit” dialog appears. Select the DB2 Database option from the drop down list.
Click Next to continue.
CAUTION: If you click the Cancel button at any time during the sequence of creating your hierarchy, LifeKeeper will cancel the entire creation process.
- The “Switchback Type” dialog appears. The switchback type determines how the DB2 resource will be switched back to the primary server when it becomes in-service (active) on the backup server following a failover. Switchback types are either intelligent or automatic. Intelligent switchback requires administrative intervention to switch the resource back to the primary server while automatic switchback occurs as soon as the primary server is back on line and reestablishes LifeKeeper communication paths.
Click Next to continue.
- The “Server” dialog appears. Select the name of the server where the DB2 resource will be created (typically this is your primary server). All servers in your cluster are included in the drop down list box.
Click Next to continue.
- The “DB2 Instance” dialog appears. Select or enter the name of the DB2 instance that is being protected.
Click Next to continue.
- An information box appears displaying information regarding the instance detected.
Click Continue.
- The “Database Tag” dialog appears. This dialog is populated automatically with a unique tag name for the new DB2 database resource instance.
Click Create to continue.
- An information box appears indicating the start of the hierarchy creation.
Click Next to continue.
- An information box appears announcing the successful creation of your DB2 resource hierarchy. You must Extend the hierarchy to another server in your cluster in order to place it under LifeKeeper protection.
Click Continue to extend the resource.
Click Cancel if you wish to extend your resource at another time.
- Click Done to exit the Create Resource Hierarchy menu selection.
このトピックへフィードバック