User Guide

➤ To recover provisioning data after a Native Directory crash:

1 Verify that the Native Directory service (Windows) or process (UNIX) is not running.

2 Open a command prompt (Windows) or console (UNIX) window.

3 Navigate to

<openLDAP_Home>\bdb\bin

. For example,

<Hyperion_Home>\SharedServices

\<HSS_version>

\openLDAP\bdb\bin (Windows) or <Hyperion_Home>/SharedServices/

<HSS_version>/openLDAP/bdb/bin

(UNIX)

4 Run the db_recover utility, using the following command:

db_recover –h <

Path_Native_Directory_data_file

For example, db_recover –h ../../var/openldap-data

Where openldap-data indicates the name of Native Directory data file.

5 Monitor the utility to ensure that it runs successfully.

6 Restart the Hyperion S9 OpenLDAP service or process.

7 On the application server, restart Shared Services.

Setting Up Native Directory for High Availability and Failover

Native Directory high availability and failover can be achieved through various scenarios.

● “Out of the Box Deployment” on page 94

● “Cold Standby Deployment” on page 96

● “Hot Standby Deployment” on page 98

Out of the Box Deployment

The out of the box failover scenario involves establishing a master-slave relationship between

two fully synchronized installations of Native Directory running on separate machines.

➤ To set up a replicated Native Directory environment:

1 Install and configure Shared Services on two server machines (for example, machine1 and machine2).

See the Hyperion Shared Services Installation Guide for instructions.

Managing Native Directory