Perform the following steps on the primary server:
- On the Edit menu, select Server, then Create Resource Hierarchy.
The Create Resource Wizard dialog will appear.
- Select SAP ASE Database from the drop-down list and click Next.
- You will be prompted for the following information. When the Back button is active in any of the dialog boxes, you can go back to the previous dialog box. This is helpful should you encounter any error requiring you to correct the previously entered information. You may click Cancel at any time to cancel the entire creation process.
- Click Next. The Create Resource Wizard will then create your SAP ASE resource hierarchy. LifeKeeper will validate the data entered. If LifeKeeper detects a problem, an error message will appear in the information box.
| Server | Select the LifeKeeper server where the SAP ASE resource is to be created. |
| Switchback Type | Choose either intelligent or automatic. This determines how the SAP ASE resource will be switched back to the primary server after it comes in-service (active) on the backup server following a failover. 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. Note: The switchback strategy must match that of the dependent resources to be used by the SAP ASE resource. |
| SAP Install Directory | This field is used to specify the installation location of the SAP ASE product. You may type in another directory path. The valid characters allowed for the pathname are letters, digits and the following special characters: – _ . / |
| SAP Instance Directory | This field is used to specify the directory path that contains the SAP data directory. The data directory will typically contain the ASE-<version>/RUN_* files for the instance. |
| SAP Instance | This field contains by default the name of the first SAP instance found on the system, for which no LifeKeeper hierarchy exists. The drop down list shows other SAP instances that may be available on your LifeKeeper server. This field is used to specify the SAP ASE Database instance that will be placed under LifeKeeper protection. The specified instance must exist and must be running. |
| SAP Username | This field is used to enter the user name for the SAP System Administrator. By default the user name is sa. This System Administrator must have login and full privileges on any database on the SAP Adaptive Server being protected. |
| SAP Login Password | This field is used to specify the password for the SAP System Administrator. |
| SAP Backup Server | This field is used to specify the SAP Backup server for the specified Adaptive Server instance. This SAP Backup will be placed under LifeKeeper protection. The user may select ‘none’ if the SAP Backup Server does not need to be included under LifeKeeper protection. |
| SAP ASE Database Tag | This is a unique tag name for the new SAP ASE database resource on the primary server. The default tag name consists of the word sybase followed by the name of the Adaptive Server instance. You may type in another unique tag name. The valid characters allowed for the tag are letters, digits, and the following special characters: – _ . / |
- You should see a message indicating that you have successfully created a SAP ASE resource hierarchy, and you must extend that hierarchy to another server in your cluster to achieve failover protection. Click Next.
- Click Continue. LifeKeeper will then launch the Pre-extend Wizard. Refer to Step 2 under Extending a SAP ASE Resource Hierarchy for details on how to extend your resource hierarchy to another server.
Post your comment on this topic.