Monday, March 30, 2009
Monday, March 23, 2009
Friday, March 13, 2009
Server Fast restart in Lotus Domino 8?
What is Server Fast restart in Lotus Domino 8?
When a Domino outage occurs, Fast Restart allows a new Domino instance to start while NSD diagnostics are being run on the initial Domino server instance. When diagnostics are completed the initial Domino server instance is automatically terminated. In the current release, Server Fast Restart is only available on AIX and Solaris versions of the Domino server.
How does Server Fast Restart work?
All files and connections in use by the initial Domino instance are closed but processes and shared memory remain active until NSD diagnostics are completed. The new instance will be started by a Server Fast Restart process called faultmon.
When the initial Domino instance fails, it will send a message to a monitoring program called faultmon. faultmon receives the message over a named pipe, and restarts Domino. faultmon has two options for restarting the new Domino instance; the default option is to start the new Domino instance in the background, while the second option allows the user to specify a script to start the new Domino instance.
For More information visit IBM Technote
When a Domino outage occurs, Fast Restart allows a new Domino instance to start while NSD diagnostics are being run on the initial Domino server instance. When diagnostics are completed the initial Domino server instance is automatically terminated. In the current release, Server Fast Restart is only available on AIX and Solaris versions of the Domino server.
How does Server Fast Restart work?
All files and connections in use by the initial Domino instance are closed but processes and shared memory remain active until NSD diagnostics are completed. The new instance will be started by a Server Fast Restart process called faultmon.
When the initial Domino instance fails, it will send a message to a monitoring program called faultmon. faultmon receives the message over a named pipe, and restarts Domino. faultmon has two options for restarting the new Domino instance; the default option is to start the new Domino instance in the background, while the second option allows the user to specify a script to start the new Domino instance.
For More information visit IBM Technote
Tuesday, March 10, 2009
How to rebuild the Domain Index for the Domino server
our Lotus® Domino® server's Domain Index is
(1) not working properly
(2) corrupted
(3) otherwise needs to be recreated.
How is this done?
Answer
1. From the Admin client, select File -> Database -> Properties -> Design tab and check the following properties for the databases to include in the index (this should already be in place for databases previously included in Domain catalog):
- List in Database Catalog
- Include in multi-database indexing
2. At the Windows Domino server console type:
tell domidx q
3. In Windows Explorer, navigate to your Lotus\Domino\Data directory and delete ftdomain.di directory.
4. From the Admin client, delete the catalog.nsf from the Files view.
5. Restart the Domino Server.
6. At the Windows Domino server prompt, type:
load catalog
7. From the Admin client, open the new catalog.nsf that has been created. Verify that the database is listed in the Databases -> by Server view with the Multi-database Indexed property marked Yes.
8. In the Server document, change Server Tasks -> Domain Indexer -> Repeat Interval of: to reflect a short indexing interval (this will speed up the Index rebuild). Close and save the document.
9. At the Windows Domino server prompt, type:
show schedule
10. Verify that the Domain Indexer schedule has been updated.
11. From the Admin client, open the new catalog.nsf and monitor the Domain Indexer Status -> By Server view, to verify that the database is indexed.
"The Domain Index can take a considerable amount of time to create, and its creation is resource intensive. As a result, it should not be deleted casually. When you build the initial Domain Index, it is important to free up as many resources on the Domain Search server as possible. Memory and CPU are taxed heavily during this process. By eliminating extraneous, unnecessary server tasks, you can increase the available resources for building the index."
(1) not working properly
(2) corrupted
(3) otherwise needs to be recreated.
How is this done?
Answer
1. From the Admin client, select File -> Database -> Properties -> Design tab and check the following properties for the databases to include in the index (this should already be in place for databases previously included in Domain catalog):
- List in Database Catalog
- Include in multi-database indexing
2. At the Windows Domino server console type:
tell domidx q
3. In Windows Explorer, navigate to your Lotus\Domino\Data directory and delete ftdomain.di directory.
4. From the Admin client, delete the catalog.nsf from the Files view.
5. Restart the Domino Server.
6. At the Windows Domino server prompt, type:
load catalog
7. From the Admin client, open the new catalog.nsf that has been created. Verify that the database is listed in the Databases -> by Server view with the Multi-database Indexed property marked Yes.
8. In the Server document, change Server Tasks -> Domain Indexer -> Repeat Interval of: to reflect a short indexing interval (this will speed up the Index rebuild). Close and save the document.
9. At the Windows Domino server prompt, type:
show schedule
10. Verify that the Domain Indexer schedule has been updated.
11. From the Admin client, open the new catalog.nsf and monitor the Domain Indexer Status -> By Server view, to verify that the database is indexed.
"The Domain Index can take a considerable amount of time to create, and its creation is resource intensive. As a result, it should not be deleted casually. When you build the initial Domain Index, it is important to free up as many resources on the Domain Search server as possible. Memory and CPU are taxed heavily during this process. By eliminating extraneous, unnecessary server tasks, you can increase the available resources for building the index."
Subscribe to:
Posts (Atom)