ShowTable of Contents
Table of Contents |
Previous Page |
Next Page
A new release of Domino brings with it new server commands. Some of these new commands are enhancements to previously existing commands while others have been added to support new Domino server features such as Domino Attachment and Object Service (DAOS) and ID Vault.
Show Commands
Show commands are generally used to displayed details about specific server tasks.
Show Tasks
The Show Tasks command has been enhanced to now display more detail regarding router activity including status from multiple router threads.
Prior to Domino 8.5, issuing a Show Tasks at the console would return results such as:
Router [00000007] Transferring next message (Note 1:0012E8CE) to Mail1/ITSO
Router Idle
With Domino 8.5 and above the command will return detailed results similar to:
Router Utility: Idle
Router MailEvent: Idle
Router Dispatch: Idle
Router Sweep: Idle
Router Mailbox: Idle
Show Server
The Show Server command has been updated to include details on DAOS status. For example, on a server that is not DAOS-enabled the Show Server command will display its usual output as well as include the following line:
DAOS: Not Enabled
If the server were DAOS-enabled that line would read:
DAOS: Enabled
If DAOS had previously been enabled and contained file attachments in its repository but is currently disabled, that line would read:
DAOS: Read Only
Show Directory
The Show Directory command now includes additional information and switches to include information regarding DAOS.
Issuing a Show Directory command without any switches now includes an additional column labeled DAOS.
DbName Version Log DAOS ---Modified Time
C:\Lotus\Domino\data\names.nsf V8:51 Yes No 08/24/2009 11:32:18 AM
C:\Lotus\Domino\data\log.nsf V8:51 Yes Read 08/24/2009 11:35:09 AM
C:\Lotus\Domino\data\events4.nsf V8:51 Yes Yes 08/24/2009 11:28:12 AM
C:\Lotus\Domino\data\ddm.nsf V8:51 Yes Yes 08/24/2009 11:28:14 AM
This column will display Yes if DAOS is enabled for this database, No if DAOS is not enabled for this database, or Read if DAOS is set to read-only for this
database (in other words, any attachments currently stored in DAOS can be read, but new attachments will not be added).
Show Stat Mail
The mail statistics in Domino 8.5 have been greatly expanded upon to provide forty-one additional statistics.
There are eleven Mail.MessageCache statistics that display memory usage information for open messages.
Mail.MessageCache.Memory.Cache.Max
|
This is constant. The limit in bytes of the size of note memory used for in-process messages beyond which notes will no longer be cached in the message queue entry. If a value is provided for RouterMaxQueueMemorySizeBytes, this statistic will have that value. If a value is not provided for RouterMaxQueueMemorySizeBytes, this statistic will contain the default calculated value.
|
MAIL.MessageCache.Memory.Current
|
The amount of note memory currently in use on behalf of the router. It includes notes on the MailEvent queue, in the main queue entry, and in process by transfer and delivery threads. It also includes any copies of messages prepared and cached for delivery if multiple delivery recipients are receiving the message.
|
Mail.MessageCache.Memory.Event.Max
|
This is constant. The limit in bytes of the size of note memory used for in-process messages beyond which copies of notes will not be put onto the mailbox event queue. If a value is provided for RouterMaxEventMemorySizeBytes, then this statistic will have that value. If a value is not provided for RouterMaxEventMemorySizeBytes, this statistic will contain the default calculated value.
|
Mail.MessageCache.Memory.Peak
|
The highest value seen for MAIL.MessageCache.Memory.Current
|
MAIL.MessageCache.Messages.Aged
|
The number of notes cached in the mail queue entry that were closed out due to age. For example, this can occur when a message is pending in a transfer queue in retry, or waitiing for low priority mail.
|
MAIL.MessageCache.Messages.Current
|
Current count of notes cached in all mail queue entries.
|
MAIL.MessageCache.Messages.Peak
|
The highest value seen for MAIL.MessageCache.Messages.Current
|
MAIL.MessageCache.Opens.Copied
|
Count of message copies taken including copies of messages ready for delivery. This is an optimized way to obtain the message; therefore, higher numbers here are good. The note passed via the MailEvent is considered a copy.
|
MAIL.MessageCache.Opens.Current
|
Count of open message instances (notes), whether obtained by copy or full note open.
|
MAIL.MessageCache.Opens.Current.Peak
|
The highest value seen for MAIL.MessageCache.Opens.Current
|
MAIL.MessageCache.Opens.Opened
|
|
Six Mail.Messages statistics have been added to show the number of messages discovered via the event and search mechanisms.
MAIL.Messages.Read.Event.New
|
Number of messages discovered by mailbox event notification.
|
MAIL.Messages.Read.Event.IntUpdate
|
Number of message updates by event notification done by the router to reflect completed recipients.
|
MAIL.Messages.Read.Event.ExtUpdate
|
Number of updates or deletes of messages in mailboxes not done by the router and found by event notification.
|
MAIL.Messages.Read.Search.New
|
Number of messages discovered by searching.
|
MAIL.Messages.Read.Search.IntUpdate
|
Number of message updates found by search and done by the router to reflect completed recipients.
|
MAIL.Messages.Read.Search.ExtUpdate
|
Number of updates or deletes of messages in mailboxes not done by the router and found by search.
|
There have also been twenty-three mail queue event and dispatch statistics added.
Mail.Queue.Event.Processed = 1
|
Number of mail events (i.e. note update, delete) processed
|
Mail.Queue.Event.ProcessTime.Average = 60
|
Average process time (from dequeue to delete)
|
Mail.Queue.Event.ProcessTime.MostRecent = 60
|
|
Mail.Queue.Event.ProcessTime.Peak = 60
|
|
Mail.Queue.Event.ProcessTime.Peak.Time =
|
Time of the peek process time
|
Mail.Queue.Event.Total = 1
|
Total events created (only displayed if Debug_Router_Extra_Queue_Statistics notes.ini is non-zero)
|
Mail.Queue.Event.Waiting = 0
|
Number of events waiting in queue
|
Mail.Queue.Event.Waiting.Peak = 1
|
Peak number of events waiting in queue
|
Mail.Queue.Event.Waiting.Peak.Time =
|
|
Mail.Queue.Event.WaitTime.Average = 60
|
Average wait time (from creation to dequeue)
|
Mail.Queue.Event.WaitTime.MostRecent = 60
|
|
Mail.Queue.Event.WaitTime.Peak = 60
|
|
Mail.Queue.Event.WaitTime.Peak.Time =
|
|
Mail.Queue.Dispatch.Processed
|
Number of dispatch requests that have been completely processed by the router
|
Mail.Queue.Dispatch.ProcessTime.Average
|
The time to process a dispatch request once removed from the queue
|
Mail.Queue.Dispatch.ProcessTime.Current
|
The time to complete processing of the most recent dispatch request
|
Mail.Queue.Dispatch.ProcessTime.Peak
|
The longest time to process a dispatch request after removal from the queue
|
Mail.Queue.Dispatch.Total
|
|
Mail.Queue.Dispatch.Waiting
|
Number of dispatch requests currently in the queue waiting to be processed
Note An increasing number generated over a period of time indicates a backup in dispatching messages on the server.
|
Mail.Queue.Dispatch.Waiting.Peak
|
Maximum number of dispatch requests waiting in the queue to be processed since the router was started
Note An increasing number generated over a period of time indicates a backup in dispatching messages on the server.
|
Mail.Queue.Dispatch.WaitTime.Average
|
The average time that router requests have waited in the queue since the router was started
|
Mail.Queue.Dispatch.WaitTime.Current
|
The time that the most-recently processed dispatch request spent in the queue waiting to be processed
|
Mail.Queue.Dispatch.WaitTime.Peak
|
The longest time a dispatch request waited in the queue
|
And finally, there has been one statistic added to show how many messages have been reenumerated since the router task began.
Mail.MessagesReenumerated
|
Number of messages reenumerated since router startup
|
Show Stat DAOS
New to Domino 8.5.1 are the DAOS statistics. There are eleven statistics that will give you insight into how DAOS is performing on your server.
|
|
Reports whether DAOS is enabled.
|
|
|
Reports whether encryption is enabled for DAOS.
|
|
|
Reports whether the DAOS catalog is synchronized.
|
DAOS. Object.Attach_DAOSCreate
|
The number of objects created in DAOS.
|
DAOS. Object.Attach_NSFCreate
|
The number of objects created in the NSF because they did not qualify for storage in DAOS, typically because they were smaller than the DAOS minimum object size.
|
DAOS. Object.Attach_DAOSOptimizedCreateLocal
|
The number of objects that did not need to be copied between Notes databases located on the same Domino server (for example, copied from MAIL.BOX to a recipient's mail file) because the objects already existed in the DAOS repository. This statistic shows intra-server savings from optimization of object copying.
|
DAOS. Object.Attach_DAOSOptimizedCreateRemote
|
The number of objects on the server that did not need to be sent over the network from remote clients or servers because the objects already existed in the DAOS repository. This statistic shows inter-server savings from optimization of object copying.
|
DAOS. Object.Attach_DAOSDelete
|
The number of objects for which the reference count went to zero (objects were either deleted immediately or placed in the deferred deletion queue).
|
DAOS. Object.Attach_TotalCreated
|
Total number of objects listed by the Object.Attach_DAOSCreate, Object.Attach_NSFCreate, Object.Attach_DAOSOptimizedCreateLocal, and Object.Attach_DAOSOptimizedCreateRemote statistics.
|
DAOS. Object.OptimizedCreateLocalSavingsMB
|
The total savings in MB for objects that did not need to be copied between databases on this server (intra-server savings from optimization of object copying).
|
DAOS. Object.OptimizedCreateRemoteSavingsMB
|
The total savings in MB for objects that did not need to be to be sent over the network from remote clients or servers (inter-server savings from optimization of object copying).
|
Issuing a Show Stat DAOS command will return all eleven statistics similar to:
DAOS.Engine.Catalog = Synchronized
DAOS.Engine.Encryption = Enabled
DAOS.Engine.Status = Enabled
DAOS.Object.Attach_DAOSCreate = 73
DAOS.Object.Attach_DAOSOptimizedCreateLocal = 0
DAOS.Object.Attach_DAOSOptimizedCreateRemote = 1
DAOS.Object.Attach_NSFCreate = 0
DAOS.Object.Attach_TotalCreated = 74
DAOS.Object.Delete = 0
DAOS.Object.OptimizedCreateLocalSavingsMB = 0
DAOS.Object.OptimizedCreateRemoteSavingsMB = 17
You may also issue a Show Stat DAOS.
statisticname using the name of the statistic for which you would like to receive more information. For example, to find out if DAOS encryption is enabled you could enter Show Stat DAOS.Engine.Encryption at the Domino console to get back only the output:
DAOS.Engine.Encryption = Enabled
Show IDVaults
New for the ID Vault implementation in Domino is the Show IDVaults command. Issuing this command at your server console will result in output that display pertinent ID Vault information similar to:
ID Vault /IDVault (IBM_ID_VAULT\IDVault.nsf)
Control Vault Name: /IDVault
Control Vault Servers: LA/ITSO
Vault Operations Key: VO-ggdp-yowt/LA/IDVault
Servers: LA/ITSO
Vault Name: /IDVault
Description: IDVault
Administrators: Vladislav Tatarincev/ITSO
Administrators: Corey Davis/ITSO
Servers: LA/ITSO
Administration Server: LA/ITSO
/ITSO trusts this vault
/ITSO trusts Vladislav Tatarincev/ITSO to reset passwords
/ITSO trusts Corey Davis/ITSO to reset passwords
Setting security_settings uses this vault
Tell Commands
Somewhat the antithesis of Show commands, Tell commands instruct Domino tasks to perform a specific action.
DAOS Manager
With the inclusion of DAOS into Domino, eleven DAOS-specific Tell commands have been added. Each command is described below.
Tell DAOSMgr Quit
This command will stop the DAOS Manager server task.
Tell DAOSMgr Help
This command will displace the different options available to use with the Tell DAOSMgr command.
Tell DAOSMgr Status
Shows the current status of DAOS on this server.
Tell DAOSMgr Status database_name
Shows the current status of DAOS with respect to the provided database.
Tell DAOSMgr Status Catalog
Shows the current status of the DAOS catalog.
Tell DAOSMgr Dbsummary
This command will display the current status of all DAOS-enabled databases.
Tell DAOSMgr Databases
Displays detailed information for all DAOS-enabled databases.
Tell DAOSMgr ListNLO
Attachments stored in the DAOS repository are stored on the filesystem as .NLO files. This command will list all of the NLO files that are known to be in the DAOS respository. This command is utilizing the data in the DAOS catalog, therefore the output can be used to verify that the actual NLO files exist on the filesystem.
You may utilize the –o
filename switch to write the list to a file.
Usging the ALL keyword will list all NLO files that are known to exist. Depending on the size of your DAOS repository, this list may be rather large. To scale back the size of the list, you can specify that the list only display the NLO files that are missing from the filesystem by using the MISSING keyword.
By specifying a DAOS-enabled database file name you can further pare down the list to only display NLO files for a specific database.
For example, to list all NLO file for the database Photos.nsf and output that list to a file named “listnlo.txt”, we would issue the command
Tell DAOSMgr ListNLO –o listnlo.txt ALL Photos.nsf
The listnlo.txt file would contain information similar to:
/dominodata/notes64adata/DAOS/0002/12A7C6A527F10B7305E79461FF9F4FB875B99FE10263D1A3.nlo
/dominodata/notes64adata/DAOS/0002/AA9106CA4591AF88C421C0F6F914E83C475A1FD5001D62E6.nlo
/dominodata/notes64adata/DAOS/0002/BA58A6B13DB152649FD63CAD38BE0103D21DF86E012DD729.nlo
/dominodata/notes64adata/DAOS/0002/74486CE7C94ECE27E1F48B4A56EDF91710EFA3F50033B38F.nlo
/dominodata/notes64adata/DAOS/0002/D86FC8686039E28B8991523F63FB7B5718C40445005E54E5.nlo
/dominodata/notes64adata/DAOS/0002/E75DC0F4CEA01136B02F72E41F318B79F42CEC3E01988C72.nlo
Tell DAOSMgr Prune
As your users delete documents from their DAOS-enabled databases, your repository will eventually contain attachments that are no longer needed. To remove these documents you can use the prune command.
Running either Tell DAOSMgr Prune or Tell DAOSMgr Prune 0 will remove the unnecessary DAOS objects that are older interval specific in the Server document.
To override this and prune the objects sooner, you can specify that objects older than a specified number of days should be pruned. For example, to prune object older than 10 days you can issue Tell DAOSMgr Prune 10.
Tell DAOSMgr Resync
When you need to resynchronize a DAOS-enabled database with the DAOS catalog, for instance after a database has been restored from backup, running this command will cause DAOS to resynchronize.
Tell DAOSMgr Resync Force
This command will resynchronize the catalog even if it is reported as being synchronized.
Table of Contents |
Previous Page |
Next Page