Lotus Domino Administrator 8.5 Help - Specifying database and server locations for resource balancing

PERFORMANCE

Specifying database and server locations for resource balancing
Use the Server Profile Options dialog box to specify which databases and servers will be searched for activity data, and whether to use cached data. Because Activity Trends data changes only on a daily basis, caching data is highly recommended to increase system performance by avoiding a read across a potentially slow network. The first time a server's data is read, the data is cached and remains available. For example, if you read and then delete a server's activity data and later add the same server, the in-memory data is used.

You can open the Server Profile Options dialog box from the Activity Trends menu or by clicking the Server Profile Options button.

To specify locations

1. From the IBM® Lotus® Domino® Administrator, click the Server - Performance tab.

2. Select the Activity Trends - Resource Balancing view.

3. Choose Resource Balancing - Options to open the Server Profile Options dialog box.

4. Click General.

5. Under Activity Data Search Order, choose one or both:

Search Local Activity Databases -- To search the Activity databases (ACTIVITY.NSF) on each server on which Activity Trends is enabled.
Search Activity Data Proxy Servers -- To use servers that contain activity data copied or replicated from another server. Enter the name of the servers that have the proxy data. Activity Trends Collector proxy data options are configured in the Configuration Settings document in the Domino Directory.

6. Under Activity Trends Data Cache for the field "Enable caching of activity data," do one:

Check Yes (default) -- To cache Activity Trends data. When data is cached, if the data for a server has already been retrieved (even though the server may not appear in any of the server lists), the cached data is used.
Uncheck Yes -- To gather Activity Trends data every time a new server is added. Data from servers that are removed is discarded immediately, and new data is retrieved.

7. For the field "Cache expiration time out," enter the number of minutes that data remains cached after the server’s data is first retrieved. The default is 360 minutes.

8. Choose one of the following to set location defaults. These defaults apply only to items on the current tab.

Use Defaults -- To revert to previously stored custom defaults.
Save as Defaults -- To save a custom set of defaults and override the system defaults.
Reset Defaults -- To revert to the system defaults.

Related topics

Setting up Activity Trends

Setting primary and secondary resource-balancing goals

Specifying which databases can move during resource balancing

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary