QuestionOccasionally (typically after a server crash or backup application problem), archive-style transaction logs (.txn files) are not deleted or reused on a Lotus Domino server. How can these be cleaned up?AnswerImportant note: The procedure below is safe for Domino, but does not take into account the state of existing database backups. A full backup should be performed before taking this action. All database DBIID's will be changed. Consult your backup application documentation for the ramifications of changing DBIID's.1. Disable transaction logging for this server. This is done from the Domino Administration client by: Open the server's Domino directory (names.nsf). Locate this server's Server document. Edit the Server document -> Transactional Logging tab -> Basics section. Change the "Transactional logging" field to Disabled.2. Stop the Domino server and confirm that all Domino tasks have shut down by checking the Domino console or log. Depending on the OS, use the appropriate tools to verify the server shutdown cleanly.3. Start the Domino server and observe the message, "Transactional logging being disabled after this restart". Also notice that the task Domino uses for transaction logging (NLOGASIO on Windows, LOGASIO on other platforms) does not load and is not in the Task Manager list.4. From the operating system (OS), rename the transaction log directory. There should be no errors when doing this, as Domino is not using any of the files in the log directory any more.5. Stop the Domino server and confirm that all Domino tasks have shut down by checking the Domino console or log.6. Start the Domino server.7. Edit the Server document again and set the "Transactional logging" field back to Enabled. Save the Server document.8. Stop the Domino server and confirm that all Domino tasks have shut down by checking the Windows Task Manager.9. Start the Domino server and observe the message, "Please wait, creating new transaction logs in directory..."10. Notice that a consistency check is run on any open databases and a new DBIID is assigned. This occurs on each database as it is opened.11. Delete the old log directory (previously renamed).

Restore Data - Lotus Notes/Domino Server - How ToTopics|How To|Full System Restore|Related Topics

Perform Cross-Machine Restore of DatabasesPerform Cross-Machine Restore of Databases and Transaction Logs

Perform Cross-Machine Restore of DatabasesThe Lotus Notes DatabaseiDataAgent restores database backups as follows: If the source and destination computer have a partition with the same data path then the data is restored to the common data path. If all partitions on the destination computer are different than the source computer, then the data will be restored to the first partition.No transaction logs are restored, and no transactions are replayed. Follow the procedure for this mode if: You don't want to shut down the destination server during the restore operation. The last database backup is more recent than the last transaction log backup. In this case, there is no need to restore the transaction log.Required Capability:SeeCapabilities and Permitted ActionsTo perform a database-only cross-machine restore:Follow the procedure described inBrowse and Restore. Make sure to:1. Select the appropriateDestination Computerfrom theRestore Options (General)dialog box.2. Determine the restore path to the destination computer usingRestore to Same Paths.WhenRestore to Same Pathsis selected: If the source computer and the destination computer have a partition with the same data path, the data is restored to the common data path. If all partitions on the destination computer are different than the source computer, the data will be restored to the first partition.WhenRestore to Same Pathsis de-selected: You can select anyDestination Folderon the selected destination computer.NOTES For out-of-place restores, any database can be restored to a new location while the server is running. Because this job does not restore log files, some restore options are not made available (e.g.,Change database instance id (DBIID),Change database replica id).

Perform Cross-Machine Restore of Databases and Transaction LogsThe Lotus Notes DatabaseiDataAgent restores database backups as follows: If the source computer and the destination computer have a partition with the same data path then the data is restored to the common data path. If all partitions on the destination computer are different than the source computer, then the data will be restored to the first partition.Then, log files are restored as needed and transactions are replayed. Follow one of the procedures for this mode if: You want to restore and replay transactions that took place after the last database backup. You can do a database plus transaction log restore to either an active (production) server that is an existing Notes Database client or to a new server in the CommCell. If you restore directly to an active production server, you do not have to install Domino Server or the Notes DatabaseiDataAgent. However, you must shut down the server during the restore job and make special preparations, as described in the procedure instructions. If you don't want to shut down a production server, you can restore to a new server. The new server will require installs of the Domino Server and the Notes DatabaseiDataAgent. After the cross-machine restore finishes, you can copy the recovered database(s) from the new server to the production server.Choose the appropriate procedure: Performing a Cross-Machine Restore of Databases and Transaction Logs to an Existing Domino Server Performing a Cross-Machine Restore of Databases and Transaction Logs to a New Domino Server

Performing a Cross-Machine Restore of Databases and Transaction Logs to an Existing Domino ServerRequired Capability:SeeCapabilities and Permitted ActionsTo perform a cross-machine restore of Notes databases and transaction logs to an existing Domino Server:The version of Domino Server on the computer to which you are restoring must be the same as when the backup took place, since there may be differences in the log file structures of different versions.

1. Shut down Domino Server on the destination computer.2. On the destination computer, create a directory for restored databases and a directory for restored log files. (If you prefer, you can use one directory for both.) We recommend that you create these directories outside the Domino Server data path.3. Copy the source computer's server ID file (usually namedserver.id)to the directory created for restored databaseson the destination computer. (If you can't access the file on the source computer, restore it to the destination computer from backup.)4. Rename thenotes.inifile on the destination computer (tonotes.sav, for example).The Notes client software has its ownnotes.inifile, as does each Domino Server partition. There may be multiplenotes.inifiles on the computer to which you are restoring. Make sure that you are modifying thenotes.inifile for the appropriate partition of the destination computer.

5. On the destination computer, create anotes.inifile in the same directory as the originalnotes.inifile.The content of the .ini file should be similar to the example below, with your own system information replacing sample file and directory names.If the directory for restored databases isD:\RestoredDBs,the directory for restored log files isD:\RestoredLogs, the server ID file name isserver.id, and the Domino server program files directory isC:\Lotus\Domino), the newnotes.inifile will look like this:[Notes]Directory=D:\RestoredDBsNotesProgram=C:\Lotus\DominoKeyFilename=D:\RestoredDBs\server.idTRANSLOG_Style=1TRANSLOG_Path=D:\RestoredLogsTRANSLOG_Status=1Translog_MEDIAONLY=1Be sure to add a new line (i.e., pressEnter) at the end of the file.6. Browse the backup data and select those databases that you want to restore. Select theDisaster Recovery / Media Recovery (to another machine)option and aDestination Computerin theAdvanced Restore Options (General)dialog box in addition to any other restore options that you want.7. Run the restore job and verify that it has completed successfully.If you want to copy a restored database back to the source computer (as opposed to any other server), DO NOT start Domino Server. DO NOT open the restored database. Doing so may cause the database to be assigned a new DBIID when it is opened by the Domino server on the source computer, which will necessitate a database backup. In addition, if the database is large, assigning a new DBIID will take some time.

8. Optionally, copy the restored databases to another server.(If you want to leave the databases on the computer to which they were restored, you must copy them to the data path of a Domino partition.) We recommend that you change the file extensions before copying (for example, to user01mail.xxx), then rename the files with the .nsf extension after the file copy is complete. This ensures that the server will not detect databases until they are complete and consistent.9. Delete thenotes.inifile that you created on the destination computer, and rename the original .ini file (e.g.,notes.sav) tonotes.ini.If you have copied the restored databases to another server, you can delete the directories that you created for restored databases and transaction logs.You can now restart Domino Server on the destination computer.

Performing a Cross-Machine Restore of Databases and Transaction Logs to a New Domino ServerThe version of Domino Server on the computer to which you are restoring must be the same as when the backup took place, since there may be differences in the log file structures of different versions.

To do this procedure, you must start with a computer that does not have Domino Server installed.

Required Capability:SeeCapabilities and Permitted ActionsTo perform a cross-machine restore of Notes databases and transaction logs to a new Domino Server:1. Install Lotus Domino Server and the Notes DatabaseiDataAgent on the destination computer.The version of Domino Server on the computer to which you are restoring must be the same as when the backup took place, since there may be differences in the log file structures of different versions.

2. Shut down the Domino server.3. Copy the source partition's server ID file (usually namedserver.id) to the directory on the destination computer that contains the server ID file. (If you can't access the file on the source partition, restore it to the destination computer from backup.) You may want to rename the server ID file in the destination computer first, so that you don't overwrite it. If the name of the source partition's server ID file differs from the name of the destination computer's server ID file, you must change theKeyFileNameparameter of thenotes.inifile on the destination computer to match the source computer's server ID file name.4. Add the following line to thenotes.inifile of the destination computer:TRANSLOG_MEDIAONLY=1If you add this line at the end of thenotes.inifile, be sure to add a new line (i.e., pressEnter) after this line.5. Make sure that the transaction log directory is clean. (You can find the path to the log directory by checking theTRANSLOG_Pathparameter in the partition'snotes.inifile. If this is a relative path, it must be appended to the path listed in theDirectoryparameter.) Delete any remaining log files and the log control file. Alternately, you can delete the log directory altogether. In this case, the restore process creates a new log directory.6. Browse the backup data and select those databases that you want to restore. Select theDisaster Recovery / Media Recovery (to another machine)option and aDestination Computerin theAdvanced Restore Options (General)dialog box in addition to any other restore options that you want.7. Run the restore job and verify that it has completed successfully.If you want to copy a restored database back to the source computer (as opposed to any other server), DO NOT start Domino Server. DO NOT open the restored database. Doing so may cause the database to be assigned a new DBIID when it is opened by the Domino server on the source computer, which will necessitate a database backup. In addition, if the database is large, assigning a new DBIID will take some time.

8. Optionally, copy the restored databases to another server.We recommend that you change the file extensions before copying (for example, to user01mail.xxx), then rename the files with the .nsf extension after the file copy is complete. This ensures that the server will not detect databases until they are complete and consistent.Back to Top

stractSome frequently asked questions about Transactional Logging.ContentQ: How does replication work with transaction logging enabled? Does the replicator read from the transactional log for any changes that need to be replicated from the Unified Buffer Manager (UBM) or are changes committed to the NSF first before replication occurs?A: Replication is unaffected by Transactional Logging. Changes are available in the same manner as they are for un-logged databases. Changes are always read from the in-memory versions of databases when they are open and all cached changes are flushed when databases are closed.

Q: If a user is trying to read a note that has not been committed to the NSF with transactional logging enabled does the user session read the note from the transactional log, the UBM or is the note committed to the database first?

A: The note is read from the in-memory versions of databases when they are open and all cached changes are flushed when databases are closed.

Q: If something is done to change the DBIID of a database, are changes committed first before the DBIID gets changed?

A:Yes. Data is not lost. Things that change the DBIID, such as Fixup -J and Compact -B, change the DBIID because they are making database changes that are not logged. The order of operations is this:(1) Flush all in-memory changes to the database(2) Clear the DBIID and halt logging for the database(3) Make the un-logged changes(4) Flush all in-memory changes to the database(5) Assign a new DBIID and start logging changes to the database again.

Note: None of these steps can be done manually; all of them are done automatically. The one manual step is to take a new backup of the database after you see the console message "Assigning New DBIID for DB xxxx."

Q: When is it beneficial to run fixup -j?

A: Hopefully never. It would be beneficial only if the database became corrupt and you did not have a backup to roll forward from.

Q: When fixup -j is run on the entire server I notice that it assigns a new DBIID to some databases but not others. Why is this?

A: Transactional logging should reassign the DBIID's for all transactionally logged databases. Fixup -j will run against unlogged as well as logged databases, so the logging status should be checked of the databases that didn't have a DBIID re-assigned to them and validate that it is not logged.

Q: If the DBIID of a database has changed for some reason, how is the database withthe old DBIID and the new DBIID incorporated?

A: There is no intermixing. You must re-backup a database when the DBIID changes. Note: there is no relation to the REPLICAID or DBID.

Q: If a server panics and upon restart Domino automatically performs database recovery, will a large amount of data be lost or is the loss minimal?

A: All cached info will be re-applied and only partial API calls will be backed out. That is, if the server was in the middle of a NoteUpdate call, that would get undone. You will see EVERY NOTE you ever added (and the API call returned) with no loss of data. The Transactional Log is written directly, with no file cache (i.e. all writes are "committed" and writes are done to the Transactional Log at least after each transaction or API call).

Q: If only one database on a server becomes corrupt is it possible to restore only this one database from the transactional log or will the entire transactional log need to be replayed?

A: Transactional Logging restores only the database(s) that need to be. The whole log from the time of the backup must be replayed but only records pertaining to the databases being recovered will be processed.

Q: What is the control file used for?

A: It is used by the logger subsystem to know the state of the log files. The logging subsystem is all of the code in nsf\logger, where some of it runs in the "application" process, meaning in the process that makes logging calls (ex. the server, etc).

Q: If there are any databases or directory links on the server, will these databases be transactional logged as well?

A: Yes the actual database will be logged independent of links.

Q: If Compact changes the DBIID then what happens to a backup copy of the database? Will the log be able to recover in the event a database is replaced on-line?

A: It assumes you did not copy back an older version of the database while the server was crashed. Never "touch" databases after a server crash until you get through a clean restart. You can start a clean restart by simply entering the command "nfixup zzzz" before the Domino server is restarted (where zzzz is a database that does not exist). The initialization of fixup will trigger the restart and recover the logged databases to a clean state. This will clear the UBMand will harden all the information to the transactionally logged databases (the actual NSF), then the server can be restarted. Consistency check will run against all non transaction logged databases.

Q: When the server is live, how is it possible to monitor the health of the transactional log?

A: Any extra "monitoring" of the log at run-time is not recommended as it will disturb your system performance. The log is not read very much while the server runs so it is true that issues with the logs would not soon be noticed; however, the log is written to constantly and all hardware would give a bad return code and generate error events if write errors occurred.

Q: The customer uses FTP to move NSF files between "live" servers. Can the Transactional Log recover from finding a new database live while the server is running?

A: IMPORTANT:Never OS copy or FTP a live logged database. The reason is that a new replica creates a replica stub on the new server, then populates the database later, preserving the state of the transaction logging. An OS copied database will be subject to a consistency check when it is placed on the new server.

It is acceptable however to pull or create a new database replica of a live logged database. A new replica creates a replica stub on the new server, then populates the database later, preserving the state of the TL. An OS copied db will be subject to consistency check when it is placed on the new server.

There are no known problems addingnewdatabases (new databases do not have a DBIID yet) to a server "live", but you must get a "clean" version and you should make it appear "instantaneously" so it does not show up as only half there, as it would when you FTP it.

The recommendation is as follows:1. Use dbbackup from API Sample or a backup vendor's backup (dbbackup test tool takes a backup and "applies all pending changes" so it's a healthy backup). Make the extension of the database something non N* line .bak.2. FTP or copy the bak file to the other server.3. Rename the bak to nsf so it "appears" instantaneously.4. The next open will assign a new DBIID and run fixup if it was logged before, to clear the log sequence numbers in the file. It may take a while if it was a large database, but then it will behave normally.

An existing database that is not open that needs to be moved from one server to another should be done using Notes\New Copy or New Replica. Prior to the move, the extension should be changed to something other than .nsf. The database can then be moved via new copy or new replica. When the move is complete, the extension should be changed back to .nsf. This method ensures that transactional logging begins logging the database only when it is complete and consistent. It is important to note that this will change the DBIID of the database so a backup must then be taken.

Q: A database on a Domino server is continuously becoming corrupted and is then being marked as read only. If transactional logging is enabled on the server will it mark the database as read only?

A: The only thing that transactional logging will do is mark the database corrupt. It will never mark the database as read only.

Q: How does transactional logging operate with SCOS (shared mail)?

A: The capability to have transactional logging for SCOS in R5.x does not exist. This capability is present in Notes/Domino 6.

Related informationTransaction Logging in Domino R5

Chapter 13Domino Server Tasks and Console CommandsIn this chapter, I discuss how to specify which component tasks Domino loads at startup and how to configure Domino to run scheduled maintenance tasks. This type of configuration is usually done once as the server is commissioned, with occasional changes as needed.There is also a set of commands that you can issue at the Domino server console to dynamically control the operation of the server. These commands are typically used to diagnose and resolve issues with Domino operations, make dynamic configuration changes to the Domino server, or to override scheduled operations and make things such as mail routing or database replication happen immediately.Domino Server TasksA few lines inNOTES.INIdefine which server tasks are started when the server starts up, and also which scheduled tasks are to run at various times during the day.TheServerTasks=line lists the tasks to start as the server starts up. The scheduled tasks are listed in theServerTasksAt0=toServerTasksAt23=lines. These specifications use the 24-hour clock, where 0 is midnight and 23 is 11:00 P.M.Another option for scheduling tasks is the Program document in the Domino Directory. The Program document is described inChapter 2,Domino Directories.By default, the following tasks are configured to start, depending on how the server has been configured: When the Quick and Easy Configuration setup option is selected, the tasks set to start at startup areRouter,Replica,Update,AMgr,AdminP,CalConn,Event,Sched,Stats, andMaps. Then other tasks are added depending on which other client audience options are selected: Web Browsers addsHTTPandDIIOP Internet Mail Packages addsIMAPandPOP3 News Readers addsNNTP Enterprise Connection Services addsDECs When the Advanced Configuration setup option is selected, the tasks set to start at startup areAdminP,AMgr,Update,Replica,Router, andMaps. Other tasks, such asCalConn,Event,Sched, andStat, are optionally added if selected. Other tasks are added if they are selected by name. These are: HTTP,DIIOP IMAP,POP3 LDAP NNTP DECS When the server has been upgraded from 4.x, you are not required to run the setup application after the code has been installed. This means that the original list of startup tasks is retained. Because theReportstask no longer exists in R5 and has been replaced by theCollecttask, you must remove it. You also must remove theSMTPMTAstatement, since this function has been added to theRouterprocess.Then, for the scheduled tasks inNOTES.INI, these entries are added as part of the original installation:ServerTasksAt1=Catalog,DesignServerTasksAt2=UpdAll,Object Collect mailobj.nsfServerTasksAt3=Object Info -FullServerTasksAt5=StatlogYou should also be aware that after you reinstall or upgrade your Domino server code, these entries are usually added again toNOTES.INI, if they had been removed.Here is a list of all of the Domino server tasks, their functions, and the specific console commands they accept:AdminPThe Administration Process automates many administration tasks. This task has the following commands available to modify its behavior while it is running:tell adminp process allInstructs theadminprocess to process all new and modified immediate/interval/daily/delayed requests.tell adminp process dailyInstructs theadminprocess to process all new and modified daily requests.tell adminp process delayedInstructs theadminprocess to process all new and modified delayed requests.tell adminp process intervalInstructs theadminprocess to process all immediate and interval requests.tell adminp process newInstructs theadminprocess to process all new requests.tell adminp process peopleInstructs theadminprocess to process all new and modified requests to update Person records within the Domino Directory.tell adminp process timeInstructs theadminprocess to process all new and modified requests to delete mail files that become unlinked.tell adminp show databasesLists the databases that an administration server manages, and also lists databases that do not have an administration server configured.AMgrThe Agent Manager runs scheduled and triggered agents in Domino databases. This task has the following commands available to modify its behavior while it is running:tell amgr pausePauses the agent manager service, so no new agents can be scheduled for execution on the server.tell amgr resumeResumes the agent manager service, so new agents can be scheduled for execution on the server.tell amgr scheduleDisplays the scheduled agents that are to run today, and also the database in which they reside.tell amgr statusDisplays the status of the agent manager, and also configuration information of the agent manager from the server document in the Domino Directory.BillingCollects the configured usage information for billing.Calconn(Calendar Connector)Used to request free/busy time information for users whose mail databases reside on other servers.CatalogMaintains the Domain Catalog, which helps users to find and locate Domino databases and files of interest to them within the Domino domain.ChronosPerforms updates of database full text indexes for databases that are configured to be updated hourly or daily. This task is autostarted by Domino and does not need to be added toNOTES.INIin order to run. You can cause this task to run immediately by issuing the commandsload chronos dailyorload chronos hourly.Cladmin(Cluster Administration Process)Ensures correct operation of the Domino application-level cluster.Cldbdir(Cluster Database Directory Manager)Maintains the cluster database directory.Clrepl(Cluster Replicator)Replicates between servers in a cluster in real time. Cluster replication is event-driven, whereas standard replication is schedule-driven. This task has the following commands available to modify its behavior while it is running:tell clrepl logInstructs the cluster replication tasks to immediately log information into the server log database, rather than wait for the defined log interval. Use this command when cluster replication is encountering problems--you can view the log entries for the errors and ensure that the problem is resolved before the next cluster replication attempt.CollectCollects server activity statistics from one or more servers. This task has the following command available to modify its behavior while it is running:tell collector collectRuns the Domino server statistic collection on every server specified and creates statistic reports.Compact(Database Compaction)Reorganizes the disk usage by each database in order to free up unused space. TheCompacttask can be invoked with the following commands (the various options can be combined as needed):load compact[database]Compacts the database or specified subdirectory.load compact[database]-SXCompacts databases with greater thanX% free space.load compact[database]-DCompacts databases and deletes any built view indexes.load compact[database]-RCompacts databases and changes the ODS version to R4 from R5. Used when backing out of an upgrade from R4 to R5.load compact[database]-MFor R4 databases, sets a maximum size of 4GB and compacts the database.load compact[database]-bCompacts databases in place. Can be used only if the database internal format is not being changed due to a change in one if the advanced database properties. It recovers unused space within the database, but does not reduce the file size of the database.load compact[database]-BCompacts databases in place. It recovers unused space within the database, and does reduce the file size of the database.load compact[database]-cUses copy-style compaction of the database, rather than in-place compaction.load compact[database]-LWhen using copy-style compaction, allows access to the database while the compaction is in process. Compaction ends for the database if a user accesses the database.load compact[database]-iWhen using copy-style compaction, ignores any errors that occur during compaction.load compact[database]-fCompacts the database and changes the format of the database to disable support for document table bitmap optimization.load compact[database]-FCompacts the database and changes the format of the database to enable support for document table bitmap optimization.load compact[database]-HCompacts the database and changes the format of the database to enable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae.load compact[database]-hCompacts the database and changes the format of the database to disable support for maintenance of the specialized response hierarchy used by the @AllChildren and @AllDesendants view selection formulae.load compact[database]-TCompacts the database and changes the format of the database to enable transactional logging.load compact[database]-tCompacts the database and changes the format of the database to disable transactional logging.load compact[database]-UCompacts the database and changes the format of the database to maintain unread marks.load compact[database]-uCompacts the database and changes the format of the database to disable maintaining unread marks.load compact[database]-ADoesn't compact the database; archives documents to another database, and then deletes those documents from this database if archiving is set up for the database.load compact[database]-aIf archiving is set up for the database, archives documents to another database and then deletes these documents from this database and compacts the database.ConvertUsed to update the mail databases to a new mail template design, typically used when upgrading the server to from R4 to R5. The Convert task can be invoked with the following commands:load convert [-r]mailfilepath currenttemplatenamenewtemplatenameConverts the mail databases in the givenmailfilepathfrom thecurrenttemplatename(*can be used to match all existing templates) to thenewtemplatename. The new mail template for R5 is calledMAIL50.NTF. The -roption is used to recursively process subdirectories below the givenmailfilepath.load convert-lmailfilelistProduces a list of primary mail databases (but not replicas) on the server and writes the list to the file specified inmailfilelist. This option is used to produce a list of mail database files, which would be used with the -foption as shown in the next entry.load convert-fmailfilelist currenttemplatenamenewtemplatenameUpdates the mail databases listed in themailfilelistfrom thecurrenttemplatename(*can be used to match all previous templates) to thenewtemplatename. The new template in R5 is calledMAIL50.NTF.load convert-mmailfilepathChanges the mail databases specified within themailfilepathto able be used for IMAP mail access.DECS(Domino Enterprise Connection Services)Enables hot linking between documents within a Domino database and backend data sources such as DB2 or Oracle.DesignUpdates database designs from their template.DIIOPAn object request broker; allows browser clients running Java applets to access backend Notes database objects via the IIOP protocol. This task has the following commands available to modify its behavior while it is running:tell diiop show usersShows all active users connected to the server by DIIOP.tell diiop drop allDrops all user connections using DIIOP immediately.DircatMaintains small copies of the Domino Directory called the Directory Catalog, which can be used for user lookup for mobile/laptop users. This task is usually not started via an entry inNOTES.INI; when you enable a schedule on the Directory Cataloger tab in the Server Document this task is launched automatically.Event(Event Monitor)Tracks of specific events that have occurred on the Domino serverFixupFixes suspected corrupt Domino databases. These options can be combined as needed:load fixup [database] -FWhenfixupruns against multiple databases, by default it checks only documents with the last modified date since its last run. This parameter then forces thefixuptask to check all documents in all databases being checked.load fixup [database] -iChecks only new documents in the database since the last run offixup.load fixup [database] -JRunsfixupagainst databases that have transaction logging enabled. If this parameter isn't used,fixupdoesn't check these databases.load fixup -LWhen used without specifying the database to check, logs every database suspected of being corrupted. The default is to log only when a database problem is found and needs to be corrected.load fixup [database] -NChanges the way thatfixupoperates when a corrupted document within a database is encountered. When this parameter is specified, any corrupted documents found are not deleted. A typical use of this is to allow documents to be copied to another database beforefixupdeletes them in an effort to retrieve documents from a corrupted database.load fixup [database] -QInstructsfixupto be less thorough in its checking for corrupted documents in the database.load fixup [database] -UChanges unread document lists to the older R4 format. (Lotus recommends that you do this only when requested by Lotus Support.)load fixup [database] -VSpecifies to not check views for corruption.HTTP(Domino web server)Serves regular HTML/CGI and converts Domino elements into HTML/Java applets as required. This task has the following commands available to modify its behavior while it is running:tell http restartRefreshes the configuration for theHTTPtask without having to unload and reload the task into the server memory.tell http show file accessShows filesystem access on the server for HTTP clients.tell http show securityDisplays SSL configuration information for the web server.tell http show usersShows the current list of session-based users that are connected and authenticated to Domino.tell http show virtual serversDisplays the configured virtual web servers defined on the Domino server.ICM(Internet Cluster Manager)Manages access to clustered servers for HTTP (web) clients.IMAPFacilitates access to Domino mail databases by IMAP clients.LDAPFacilitates access to the Domino Directory by LDAP clients. This task has the following commands available to modify its behavior while it is running:tell ldap reloadschemaUpdates the schema for LDAP to reflect customizations made to the Domino Directory.tell ldap exportschemaCreates or updates the schema database (SCHEMA50.NSF) to reflect schema changes in the Domino Directory.MapsExtracts information from Connection documents to produce the graphical replication and routing information in Domino Administrator.MTC(Message Tracking Collector)Monitors the work of theRouterprocess (which delivers mail in Domino) and keeps records as required as to what mail was sent to whom. This allows users and administrators to query mail status. This task does not need to be explicitly started; if mail tracking is enabled on the server by a Configuration document, then Domino will start this task automatically as theRoutertask is started.tell mtc processCollects information now for message tracking, rather than waiting for the message tracking interval.tell mtc intervalvalueChanges the collection interval used for message tracking information by theMTCtask.tell mtc compactCompacts the message tracking store database now.tell mtc reindexReindexes the message tracking store database now.tell mtc purgevaluePurges collected message tracking information older thanvaluedays from the message tracking database now.NNTPEnables the Domino server to be used as a newsgroup server. This task has the following commands available to modify its behavior while it is running:tell nntp newgroupnewsgroupnameCreates a new newsgroup callednewsgroupname.tell nntp newgroup deletegroupname1, groupname2Deletes the specified newsgroups.tell nntp newgroupnewsgroupname pathnameTells theNNTPtask to add a new newsgroup to its cache using the specified database.tell nntp print cache listDisplays the current newsgroups and their corresponding databases.tell nntp print configShows the configuration information for the NNTP server.tell nntp resetservernameResets the newsfeed from the specified server, so the next newsfeed will be considered an initial newsfeed.tell nntp show configShows the configuration information for the NNTP server.tell nttp show groupsShows the currently configured newsgroups on the server, and the path of each relative to the data directory on the server.Object(Object Store Manager)Works with single-object store mail databases, if enabled. TheObjecttask can be invoked as follows:load object createsharedmaildb.nsfCreates a new shared mail database with the namesharedmaildb.nsf.load object linkusermaildb.nsf sharedmaildb.nsfLinks messages already present withinsharedmaildb.nsfinto the shared mail database.load object link -nocompactusermaildb.nsf sharedmaildb.nsfLinks messages already present withinsharedmaildb.nsfinto the shared mail database. The-nocompactoption means thatusermaildb.nsfis not compacted (which reclaims unused space in databases) even if there are more than five messages linked intosharedmaildb.nsf.load object link -relinkusermaildb.nsf sharedmaildb.nsfLinks a user's mail database to a differentsharedmaildb.nsf.load object unlinkusermaildb.nsfUnlinks messages for the givenusermaildb.nsf.load object unlinksharedmaildb.nsfUnlinks messages for the givensharedmaildb.nsf.load object set -neverusermaildb.nsfSetsusermaildb.nsfto never use shared mail.load object reset -neverusermaildb.nsfRemoves the setting to never use shared mail forusernmildb.nsf.load object set -alwaysusermaildb.nsf sharedmaildb.nsfEnsures all replicas of theusermaildb.nsfuse the shared mail databasesharedmaildb.nsf.load object reset -alwaysusermaildb.nsfRemoves the setting that makes sure all replicas ofusermaildb.nsfuse the shared mail database.load object collect-nodeleteChecks which old messages are ready to be deleted, but does not actually delete them.load object collectusermaildb.nsfDeletes obsolete messages from theusermaildb.nsf.load object collectsharedmaildb.nsfDeletes obsolete messages from thesharedmaildb.nsf.load object collect -forcesharedmaildb.nsfThe -forceoption is used after a user mail database has been deleted, and you wish to reclaim the space used for linked messages insharedmaildb.nsfthat were referred to only from that user mail database.load object infousermaildb.nsfChecks whether theusermaildb.nsfcontains any messages that use a shared mail database.POP3Facilitates access to Domino mail databases by POP3 clients.ReplicaAllows Domino servers to replicate database updates with each other.RouterDelivers mail to databases on this server and forwards it to other servers as required. This task has the following commands available to modify its behavior while it is running:tell router delivery statsShows the current mail routing delivery statistics.tell router compactShuts down the mail routing process on the server, and compacts theMAIL.BOXdatabase. If more than oneMAIL.BOXis on the server (for example,MAIL1.BOXandMAIL2.BOXif the server is configured to have two), each of these databases is compacted in turn. When the compaction activity is complete, the router process is resumed.tell router show queuesShows the current number of waiting mail items in the queues for each destination mail server.tell router usedatabasenameEnables the use of shared mail on this server. It also changes the value ofSHARED_MAILto2inNOTES.INI.databasenameis the name of the database used for the shared mail database, and a new database link calledMAILOBJ.NSFis created in the server data directory, which points todatabasename.RunJava ISpyAllows us to configure probes between servers to periodically check that servers can be accessed to send mail or that they can communicate via a TCP port. Note that this task name is case-sensitive--it must be specified in this way (with an uppercaseISand lowercasepy)--otherwise, the Java VM within Domino will not be able to find the appropriate Java classes to load.Sched(Schedule Manager)Tracks free/busy time for all who have their mail database on that server. This task has the following commands available to modify its behavior while it is running:tell sched statsDisplays the number of user appointments and resources reservations in the free time database.tell sched showusernameDisplays whenusernameis busy according to the schedule in that given user's mail database.tell sched validateFor every mail user on the server, checks whether free/busy time is recorded in the free time database.tell sched validateusernameForusername, checks whether free/busy time is recorded in the free time database.SMTPListens for incoming SMTP mail. Usually you need not configure this task to start; it is started automatically once theSMTP Listenertask is enabled on the Server document within the Domino Directory.StatlogRecords database usage information into the Domino Log file,LOG.NSF.StatsProduces statistics for a Domino server.Updall(Indexer)Maintains changed views and full text indices as the data changes within the Domino database.load updall [database] -APerforms an incremental update of an R4 site search database.load updall [database] -BPerforms a full update of an R4 site search database.load updalldatabase-CRebuilds the full text indexes and any unused views in the database.load updall [database] -FUpdates full text indexes but not views.load updall [database] -HUpdates full text indexes that are configured to be updated immediately.load updall [database] -LUpdates full text indexes that are configured to be updated immediately, hourly, or daily.load updall [database] -MUpdates full text indexes that are configured to be updated immediately or hourly.load updall [database] -RRebuilds all full text indexes and all views in the database.load updalldatabase-TviewRebuilds the out-of-date view in the database.load updalldatabase-Tview-RRebuilds the view in the database whether or not it is out of date.load updall [database] -VUpdates view but not full text indexes.load updall [database] -XDisplays the number of user appointments and resource reservations in the free time database.WebConverts HTML web pages into Notes documents for retrieval by Notes clients. This task has the following commands available to modify its behavior while it is running:tell web helpLists the available options for the web task:tell web quit,loadweb,tell web help, andtell web refresh.tell web refreshRefreshes the web navigator task settings while the task is running.Domino Server ConsoleThe Domino server console is a DOS-like window on NT and OS/2 servers in which you can view server messages and enter commands. For those platforms, switch to this open window to access it at the server. On the AS/400 platform, issue the commandWRKDOMCSLservername(work with Domino Console) to access the Domino console. On the OS/390 platform, you have the option to use telnet or the OS/390 operator console with the as-is DOMCON package, which is downloadable fromhttp://www.s390.ibm.com/products/domino/domcon/dmcnmain.html.On the Unix platforms (AIX, HP/UX, Linux, and Solaris), there is a new character console in R5 that can be used to access the server console. This function works only on the Domino server itself, so to do this remotely requires telnet access to the server. Also, you have to be listed as an Administrator for that server within the Domino Directory. The steps to use this function in Unix are: Change to the data directory for the server (cd ~/notes/data). Execute the cconsole program (/opt/bin/cconsole). Enter the location of your ID file, then enter your password.There are three special commands available on the Unix platforms to work with this character console:doneExits the console program.live onTurns on live update of server messages on the console.live offTurns off live update of server messages on the console. You might do this so that commands you enter and any responses made by Domino are not lost in a sea of updated messages issued by the running server.These console commands on all platforms are also logged in theLOG.NSFdatabase on the server. So if the output messages from the commands you enter get scrolled off the screen because of other messages from the server, you can open the Miscellaneous Events view of this database to review the output messages. The documents in this view are listed in chronological order, with the most recent log messages therefore at the bottom of the view (seeFigure 13-1).Figure 13-1.Viewing old console messages in the server's log database (LOG.NSF)

As discussed inChapter 6,Domino Administration Tools, Domino Administrator has an option on the Server tab to access the console of the current server being administered. You are more likely to use this in day-to-day operations than you are to use the server itself. Another advantage of using this mode of operation is that the Domino Administrator client has a built-in list of server commands, which means that you don't need to always work from memory on the command names and their correct syntax (seeFigure 13-2).Figure 13-2.Accessing the server console via the Domino Administrator client

The Domino server console supports redirection for both input and output with the>and b "Please close all open Domino databases for scheduled maintenance"07/11/99 09:16:06 PM BROADCAST from shoreline/Alameda: Please close all open Domino databases forscheduled maintenance> b "Please call the help desk on xtn5555" "Greg Neilson/Alameda"07/11/99 09:16:41 PM BROADCAST from shoreline/Alameda: Please call the help desk on xtn5555 [GregNeilson/Alameda]dbcacheDomino uses the database cache to keep open the most recently used databases for performance reasons. However, sometimes you may need to work with one of the databases within the cache (perhaps to restore from backup). You can use these commands to view the contents of the database cache, disable the use of the cache, and flush out the contents of the database cache.Syntaxdbcache showdbcache disabledbcache flushCommand optionsshowDisplays the current opened databases in the database cache.disableDisables the server from using the database cache.flushFlushes out the open databases that were in the database cache.ExamplesThis is the output from adbcache showcommand to display which databases are currently open in the cache:> dbcache showDatabase Cache is limited to 121 entries DatabaseC:\Lotus\Domino\Data\mtdata\mtstore.nsfC:\Lotus\Domino\Data\admin4.nsfC:\Lotus\Domino\Data\mail\sneilson.nsfdrop (dr)This command can be used to close user sessions either for all users or for the nominated users. Typically you would use this command only in preparation for an unscheduled shutdown of the Domino server.Syntaxdrop alldrop usernameCommand optionsallDrops all user sessions from the server.usernameDrops the nominated user sessions from the server. More than one username can be entered at once, each of which should be enclosed in double quotes.ExamplesThis is output from a command to drop all user sessions from the server:> dr all07/11/99 09:06:24 PM Closed session for Greg Neilson/AlamedaDatabases accessed: 2 Documents read: 2 Documents written: 107/11/99 09:06:24 PM Closed session for Greg Neilson/AlamedaDatabases accessed: 1 Documents read: 0 Documents written: 0exit (e)Closes down the Domino server.Syntaxexit [password]Command optionspasswordIf theSET SECUREcommand has been run to provide a password for operation of the Domino server, then this password needs to be provided in order to shut down the server.See Alsoquit, restart serverhelp (he)Displays the list of server commands and their main parameters. Unfortunately, this list is too long for a single screen and quickly scrolls to the end. To use this list, you can either view the console output in the server log database (LOG.NSF) or redirect the server output into a file.Syntaxhelpload (l)Starts a Domino server task. Three particular tasks,convert,compact, andobject, have a number of optional command-line parameters. For thecompacttask, if a database or subdirectory is not specified, this command applies to all databases on the server. Theobjecttask works with the optional shared mail feature, and is further described inChapter 4,Mail. Theconverttask is used when upgrading to a new release of the server code--say from R4 to R5--and updates the specified mail databases to use the new design template.Syntaxload program [options]Command optionsprogramSee the list of server tasks at the start of this chapter.platform (pl)Works with operating system statistic collection on the Windows NT (Intel) and Solaris (Sparc) platforms. You must have the collection of platform statistics enabled (by having theNOTES.INIparameterPLATFORM_STATISTICS_ENABLED=1) to be able to use these commands.Syntaxplatform time [secs]platform resetplatform runplatform waitCommand optionstime [minutes]When this command is run without a time parameter, it displays the current statistic collection sampling rate. The default is one minute. Otherwise, this sets the statistic collection sampling rate to the value (in minutes) entered.resetIssued at the start of a monitoring session, this command resets the statistic counters for the operating system platform.runResumes the collection of platform statistics.waitTemporarily pauses the collection of platform statistics.pull (pul)Starts database replication from the specified server to the local server. Typically, a Connection document defines the scheduled replication between servers, and this command is used to manually override it.Syntaxpull server [database]Command optionsserverThe name of the remote server you wish to pull database changes from to the local server. The remote server name should be the full hierarchical name, and enclosed in quotes if there any spaces in it.databaseOptionally, the name of the database on the local server into which you wish to pull changes from the server. The database on the other server must be a replica copy (that is, have the same replica ID) in order for replication to occur.If the database parameter is not listed, then the server prepares a list of databases with identical replica IDs on both servers, and then pulls the changes in each from the other server.ExamplespulWestline/Alamedapulls changes from the remote server namedWestline/Alamedato the local server for all databases having the same replica ID.pulShoreline/Alamedanames.nsfpulls changes from the remote server namedShoreline/Alamedato the local server for theNAMES.NSFdatabase.See Alsopush, replicate, routepush (pus)Starts database replication from the local server to the specified server. Typically, a Connection document defines the scheduled replication between servers, and this command is used to manually override it.Syntaxpush server [database]Command optionsserverThe name of the remote server you wish to push database changes to from the local server. The server name should be the full hierarchical name, and enclosed in quotes if there any spaces in it.databaseOptionally, the name of the database on the local server out of which you wish to push changes to the remote server. The database on the remote server must be a replica copy (that is, have the same replica ID) in order for replication to occur.If the database parameter is not listed, the server prepares a list of databases with identical replica IDs on both servers, and then pushes the changes in each to the other server.ExamplespusWestline/Alamedapushes changes from this local server to the remote serverWestline/Alamedafor all databases having the same replica ID.pusShoreline/Alamedanames.nsfpushes changes from the local server to the remote serverShoreline/Alamedafor theNAMES.NSFdatabase.See Alsopull, replicate, routequit (q)Closes down the Domino server.Syntaxquit [password]Command optionspasswordIf theSET SECUREcommand has been run to provide a password for operation of the Domino server, this password needs to be provided in order to shut down the server.See Alsoexit, restart serverreplicate (rep)Starts database replication from this server to/from the specified remote server. Typically, a Connection document defines the scheduled replication between servers, and this command is used to manually override it. The process works in two stages: the local server pulls any changes from the remote server, and then the remote server has the option to pull any changes from the local server. The remote server refers to the replication schedule, and performs a pull now only if this manual replication doesn't fall within the timeframe the server replicates to this server.Syntaxreplicate server [database]Command optionsserverThe name of the remote server you wish to push/pull database changes to or from. The server name should be the full hierarchical name, and enclosed in quotes if there any spaces in it.databaseAn optional parameter specifying which database to replicate. If this parameter is not present, the server attempts to replicate every database that has a common replica ID between the two servers.ExamplesThis example replicates the Domino Directory between the two servers with the commandrep Westline/Alameda names.nsf:> rep westline/alameda names.nsf07/18/99 12:10:43 AM Database Replicator started07/18/99 12:10:43 AM Starting replication with server westline/alameda07/18/99 12:10:43 AM Pulling names.nsf from westline/alameda names.nsf07/18/99 12:10:44 AM Replicator added 1 document(s) to names.nsf fromwestline/alameda names.nsf07/18/99 12:10:44 AM Pushing names.nsf to westline/alameda names.nsf07/18/99 12:10:44 AM Replicator added 1 document(s) to westline/alamedanames.nsf from names.nsf07/18/99 12:10:44 AM Replicator updated 6 document(s) in westline/alamedanames.nsf from names.nsf07/18/99 12:10:44 AM Finished replication with server westline/alameda07/18/99 12:10:44 AM Database Replicator shutdownSee Alsopull, push, routerestartStops or starts the Domino server or one of its network ports.Syntaxrestart server [password]restart port portnameCommand optionsserverPerforms an orderly shutdown of the server and then restarts it.Note that this does not work when Domino is configured as a Windows NT/2000 service. In this case, you must stop and start the service to restart the Domino server.portportnameSpecifies which port is to be restarted. The currently enabled ports for Domino are defined in thePorts=line inNOTES.INI. The default ports available to be configured (others can be defined if needed) areTCPIP,LAN0ip,VINES,SPX,Appletalk,LAN1-LAN8(NetBIOS), andCOM1-COM5.passwordIf theSET SECUREcommand has been run to provide a password for operation of the Domino server, this password must be provided in order to shut down the server.Examplesrestart servershuts down and restarts the Domino server.restart port tcpipstops and restarts the TCP/IP port for Domino network communications.See Alsoexit, quit, start port, stop port, show allportsroute (ro)Starts mail routing with a given server. Typically, a Connection document will define the scheduled mail routing a server, and this command is used to manually override the scheduled mail routing. If there is no mail to route at this server (that is,MAIL.BOXis empty) this command is ignored.Syntaxroute servernameCommand optionsservernameThe name of the server we wish to send mail to, using the hierarchical name format.Examplesroute Westline/Alamedasends any outstanding mail that was destined for that server.See Alsoreplicate, push, pullset (se)Makes dynamic changes to the Domino server configuration.Syntaxset configuration variable = value [password]set secure passwordset secure password newpasswordset stat statisticnameCommand optionsconfigurationvariable=valueThis command specifies the variable fromNOTES.INIto be changed and its new value to use. As well as making the dynamic change in the Domino, theNOTES.INIfile is also updated with this new value. It can also be used to add configuration variables toNOTES.INI.Note that if the server console has been secured via aSET SECUREcommand, this password needs to be supplied in order to change this variable.securepasswordSets a password for the Domino server that must be entered to shut down the server or dynamically change any of the parameters. However, this usage is not entirely foolproof--it adds an entry toNOTES.INIcalledSERVER_CONSOLE_PASSWORDand stores the password there in a hashed format. This line can be deleted fromNOTES.INIto remove the use of the password. So physical security of the server, ensured by placing it in a secured room with limited access, is probably a better idea.If the same command is run again with the current password, the password is deleted from use.newpasswordUsed to change the password from the previous password to this new value.statstatisticnameResets the value of the counter statistic to0. Thestatisticnameparameter must be provided. You can obtain a complete set of statistics from the output of theshow statconsole command. However, the vast majority of the server statistics cannot be reset; if you attempt to reset them, the console will return the message "statisticcannot be reset." The only statistics that can be reset are those for the server. These are: SERVER.BUSYTIMEQUERY.RECEIVEDCOUNT SERVER.OPENREQUEST.MAXUSERS SERVER.OPENREQUEST.PREV4CLIENT SERVER.OPENREQUEST.RESTRICTED SERVER.OPENREQUEST.V4CLIENT SERVER.TRANS.TOTALExamplesThis example resets theSERVER.TRANS.TOTALstatistic:> set stat Server.Trans.Total07/17/99 08:29:00 PM SERVER.TRANS.TOTAL was set to zero.The following example checks the value of theLOG_REPLICATIONconfiguration value, then sets it to5(which displays the most information when replicating ), then checks the value again:> show configuration log_replicationLOG_REPLICATION=1> set configuration log_replication=5> show configuration log_replicationLOG_REPLICATION=5See Alsoshow configurationshow (sh)This command has many options available and is used to display information about the Domino server. Note that much of this information is available graphically from the Server tab in Domino Administrator.Syntaxshow allportsshow clustershow configuration settingshow directory [*log | *nolog]show diskspace [location]show memoryshow performanceshow port portnameshow scheduleshow servershow stat [statisticname]show tasksshow transactionsshow usersCommand optionsallportsLists all ports defined on the server as enabled or disabled ports.clusterIf the server is part of a Domino cluster, displays current information such as the name of the cluster, which servers are defined in the cluster, and their availability state and index (out of 100). This command can be abbreviated as:SH CLconfigurationsettingDisplays the current value of a given setting fromNOTES.INI. This command can be abbreviated as:SH COsettingdirectory [*log | *nolog]Lists all files in the server'sDATAdirectory, what database version they are (R4 or R5), whether the database uses transactional logging, and the date and time of the last update. This command can be abbreviated as:SH DIRThe*logoption displays only files that use transactional logging, while the*nologoption displays only files that do not use transactional logging.diskspace [location]Shows how much free space is available on the given drive (NT and OS/2) and filesystem (Unix variants). If the drive is unspecified, the default is to use the drive/file system that has the Domino program directory. The disk space is displayed in bytes. This command can be abbreviated as:SH DISmemoryThe command displays the amount of available memory, which includes the virtual memory allowed. In OS/2, this is the remaining free space on the drive that houses the swap file; in NT, this is the sum of the maximum specified sizes for paging files (assuming there is sufficient free space available on the disk(s)). This command can be abbreviated as:SH MEperformanceToggles on or off the display of performance data to the Domino each minute. This display shows the number of transactions per minute and the number of users on the server. This command can be abbreviated as:SH PEportportnameShows communication statistics for that configured port. This command can be abbreviated as:SH POportnameschedule [taskname|servername]Displays the list of currently scheduled tasks and when they are scheduled to run next. If a task name is given, the next time that task is scheduled to run is displayed. For mail routing and replication, if a destination servername is given, then the next time this is scheduled to run is listed.This uses information from Connection (for mail routing and database replication) and Program documents to determine the scheduled tasks. It does not include those from theServerTasksAtx=lines inNOTES.INI. This command can be abbreviated as:SH SCserverShows information about the server, including the name, whether transaction logging is enabled, whether shared mail is enabled, whether there is any mail still to be sent somewhere, and some measures of the peak server load since starting. This command can be abbreviated as:SH SEstat[statisticname]If a statistic name is entered, then the current value of that statistic is displayed. Also, a group of statistics can be entered with*as the wildcard character; for example,show stat database.*. If no statistic name is entered, all of the currently defined statistics and their values are listed. In this case, since there are likely to be over 200 values displayed--and perhaps more depending on how many tasks are running on the server at that time--this information will scroll through the console window too quickly to read. In this case, you can either review the output in the server log, or redirect the output to a file setting fromNOTES.INI. This command can be abbreviated as:SH ST [statisticname]tasksLists the currently executing Domino server tasks and their status. This command can be abbreviated as:SH TAtransactionsLists statistics of Domino NRPC transaction types performed on the server. For each command, lists the transaction count and the minimum, maximum, total time, and average time to complete the command in milliseconds. This command can be abbreviated as:SH TRusersLists the current user sessions on the server, the databases they have open, and how long since the database was last used. This command can be abbreviated as:SH USExamplesOutput example from theSHOW SCHEDULEcommand:> show schedulewestline/Alameda Replication 07/24/99 08:00:00 AMwestline/Alameda Mail Routing 07/24/99 08:00:00 AMcompact Run Program 07/24/99 11:30:00 PMOutput example from theSHOW TRANSACTIONcommand:Function Count Min Max Total AverageILLEGAL 3 0 0 0 0OPEN_DB 25 0 541 1373 54GET_SPECIAL_NOTE_ID 2 0 10 10 5OPEN_NOTE 3 10 30 60 20CLOSE_DB 20 0 20 20 1POLL_DEL_SEQNUM 7 0 20 20 2SERVER_AVAILABLE_LITE 53 0 0 0 0START_SERVER 65 0 902 2635 40REGISTER_MONITOR_RQST 3 0 20 20 6MONITOR_GETEVENTS_RQST 12 0 70 80 6FINDDESIGN_NOTES 3 0 20 20 6This is an example of theSHOW CLUSTERcommand:> sh clCluster Information Cluster name: Cluster1, Server name: shoreline/Alameda Server cluster probe timeout: 1 minute(s) Server cluster probe count: 72 Server availability threshold: 0 Server availability index: 100 (state: AVAILABLE) Cluster members (2)... server: shoreline/Alameda, availability index: 100 server: westline/Alameda, availability index: 100See Alsoset configuration, set statisicsstart portThis command enables the network port for communications in Domino.Syntaxstart port portnameCommand optionsportnameThe currently enabled ports for Domino are defined in thePorts=line inNOTES.INI. The default ports that are available to be configured (others can be defined if needed) areTCPIP,LAN0ip,VINES,SPX,Appletalk,LAN1-LAN8(NetBIOS), andCOM1-COM5.Examplesstart port tcpipenables the TCP/IP port to be used for Domino network communications.See Alsoshow allports, stop port, restart portstop portThis command disables the network port for communications in Domino.Syntaxstop port portnameCommand optionsportnameThe currently enabled ports for Domino are defined in thePorts=line inNOTES.INI. The default ports that are available to be configured (others can be defined if needed) areTCPIP,LAN0ip,VINES,SPX,Appletalk,LAN1-LAN8(NetBIOS), andCOM1-COM5.Examplesstop port tcpipdisables this port from being used for Domino communications.See Alsoshow allports, start port, restart porttell (t)Used to issue a command to a running Domino server task. Every task responds to thequitcommand, but some tasks have special options available to control their operation.Syntaxtell task quittell task [options]Command optionstaskquitStops thetask.trace (tr)Used to test whether a server can successfully connect to another. There is also an option to specify which port to use to test the connection.Syntaxtrace servernametrace portname!!!servernameCommand optionsservernameThe name of the server you wish to test the connection to.portnameThe name of the server communication port you optionally wish to use to connect to the other server.ExamplesOutput from a successful invocation oftraceservername:> trace westline/alamedaDetermining path to server WESTLINE/ALAMEDAEnabled Ports: TCPIPChecking normal priority connection documents only...Local network connection document found for westline/Alameda Verifying address 'westline.alameda.com' for WESTLINE/ALAMEDA on TCPIP Requesting IP Address for westline.alameda.com from DNS DNS returned address 10.0.0.11 for westline.alameda.com Connected to server WESTLINE/ALAMEDASee Alsoshow allports, start port, stop port, restart portBack to:Lotus Domino Administration in a Nutshel

New All Databasesload compact -F [edit]All MailStop Routertell router quitCompact Commandload compact -F mail/*Start routerload router[edit]Tell RouterCommand ResultTell Router Delivery StatsShows Router delivery statistics.Tell Router CompactCompacts MAIL.BOX and cleans up open Router queues. You can use this command to compact MAIL.BOX at any time. If more than one MAIL.BOX is configured for the server, each MAIL.BOX database will be compacted in sequence.By default, MAIL.BOX is automatically compacted at 4 AM.Tell Router ExitStops the Router task on a server.Tell Router OLists all databases that have an active Out of Office service. For more information about the Out of Office service, see the topic Designating the Out of Office service type.Tell Router Show QueuesShows mail held in transfer queues to specific servers and mail held in the local delivery queue.Tell Router Update ConfigUpdates the server's routing tables to immediately modify how messages are routed. This removes the 5 minute delay before a Router configuration change takes effect.To determine the best route for delivering a message to its destination, the Router creates routing tables, which map a path to the destination. The routing table derives information from variables in the NOTES.INI file and from the Configuration Settings, Domain, Connection, and Server documents in the Domino Directory. The command does not update the routing tables with changes made to the Global Domain document.By default, mail the router automatically refreshes its configuration every 5 minutes to absorb changes made in its sources. In previous versions of Domino, you had to restart the router task to update the routing tables after making changes in the sources documents.The command is case insensitive.CautionIf the Tell Router Update Config command is initiated on an R5 server, it loads shared mail. The Tell Router U portion of the command loads shared mail on R5 servers.Tell Router QuitStops the Router task on a server.[edit]Convert to imapStop Routertell router quitLoad convert utilityload convert -e mail\user.nsfNote: use a "/" for UNIX systemsStart routerload router