Novell Doc: OES 1 - Monitoring the Health of VLDB Services

20.8 Monitoring the Health of VLDB Services

To find the replica sites for a management context and view the status of VLDB services on them:

In iManager, select Distributed File Services>Manage Replica Sites.
Select any server with an NSS volume that is located in the DFS management context that you want to manage.

This action locates the DFS management context, lists the replica servers in that context that host its VLDB services, and reports the current status of the VLDB services on them.
- Name: The distinguished name of the O-level or OU-level container in the eDirectory tree that defines the selected DFS management context.
- Replica Site: The distinguished names of the servers that host an instance of VLDB services for the selected management context. A management context can have 1 or 2 replica sites. The server can be at any level within the specified container that is not controlled by a lower-level management context.
- State: The status of currently running VLDB services on the replica site. See the table below for details.
- Version: The build version of the VLDB services module that is running on the replica site.

The following table explains the status conditions for VLDB services and possible actions:

Table 20-4 State of VLDB Services

State	Icon	Description	Possible Actions
Running		VLDB services are loaded and running.	Details, Repair, or Stop actions are possible.
Stopped		VLDB services are not loaded. VLDB services are stopped. After a VLDB repair completes successfully, the services should automatically load and activate. If the activation fails, the VLDB service goes into a Stopped state.	Activate, Details, Repair, or Start actions are possible.
Working		The VLDB services are initializing; please wait. A VLDB repair is in progress; please wait.	After you start or activate VLDB services, please wait until the replica reports a different state to perform other tasks on that replica. If you interrupt a VLDB repair while it is in progress, you must start over. It does not pick up where it left off.
Site Connection Failed		iManager could not connect to the replica site. The cause is unknown. This might occur if the connection path, server, or volume are offline at that time.	Use standard methods to verify the health of the replica server and paths in-between the iManager server and the replica server.
Unknown		The reported state from the replica site is either null or a state that iManager does not recognize.	Use standard methods to verify the health of the replica server.