Observing the space savings with DAOS

 

DAOS compression

Domino already manages attachment compression. DAOS itself does not compress data in any way.

The decision to compress data is made when you attach the data. From the client, when you attach a file you see something like this dialog box. (Compress is the default).

If the Compress checkbox is selected, the attachment will be compressed before it is sent to the server for storage. Depending on the database properties for this database this will either be Huffman compression or LZ1 compression.

The most important thing from a DAOS perspective is that all the mail files use the same type of compression. If different types of compression are used, you could end up with one "master" copy of the LZ1 attachment and one "master" copy of the Huffman attachment. This is because DAOS recognizes them as different and unique file attachments based on their checksums.

Activity
1.        Verify that the Domino server's mail.box is configured for DAOS:
a.        Select mail.box in the files tab
b.        Click File > Application Properties
c.        On the Database Info tab, verify the ODS version indicates 51V.
d.        On the Database Properties tab, verify Disable transaction logging is not checked
e.        On the Database Properties tab, verify Use LZ1 compression for attachments is checked
f.        On the Database Properties tab, verify Use Domino Attachment and Object Service is checked
2.        Register 5 test users.
3.        Open your Administrator's mail file and send a single memo to all users with an attachment of about 3000Kb.
4.        Using Windows Explorer, navigate to the DAOS folder and observe that an additional subfolder has been created and that within it resides an .NLO file that corresponds to the attachment you just sent. Keep the Explorer window open.
5.        Return to your Administrator's mail file to send two more memos to all users. The first memo should have two attachments of about 10Kb and 20Kb each. The second memo should have one attachment of about 50Kb.
6.        Switch to back to Windows Explorer and observe the activity in the \Domino\Data\DAOS\0001 folder.
You will see the expected .NLO file for each attachment. You will also see an additional, temporary copy of each .NLO file. Once DAOS determines that an .NLO file exists for a given attachment, the additional .NLO file is removed. If you are unable to see the temporary NLO files, repeat Step 4 to send another set of memos with the same attachments to the same recipients.
7.        Return to your Administrator's mail file to send a final memo. Send one memo to only yourself with an attachment of no more than 2.5Kb.
8.        Switch back to Windows Explorer and examine the consolidated object store repository on the server.
There should be 4 .NLO files even though you have sent a total of 5 attachments. Why only 4 .NLO files? Because the last attachment you sent (the one less than 2.5Kb) is too small to be saved to the consolidated attachment store repository. This is based on the default settings you accepted in the server document when enabling DAOS

• Comments [0]

Configuring Mail files to Participate in DAOS

 

1.        Perform the following steps to enable DAOS in a newly created mail file:
a.        Log in to the Domino server as an administrator
b.        Register a new user and give them editor access to their mail file. Leaving the access at Editor ensures your administrator is set as Manager.
c.        Access the newly created mail file. On the Database Info tab, note that the ODS version indicates 51. This is a result of the notes.ini parameter you configured in Part 1 of this exercise.
d.        On the Advanced tab, under Advanced options, select Use Domino Attachment and Object Service.
Note: Only administrators can enable DAOS. An individual user, even with Manager access, cannot turn on participation of DAOS for their own mail file.
2.        Perform the following steps to make sure that databases that do not have the 8.5 ODS cannot be configured to participate in DAOS:
a.        Access the administrator's mail file.
b.        Display the application properties.

• On the Database Info tab, note that the ODS version is 43.
• On the Advanced tab, under Advanced options, observe that there is no visible option to Use Domino Attachment and Object Service.

3.        Enable DAOS for existing users' mail files in one of the following ways:

• Update all applications at the same time. Open the Domino server console and enter the following syntax to run compact: load compact mail -c -daos on. This updates the ODS and activates the use of DAOS for all applications.
• Update applications individually. Update the application's ODS ?HOW?, and then enable participation in DAOS either by specifying Use Domino Attachment and Object Service in the Advanced database property, ?OR? in the Files tab in the Domino Administrator client.

4.        Perform the following steps to confirm that the administrator's mail file is configured to use DAOS:
a.        Access the administrator's mail file.
b.        Display the application properties.
c.        Click the Database Info tab, make sure that the ODS version is 51.
d.        Click the Advanced tab, and then under Advanced options make sure that the application is configured to Use Domino Attachment and Object Service.

• Comments [0]

Enabling DAOS on the server

 

1.        Add the following string to the notes.ini file on the Domino server: Create_R85_Databases=1. This parameter configures the Domino server to create new Notes applications using the Notes and Domino 8.5 ODS (On Disk Structure). By default, new applications in both Domino 8.0 and 8.5 are created with an ODS of 43 unless an .ini parameter is in place. For more detail, refer to Technote 1267844..
2.        Perform the following steps to enable transaction logging for the Domino server:
a.        Edit the Domino Server document.
b.        Navigate to the Transactional Logging tab.
c.        In the Basics section, change Transactional logging to Enabled. A message will display advising you to place the log files on a separate drive. This is not necessary in a test environment.
d.        Set the Maximum log space to 2000 MB. If you leave this field blank, you receive an error when trying to save the Server document. The error explains that an entry is required and that the minimum recommended value is 192 MB.
e.        Accept all the other defaults.
f.        Save and close the Server document.
g.        Restart the Domino server for the change to take effect.
h.        As the server is restarting, you will see console messages that reflect this change. This is correct behavior. This process can take several minutes. In some cases, it can appear as though the server is not processing. Give it a another minute or two.
3.        Perform the following steps to enable DAOS in the server's Server document:
a.        In the Domino Server document, navigate to the DAOS tab.
b.        In the field for enabling DAOS, specify Enabled.
c.        Accept the default minimum object size and DAOS base path (the Domino\data\daos directory).
d.        Save and close the Server document.
e.        Restart the Domino server.
Applications on this Domino server can now use DAOS.
4.        In the Domino server console, enter the show server command. The command reports the status of DAOS. Enabling DAOS in the server document results in the following changes:

• There is now a DAOS folder located beneath the server's Domino\Data folder: ...Domino\Data\DAOS. This is the default location of the consolidated object store repository.
• The DAOS Catalog (DAOScat.nsf) has been created. You will learn more about DAOScat.nsf in a subsequent exercise. If you do not see the DAOScat.nsf listed on the Files tab in your Domino Administrator, restart the Administrator client.
  

Note: Enabling DAOS within a Domino Server document does not configure any databases to use DAOS. Administrators and database managers choose which applications "participate" in DAOS. In the next part of the exercise, you will configure both new and existing mail files to use DAOS.

• Comments [0]

DAOS catalog

 

The DAOS catalog

The DAOS catalog (DAOScat.nsf) is the central map of database references (tickets) to .NLO files.

Each DAOS-enabled server maintains its own DAOS catalog. Each DAOS catalog stands alone and does not replicate or synchronize with the DAOS catalog on other servers in any way.

Each server's DAOS catalog must stay synchronized by synchronizing the references to the .NLO files held by each database on the server with all the .NLO files (the consolidated object store repository on that server).

The DAOScat.nsf cannot be opened by the Domino Administrator or anyone else. Even if an Administrator could open it, there is nothing to see that will mean anything. However, there are several tell DAOSMgr commands that report out the information needed from the catalog. For example, one option for reporting the catalog status is the tell DAOSMgr status command:
> tell daosmgr status catalog
10/07/2008 01:08:56 PM  DAOSMGR: Status CATALOG started
10/07/2008 01:08:56 PM  DAOS catalog status:
10/07/2008 01:08:56 PM  catalogState = SYNCHRONIZED
10/07/2008 01:08:56 PM  catalogVersion = 3
10/07/2008 01:08:56 PM  catalogMinVersion = 3
10/07/2008 01:08:56 PM  DAOSMGR: Status CATALOG completed  
For perspective, similar information is reported out by the show stat daos command:
> sh stat daos.engine.*
DAOS.Engine.Catalog = Synchronized
DAOS.Engine.Encryption = Enabled
DAOS.Engine.Status = Enabled
3 statistics found  

If a server's DAOS catalog needs synchronization, DAOS fires a DDM event. Administrators can choose to schedule a DAOSMgr resync in response to this DDM event. To learn more about the DDM event and resynchronization, read the Notes/Domino wiki article How to set up an automatic resynchronization ddm event. An Administrator can also run tell DAOSMgr Resync at any time to manually synchronize the catalog on demand.

Evaluating tell DAOSMgr commands
Run each of the following tell DAOSMgr commands at your server console and observe their output:
1.        tell DAOSMgr Status
Displays status of various DAOS Manager operations.
2.        tell DAOSMgr Status Catalog
Displays status of the DAOS catalog.
3.        tell DAOSMgr Dbsummary
Displays status of all DAOS-enabled databases.
4.        tell DAOSMgr Databases
Displays status of all DAOS-enabled databases with additional details, for example, a database's last resynchronization point.
5.        tell DAOSMgr ListNLO what to list
Lists DAOS objects (.NLO files) in the DAOS storage repository, allowing an administrator to identify documents whose objects may be missing after an event such as a server restore or the deletion of a database file through the operating system. You can restore the missing objects from backup sources. Files are missing when they are still referenced by documents in at least one database, but are no longer present in the repository.

You can enter -o to specify the name of an output file, the keyword ALL or MISSING to list all or just missing files, and the name of a database whose objects to list. For example: tell daosmgr listnlo -o mymailobjects.txt MISSING mymail.nsf or tell daosmgr listnlo -o mytest.txt ALL mail\mymail.nsf
Note: The text file is created on the fly in the Domino directory.
6.        tell DAOSMgr Resync
Resynchronizes DAOS-enabled databases with DAOS objects in the storage repository. Resynchronization is necessary whenever DAOS reference counts need to be recalculated, for example when there has been a database restore, deletion of a database through the operating system, or any other event that can invalidate the count.

Resynchronization corrects mismatches between reference counts in the DAOS catalog (DAOSCAT.NSF) and actual references to objects found in the DAOS enabled databases. When a mismatch is detected, DAOS disallows pruning (deleting from the NLO repository) of attachment objects (.NLO files) until DAOS is synchronized using this command shown on the left.

If you run the command and it starts and stops quickly, then the catalog is synchronized. If it is not synchronized it may take a while because this is what it does:

• scans all the databases enabled for DAOS
• asks each database what references(tickets) to .NLO filess are held by it
• updates the record in the DAOScat.nsf to match what it has found during its scan

If you want DAOS to resynchronize the catalog even if it is already reporting to be synchronized, then you can run the tell daosmgr resync force command.

• Comments [0]

Hangs et Crash serveur Domino

 

Avant de rentrer dans les détails techniques, voici la définition des termes, crash et hang, pour s'assurer que nous somme sur la même longeur d'onde.

Crash server

Un serveur Domino crash et la situation dans laquelle le programme server se termine de façon anormale et ne tourne donc plus. Il est souvent possible de déterminer la tâche qui était en cours lors du crash en regardant lee fichier log ou le fichichier NSD (hotoriquement le fichier RIP pouvait aussi être utilisé sur Windows sur des version antérieure à la version 6).

Les symptomes les plus courants d'un crash :

• The Domino server is no longer running, but other programs on the system are still running.
• The Domino server console does not appear, even when tasks appear to be loaded.
• The Domino server loaded and abruptly came down without doing anything.
• A panic error appears on the console or in Log.nsf, and the system comes down.
• NSD/RIP automatically runs and generates a file, and the server comes down and/or restarts by itself.

There are several different types of server crashes. For example, a one-time crash, as the name implies, may occur once and never appear again. A one-time crash may be caused by bad memory or a corrupted document accessed by a process that resulted in Domino crashing. For example, suppose a document deposited in Mail.box is corrupted. When the Domino router accesses Mail.box to route the document to its destination, this produces a Domino server crash. A similar situation may or may not occur in the future. In general, one-time crashes are the most difficult to analyze.

A reproducible crash is one that can be repeated by following a sequence of steps. One example is a form that includes a badly coded button that always results in a crash when pressed.

Repetitive crashes occur on a particular schedule. They don't seem to be associated with any specific actions; instead, they may happen at the same time every day. In such situations, you need to identify exactly what is getting executed on the server at that time that may be causing the problem. For instance, imagine that a Domino server has a scheduled agent enabled that runs every month. This agent may be producing the server crash. In such scenarios, you need to first disable the agent creating the problem and then review why the agent is causing the problem (and fix it).

An ABEND is a special form of server crash. The term ABEND is a combination of the words "abnormal end." ABEND crashes do not produce RIP or NSD files.

Causes of crashes include:

• A software problem in the code (either on the server or on the client).
• Corruption in a database.
• A software problem in a third-party application accessing Domino.
• Insufficient memory.
• Restricted operations caused by customized code.
• A memory leak.
• An incomplete request.

Server hang

A Domino server hang is a situation where the Domino server is still running, but one or more tasks on the server are not responding to requests. These tasks may still be active, but they are not doing what they are supposed to do. The term "hang" also defines a state that sometimes occurs when computer programs do not run as designed. Most of the time, a hang occurs due to a low-level loop or a permanent unavailability of a resource, causing serious performance issues. (Server hangs are most commonly attributed to resource issues, so they are sometimes considered performance problems.)

During a hang, the program seems to be paralyzed, no error messages are displayed, and the screen freezes or the application does not respond to users' actions. Keyboard input or mouse clicking has no effect, regardless of where the cursor is placed, but the program is still running. Unlike an ABEND or crash, sometimes a hang will resolve itself, and the application resumes its normal execution without your involvement. Such a case might be considered more of a performance issue than a hang.

Symptoms of a Domino server hang include:

• Domino is still running, but is not responsive to clients. In this case, users often report that they are receiving "Server not responding" messages.
• The console behaves as if it is disconnected and won't accept any commands, not even a simple command such as quit.
• Clients accessing the server (for example, opening databases) are experiencing slow response times.
• Semaphore timeouts are occurring. The 'show stat' command will record semaphore timeout information. The following is an example of semaphore timeouts recorded in Statrep.nsf: Sem.Timeouts = 430D: 58 0A13:42 030B:28 0116:26 0A12:21. In this example, 430D is the semaphore name, and 58 is the number of timeouts. Note that semaphore timeouts do not always indicate a performance problem. It is common for semaphore timeouts to occur on a busy server. The statistic Sem.timeouts will not appear in Statrep.nsf if the server has not experienced any semaphore timeouts.
• Performance-related error messages are reported, such as:
  Insufficient memory.
  Insufficient memory. NSF Folder Pool is full.
  Maximum number of memory segments that Notes can support has been exceeded.
  Network operation did not complete in a reasonable amount of time.
  Server not responding.

Note that in a server hang situation, an NSD/RIP is never generated automatically.

Causes of server hangs include resource problems (insufficient resources), third-party application conflicts, and hardware problems. In general, server hangs are more difficult to analyze than server crashes. One final note: crashes and hangs not only occur on the Domino server, they can also happen on the Notes client.

Troubleshooting

In this section, we examine some general approaches to troubleshooting server crashes and server hangs.

Troubleshooting Domino server crashes

If Domino has crashed and is not able to restart, remove tasks from the Notes.ini variable Servertask and attempt to narrow down and identify the task causing the crash. When you suspect a particular task is causing the problem, open the server console and narrow down the possible error messages generated by task. For example, if the router crashed while accessing mail in Mail.box, rename Mail.box and allow the server to recreate Mail.box.

If you suspect the problem is caused by a corrupted database, run offline maintenance tasks on this database. If the crash is occurring on a scheduled basis, review the actions performed on the server at the time of the crash.

Consider the following questions:

• Is the Domino server reporting error messages to the console or the log file?
• What is the exact syntax of the error message?
• Where is the error message being generated, on the Domino server or on the Notes client?
• When did this problem first appear?
• Did you implement any recent changes before the problem started appearing?

Troubleshooting Notes client crashes

First, find out whether or not the problem is specific to a single user. If so, check the configuration of that user and compare it to configurations for other users. Also, determine whether or not the problem happens due to a specific application being accessed. If so, review the application with a developer.

If you suspect the problem is caused by a corrupted database or document, run the maintenance tasks Updall, Fixup, and Compact (with appropriate switches). Also, try to recreate the database's full-text index, if possible, if you think the problem is due to a bad index.

Troubleshooting Domino server hangs

If constant semaphore problems appear on the server console, check whether or not the tasks' schedule is conflicting. If the system is responding slowly, check your non-Domino applications to see whether or not they are also performing slowly. Additionally, as a general rule, make sure your operating system is updated with all the latest patches.

NSD analysis
Determining the process that crashed the server is often the first step in resolving a server crash. In Domino 6 and later, the NSD file can be a good place to start. NSD gives you all current information about the state of the server (call stacks for all threads, memory information, and so on). In the event of a crash, an NSD log file will automatically be generated by the Domino server and stored in the data\IBM_TECHNICAL_SUPPORT directory. An NSD log will have a file name with a time stamp showing the time when the NSD was generated. For example: Nsd_W32I_KIRANTP_2006_01_17@17_17_18.log indicates this NSD was created on January 17, 2006. When NSD runs, it attaches to each process and thread, to dump the calls stacks. This can help you determine the cause of a server or workstation crash.

The "heart" of an NSD file is the stack trace section. This section provides a breakdown of the code path each thread in a currently existing process traversed to put it in its current state. This is very helpful in examining hang or crash situations on a server. Also, by examining the NSD file, you can find any core files generated in a Domino data directory, and can do a base-level analysis to trace the final stack of calls that were made by the process that died and left behind the core. In a complex product such as Domino, a stack trace of the same type of action on two different servers can produce different results.

In the NSD file, you can identify the executable in the failing process by performing a word search for "fatal," "panic," or "segmentation." By finding the process, we can see what preceded it, and hopefully determine how the crash occurred. When neither "panic" or "fatal" are found, sometimes a core dump will contain a reference to a "segmentation fault" in a function. This indicates that the process tried to access a shared memory segment that was corrupted for some reason, and will crash without calling "fatal_error" or "panic."

The following is a sample excerpt from an NSD file where a server process is involved in a crash:

### FATAL THREAD 39/83 [ nSERVER:07c0: 2764]
### FP=0743f548, PC=60197cf3, SP=0743ebd0, stksize=2424
Exception code: c0000005 (ACCESS_VIOLATION)
############################################################
@[ 1] 0x60197cf3 nnotes._Panic@4+483 (7430016,496dae76,0,496dace8)
@[ 2] 0x600018a4 nnotes._OSBBlockAddr@8+148 (1153f38,2000000,743f608,1)
@[ 3] 0x6000bd92 nnotes._CollectionNavigate@24+610 (0,743fc74,f,0)
@[ 4] 0x600626cc nnotes._ReadEntries@68+2860 (4c5440e8,4cfb8dba,800f,1)
@[ 5] 0x600b9f6f nnotes._NIFReadEntriesExt@72+351 (0,4cfb8dba,800f,1)
@[ 6] 0x10032d40 nserverl._ServerReadEntries@8+1424 (0,8d0c0035,4b64b5bc,4ae46dd6)
@[ 7] 0x100191fc nserverl._DbServer@8+2284 (41b0383,cb740064,0,23696f8)
@[ 8] 0x1002b8c8 nserverl._WorkThreadTask@8+1576 (4711d68,0,3,563fb10)
@[ 9] 0x100016cb nserverl._Scheduler@4+763 (0,563fb10,0,10ec334)
@[10] 0x6011e5e4 nnotes._ThreadWrapper@4+212 (0,10ec334,563fb10,0)
[11] 0x77e887dd KERNEL32.GetModuleFileNameA+465

When the failing process has been determined, you can focus on troubleshooting that particular process.

ServerTasks
If a server is crashing continuously (for example, every five minutes), a useful troubleshooting step is to temporarily remove the ServerTasksline from the server's Notes.ini file. The server can then be restarted and tasks can be loaded individually to determine which process is causing the crash.

Panic messages
When Domino detects an internal consistency error, or a condition that may lead to corruption of data or some other problem, it immediately calls a subroutine called Panic. This is a special construct used to continually monitor critical parts of the code as it operates. This helps catch problems as early as possible, before they escalate and possibly destroy data. When a panic takes place, it brings the system to a stop (and thus can be considered a controlled crash). Panics generate messages, sometimes in English and sometimes in code (for example: PANIC: 04:3C). You can give this code to Lotus Software Technical Support for further troubleshooting.

Troubleshooting tools

This section reviews some of the troubleshooting tools available to you when you encounter a Domino server crash or hang. Before using any of these tools, be sure to consult the Domino administration documentation. Also, the Domino self-help support page is a good resource for troubleshooting information.

RIP (Domino R5)

A RIP file is generated when a server crashes. This file contains information about what the server was doing when it crashed. It reports any crash on the system, not just ones related to Domino. RIP files are generated only in Domino 5.x. In Domino 6 and later, NSD serves the purpose formerly performed by RIP, and also includes additional capabilities not included in RIP.

For a RIP file to be generated, QNC.EXE needs to be loaded on the Domino server. The QNC.EXE program (often called "quincy") is the default debugger program that ships with Domino. The QNC.EXE program is usually located in the \Domino directory. To enable QNC.EXE, type "qnc -I" at the operating system's command prompt. You can also enable QNC.EXE by typing "qnc nserver" at server launch. If RIP files are not generated when the server crashes, check whether QNC.EXE is enabled. Normally, RIP files get created in the data directory.

NSD (Domino 6 and later)

As mentioned previously, Domino 6 and later provides the NSD feature. This is a file that contains information about the state of the server at the time of a crash. For more information, see the section, "NSD analysis," earlier in this article.

Memory dump (Domino 6 and later)

In Domino 6 and later, you can use the command "sh memory dump" on the server console to create a memory dump file. A memory dump contains information on memory currently used by Domino. This is very useful when troubleshooting performance problems and memory leaks. Normally, memory dump files get collected in the data\IBM_TECHNICAL_SUPPORT directory. A memory dump file name includes a time stamp for the time when the NSD was generated. For example:

memory_ KIRANTP_2005_09_14@17_50_08.dmp

Note: To record the available memory to a file instead of viewing it on the server console, enter the following server console command: sh memory dump >memory.txt

HTTP request logs

To troubleshoot issues related to Domino Web server crashes and hangs, Lotus Software Technical Support will often ask you to create an HTTP request log. To enable the default settings for request logs, edit the server's Notes.ini file and add the line HTTPEnableThreadDebug=1. This sets HTTP request logging at the default level. (To set the logging level to record more details, see the Domino administration documentation.) You can also enable HTTP request logging dynamically by entering "tell http debug thread on | off" at the Domino server console. With HTTP request logging enabled, Domino creates a series of files with the name htthr*.log. For example: htthr_a40_10_20050914@171556.log.

HTTP request logging should be used only for troubleshooting specific issues, and usually at the direction of and with assistance from Lotus Software Technical Support. Do not use request logging for other purposes, such as general administration. These log files grow in size over time, so you should not leave this setting enabled for long periods or you could consume all available drive space.

Automatic Data Collection

Notes/Domino 6.0.1 introduced the automatic diagnostic data collection tool, also known as Automatic Data Collection, or ADC for short. Automatic Data Collection simply means that, when a Notes client or Domino server crashes, the program gathers all the necessary data to debug the crash and sends it to a mail-in database when the client or server restarts. Administrators then have one location per domain in which they can see all the crashes that have occurred for all clients and servers. This will help eliminate the instances where an administrator or user may not be able to capture the proper data on a client or server crash.

Notes.ini settings

To troubleshoot performance and crash issues, you can enable the following Notes.ini debugging parameters:

• Debug_threadid=1 logs each process and thread ID for each server operation.
• Debug_show_timeout=1 turns on semaphore timeout messages to the console, and creates a semaphore text file called semdebug.txt.
• Debug_capture_timeout=10 time stamps each semaphore timeout message.
• CONSOLE_LOG_ENABLED=1 (Domino 6 and later) enables Domino console logging.

Fault recovery for server crashes

You can set up fault recovery to automatically handle Domino server crashes. When the server crashes, it shuts itself down and then restarts automatically, without any administrator intervention. Domino records crash information in the data directory. When the server restarts, Domino checks to see if it is restarting after a crash. If it is, an email is automatically sent to the person or group in the "Mail Fault Notification to" field.

A fatal error (such as an operating system exception or an internal panic) terminates each Domino process and releases all associated resources. The startup script detects the situation and restarts the server. If you are using multiple server partitions and a failure occurs in a single partition, only that partition is terminated and restarted.

New troubleshooting features in Domino 7

This section briefly discusses some new Domino 7 features that can help you analyze and correct server hangs and crashes.

Domino Domain Monitoring

One of the most significant and useful server maintenance and troubleshooting features in Domino 7 is Domino Domain Monitoring (DDM). This provides one central location for monitoring all the servers in a domain (or multiple domains). DDM uses programs called probes to gather server information from the individual servers, and then report back to a special database (DDM.nsf) where you can view the collected data. This allows you to monitor, analyze, and troubleshoot a large number of servers from a single Domino Administrator console.

Activity Trends

The Activity Trends feature lets you analyze "historical" server data, to help spot trends that can only be identified over an extended period of time. You can review this data to help predict and avoid future issues. This data is collected from the log file (Log.nsf) and the Catalog task, and stored in the Activity Trends database (Activity.nsf). The Activity Trends Collector task processes this data, and produces "trended" data that you can use for charting and resource balancing.

Writing status bar history to a log file

You can now enable Notes client logging of status bar messages to the local log file (Log.nsf) or to an external file that you designate. This can help you troubleshoot Notes client crashes. Use the Notes.ini setting logstatusbar=1 to enable logging of status bar messages to Log.nsf. To view the logged messages, open Log.nsf and then click the Miscellaneous Events view. Status bar messages are appended with Status Msg. To write the status bar messages to an external file, use the Notes.ini setting Debug_Outfile= with the Notes.ini setting logstatusbar=1. For example:
logstatusbar=1
Debug_Outfile=c:\temp\StatusBarLogging.txt

This logs status bar messages to the file StatusBarLogging.txt.

The Log.nsf file can also provide a snapshot of actions logged in the status bar before the Notes client crashed.

Fault Analyzer

Fault Analyzer is a new server feature that processes all new crashes as they are delivered to the Automatic Data Collection mail-in database. The Fault Analyzer task searches the database configured for Fault Report documents and determines whether or not the stack matches a crash that has already been seen by a user or server. It adds to the functionality of the Automatic Data Collection feature by analyzing the call stacks that are located in the Fault Report mail-in database, and evaluating them to determine whether or not there are other instances of the same problem.

Fault Analyzer is configured at the same time that you set up Automatic Data Collection (see figure 1). Use the Server Configuration document to set up Automatic Data Collection on the server and to enable or disable Fault Analyzer.

Figure 1. Configuring Fault Analyzer

If Fault Analyzer locates duplicate fault reports, the new crash is reported as a response to the original crash, and attachments are either removed from the response document to save space in the database, or they are saved with the response document.

Automatic Data Collection enhancements

When you use the Automatic Data Collection tool to gather information about server crashes, the server is now first checked to see if it is being run under the Domino Controller and, if so, uses the Controller logs. If not, the server is checked to see if console logging is enabled and, if so, uses the console output. Finally, data is extracted from Log.nsf if neither the Domino Controller nor console logging has been set.

Now you can select which files (using wildcards) will be collected by the Automatic Data Collection tool when it runs on clients or servers. On Notes clients, it is configured using a Desktop Policy Settings document (see figure 2).

Figure 2. Configuring Automatic Data Collection on the Notes client

On Domino servers, it is configured using the Server Configuration document (see figure 3).

Figure 3. Configuring Automatic Data Collection on the Domino server

This allows you to collect diagnostic files from other IBM products, as well as third-party add-ins.

There is a possibility that the output sent by Automatic Data Collection could be very large. If this becomes a problem, you can configure Automatic Data Collection to restrict the size of attachments sent by NSD and the console log to the Fault Reports database (see figure 3).

Shutdown Monitor

It often takes a long time for the Domino server to actually shut down after you issue a quit or restart server command. To avoid this delay, the Shutdown Monitor task ensures that Domino terminates when requested to do so. If the server doesn't terminate in the allotted time, the server will forcefully terminate and an NSD log will be generated before termination. The time limit is specified in the Server Shutdown Timeout field of the Automatic Server Restart section of the Server document, on the Basics tab (see figure 4).

Figure 4. Setting the Server Shutdown Timeout

The default Server Shutdown Timeout setting is 5 minutes. This feature can be disabled using the Notes.ini setting shutdown_monitor_disabled=1.

Process Monitor (Windows platforms only)

The Process Monitor task monitors the processes that should be running as part of the Domino server environment. (This task runs on Microsoft Windows platforms only; this functionality is implemented in Domino for Unix platforms without using a separate server task.) If any of these processes is missing, or if one terminates unexpectedly without completing the usual Domino termination routines, this task causes the server to panic and identify which process has prematurely terminated. The Process Monitor task works with Nprocmon.exe, which monitors the Nserver.exe process for abnormal terminations.

This feature can significantly reduce the number of abnormal termination problems, which otherwise are difficult to analyze (because it's often difficult to determine which process has terminated and caused the server problem). To disable the Process Monitor task, set the variable process_monitor_disabled=1 in the server's Notes.ini file.

Conclusion

In this article, we have defined the differences between a Domino server hang and a crash. We have discussed some troubleshooting procedures and tools you can follow when analyzing and fixing Notes/Domino problems. We also looked at new troubleshooting features introduced in Notes/Domino 7. You can consult this article whenever you encounter a hang or crash with the Notes client or Domino server -- which hopefully won't be very often!

• Comments [0]

Xpage

 

XPage un guide pas à pas depuis zéro SHOW106_Updated20090203.pdf

• Comments [0]

DAOS : Gains et mise en place en toute sécurité

 

Comme toutes les nouvelles fonctionnalités DAOS n'est pas toujours bien compris et son fonctionnement mis en doc'était probablement justifié, cependant en 8.5.1 il est temps de faire le pas. Vous trouverez des informations complémentaires et à jour sur le site d'IBM: DAOS, DAOS Backup and Restore et DAOS Best Practices Guide
Ce post a pour but de vous donner des pistes pour le déployer en ne prenant pas de que peu de risques.

Tout d'abord il faut préciser que DAOS est local au serveur sur lequel il est activé.  En prérequis le serveur doit utiliser le Journal de transaction.
Si vous utiliser le stockage DAOS (où les attachement seront stockés comme des fichiers .NLO) il doit être placer sur un disque accessible au serveur.
L'utilisation de disque monter en réseau est une très mauvaise idée. DAOS tourne mal très rapidement si le montage réseau est perdu, sans parler des problèmes de performance sur un disque réseau. Les fichiers .NLO sont chiffrés avec l'ID serveur par défaut, bien qu'il soit possible de desactiver le chiffrement, c'est une très mauvaise idée. Cliquez ici pour voir comment.

Le système de stockage est spécifique au serveur. Si vous avez 2 serveurs qui répliquent leur données, il est possible d'activer DAOS sur l'un et pas sur l'autre. Si l'activation est faite sur les deux chaque serveur gérera son propre .NLO. Si un seul utilise DAOS, l'autre serveur stockera les attachements dans les bases .nsf de façon traditionnelle. DAOS agit en fond de panier au niveau du serveur. en raccourci le serveur domino qui réplique ne sait pas si DAOS tourne sur son voisin.

Avec un cluster, c'est la même chose, un ou les 2 serveurs peuvent utiliser DAOS. Et il est facile d'activer ou de désactiver DAOS.
Si c'est off, les attachements sont dans les .nsf. Si c'est on, les attachements sont placer dans le .NLO. MAIS 2 SERVEURS EN CLUTER NE PEUVENT JAMAIS PARTAGER UN MÊME STOCKAGE NLO !! En effet les fichiers .nlo sont chiffrés par l'ID serveur.

Au vu de ces quelques lignes il devient assez simple de mettre en production .NLO de façon progressive et en maitrisant le risque :
- Commencer par activer DAOS sur un membre d'un cluster pivot de réplication.
- Activer DAOS sur des serveurs d'archivage de messagerie. (Pour la sauvegarde, sauvegarder aussi le NLO) - Vous contaterez un gains d'espace de plus de 50
- Ensuite passer aux serveurs de messagerie sur un membre de vos clusters.

Jeter un oeil sur la présentation sur DAOS (et IDVault by the wonderful Gabriella Davis) adminblastr1topresent.pdf

Estimer le gain dans votre environnement:

• L'outil DAOS Estimator arrive en version 1.5 vous permet de voir à quel point ce mode est utile et vous permettra des gains d'espace et de performances.

Sur des serveurs messagerie ou de sauvegarde entre 15 et 40% de gain de place (A partir de 100 Go de données). L'analyse peut se faire sur un serveur V6 ou V7 est simple à utiliser.


Sauvegarde des serveurs utilisant DAOS ?

Quand une base est configurée pour utiliser la consolidation d'attachement , la sauvegarde du serveur implique de rajouter le backup de tous les fichiers NLO stockés dans le dépôt DAOS. Ces objets ne sont pas sujets à de fréquente modification, aussi après une première sauvegarde, vous pouvez utiliser un backup incrémental sans problèmes ou perte de temps.

NOTE:

Cette procédure suppose que, on cas de défaut vous voulez restaurer les fichier sur le serveur d'origine. Les fichiers NLO étant chiffré avec les clés du serveur d'origine, il sont lissible uniquement sur ce serveur.
1.         Si vous utiliser la suppression différée avec  DAOS, indiquer un intervalle supérieur à l'intervalle entre deux sauvegardes. Si un backup par semaine, spécifier au moins 8 jours dans le Champs  "Defer deletion of DAOS objects n days" du document serveur.
2.        Sauvegardera les fichier NSF avec un utilitaire compatible avec les fichiers NSF. Cet utilitaire doit être capable de faire appel au API de backup et de restauration du  Toolkit Lotus Domino C API .
3.        Sauvegarder les fichiers  DAOSCAT.NSF et DAOS.CFG situés dans le répertoire data.
4.        Sauvegarder tous les fichiers NLO du dépôt DAOS. Vous pouvez utiliser n'importe quel utilitaire de sauvegarde pour fichier "à plat". Si DAOS à créer des sous-répertoire, maintenir la hiérarchie lors du backup..
5.        Après un premier  backup du dépôt DAOS des fichier .NLO, les fichiers NSF devant être sauvegardés le sont par les moyens normalement en vigueur.
6.        (Optionel) Il reste très fortement recommandé par IBM d'archiver toutes les transactions logs ainsi tous les changements (utilisation du TL en mode archive ).

• Comments [0]

iNotes Ultralite

 

IBM annonce la disponibilité de sa suite collaborative Lotus Notes et Domino sur les iPhone d’Apple. IBM l’avait annoncé il y a déjà plusieurs mois, et c’est désormais chose faite. Les outils Notes et Domino sont désormais accessibles sur iPhone, via  web iNotes Ultralite (téléchargeable en cliquant ici). Reste que la solution full iphone en mode non connecté ne sera disponible que Q2 2009.... Par ailleurs, ce portail est une belle vitrine technologique qui devrait redorer le blason des produits Lotus si les probléme de performances sont rapidement solutionnés.

• Comments [0]

Revue d’architecture avant migration V8

 

Avant de procéder à la mise à jour d'une infrastructure Domino avec une nouvelle version Majeure telle que la V8.02 qui semble un bon candidat il vous faudra identifier  les composants qui seront touchés par cette mise à jour. C'est l'opportunité rêvée pour effectuer un bilan de santé complet de votre architecture. Ce n'est pas un luxe c'est un pré-requis à une migration. Serveurs Lotus Domino: Inventorié tous les incidents connus, les craches, les problèmes serveurs, et les accès trop lent. Vos serveurs doivent être testés et validés avant l'upgrade. Effectué une migration dans un environnement de test sur un pilote sur un serveur de même type. Utiliser server.load pour évaluer les performances. Assurez-vous aussi qui le serveur n'a pas de défaut, inutile de faire un upgrade sur un serveur qui crache ou qui a des problèmes matériels. Monitoring vos systemes (Tivoli, DDM, BMC, and so on): Il y a de nombreuses nouvelles fonctionnalités dans  Domino 8. Assurez-vous que le monitoring existant fonctionnera avec Domino 8, et qu'il n'hésitera pas de conflits avec les nouvelles fonctions. Architecture Annuaire (Analyse annuaires, personnalisation annuaires): C'est le plus grand pas. Analysez votre annuaire et déterminer s'il y a ou dnon des personnalisation.  Déterminez les éléments de structures (vues,masque et autres) qui doivent être mis dans la nouvelle structure. Souvent, vous pourrez vous rendre compte que telle ou telle adaptation n'est plus nécessaire en Domino 8. Clients: Testez vos  clients, et assurez vous que matériels et OS supporteront  Lotus Notes 8. PDA et dispositif sans fils: Domino 8 ajoute des nouvelles fonctions.Assurez-vous qu'aucun conflit n'existe avec vos PDA. Un exemple, dans le passé un changement d'ODS a cassé la connexion entre le  PDA et le Client Notes. Status AdminP : Vérifier qu'admin4.nsf replique correctement entre tous les serveurs Lotus Domino serveurs, et que les LCA sont correctes. Cela vous permettra de configurer plusieurs serveurs  en utilisant la LCA Extended Directory. Analyse des Applications: Incluez tous  problèmes rencontrés dans les applications à upgrader, modèle spécifique ou personnalisé, et analyse des utilisation d' API. Assurez un service de test pour les applications avec Domino 8. Dans le cas général un upgrade en Domino 8 ne doit pas provoquer d'incident, mais il toujours bon de tester une mise à jour. L'utilisation d'APIs customiser doivent être contrôlées. Dans certains cas, il est possible qu'une recompilation soit nécessaire, dans d'autre cas vous n'aurez plus besoin d'APIs. Modèle spécifiques: Vérifiez les adaptation faites au modèle système standard. Comparez les adaptations avec les nouvelles fonctions Domino 8 afin de déterminer ce qui reste ou non nécessaire. L'utilisation de  IVES Team Studio Delta vous aidera. Pour une grosse Entreprise il est possible que plusieurs systèmes système de messagerie cohabitent. Testez chaque interface spécifiques, logiciels et connexion SMTP. Attention à la nouvelle configuration V8 d'agent d'absence-- vous pouvez configurer lle routeur pour gérer les absences  à la place de l' agent standard. Autres services et serveurs: Un grand nombre de produit Lotus/IBM existent. Tous nécessitent un test (Quickplace, Sametime, LEI, passerelles SMTP, anti virus, service de sauvegarde, et système de provisioning. Assurez vous que les produits utilisés sont supporter avec Domino/Lotus Notes 8. Replication Domino (activity logging, topologie de replication, paramètres de replication, document de connexion, contrôle d'accès, horaire de replication, replication grappe. JeIl n'y a pas de problème identifié sur cet aspect mais un contrôle de votre part n'est pas de trop. Topologie de messagerie (Topologie serveur, réseaux nommés, domaines, flux de messagerie entrant et sortants, routage, priorités, stratégie clients, serveur versus mode local répliqué, clients alternatifs  [POP, IMAP, web, utilisateurs mobiles], pratiques recommandées [Treo vs. Blackberry]): En V7 une tâche de gestion des salles et des ressources a été rajoutée, attention a intégrer cette partie dans votre migration. Applications utilisant le mail: La plupart des architectures disposent d'applications qui utilise la messagerie. Elle peuvent, et seront affectées par une mise à jour . Bien que Lotus Notes et Domino assure une très bonne compatibilité ascendante vous devrez regarder les améliorations possibles apportées par les nouvelles fonctions  LotusScript , les nouvelles "@Functions", et les nouveaux éléments de structures. Au minimum vérifiez que les mailling database fonctionnent correctement. Architecture (revue générale, connexions aux systèmes internes [réseau, messagerie unifiée, domaines SMTP/Internet}). Réseaux (plate-forme, DNS/DHCP, accès distant): Il n'y a pas d'impact prévisible mais assurez vous que les bases fonctionnent. Agenda  [délégation, accès gestionnaires], entreprise [ressources, calendriers groupes]). Annuaires (l'architecture annuaire  [particulièrement la structure], gestion et fédération d'annuaire, nommage [Serveurs, utisateurs, O et  OUs]). Securité (LCA, accès anonymous, encryption et certificats, pratique de certification, structure de l'organization structure,gestion des  ID, contrôle d'accès  [file system sur les serveur, console et accès physique au serveur(pass-thru/deny), ECL, accès administration ]). Capacity planning: Assurez vous que les serveurs peuvent recevoir les utilisateurs  (taille des boîtes aux lettres, dimensionnement matèriel), load balancing, D'expérience chaque nouvelle version procure de meilleures performances coté CPU et mémoire et plus de fonctionnalités. Avec chaque nouvelles fonctionnalités ou fonctions réclament de nouvelles ressources (système)  lorsqu'elles sont activées, surveillez la charge via des statistiques de base afin d'estimer l'impact. Configuration: Il est très important de revoir la configuration de chaque serveur pour savoir si des changement sont nécessaires. Variable d'environnement: Vérifiez les variables notes.ini pour supprimer les variables obsolètes. Vérifier sur le support en ligne d'IBM pour en avoir la liste. Les release notes peuvent aussi fournir des informations  sur les variables notes.ini supportées. Gestion et  administration (contrôle du changement, modèle d'administration, gestion client, accès à distance, service monitoring et reporting, gestion système, sauvegarde et modèle de restauration).

• Comments [0]

Comment reconstituer le dossier "Courrier en Arrivée"

 

Une Technotes vous donnes une serie de solution.
http://www-01.ibm.com/support/docview.wss?fdoc=wplcnote&rs=475&uid=swg21104973

Un cas non pris en comptes et la réplication avec une vieille base alors que la structure a évoluer sur le serveur. Cela peut arriver dans des cas limites, si l'utilisateur c'est absenté plus de 30 jours après l'application d'une structure (V8 par exemple). Le  dossier ($Inbox) se retrouve en double et des problémes apparaissent alors. Il suffit de supprimer (ou mieux de renommer au cas où..) le dossier ($Inbox) qui ne référence pas de documents...

• Comments [0]

ASSP :proxy SMTP

 

La signature des mails SMTP sortants avec DKIM permettant permet de limiter les possibilités de spoof offertes aux spammeurs.
La principale difficulté  est de savoir comment implémenter les mécanismes sur des versions de MTA smtp où la technologie n'est pas disponible (domino !!) ou dans des versions non encore déployée ?
Pour les petites structure, une solution simple et efficace est la mise en place d'un proxy SMTP anti-spam chargé de la signature et des action anti-spam.
La solution  ASSP (AntiSpam SMTP Proxy).et opensouce : http://assp.sf.net

De quoi donner des idées aux éditeurs....
Cisco et Yahoo! ont créé Domain Keys Identified Mail (DKIM). Elle impose l’ajout d’une signature numérique  à tous les mails sortants, ce qui permet aux destinataires de vérifier l’identité des expéditeurs.
Ainsi, une mauvaise corrélation entre l’envoyeur et la signature permetd’identifier un spam voire un message d'attaque de type « phishing » et ce mail pourra facilement être supprimé par le biais d’un filtre.

Le standard proposé est  l’union de deux technologie : le DomainKeys de Yahoo ! et l’Identified Internet Mail de Cisco.
Alt-N Technologies, America Online, EarthLink, IBM, Microsoft et Verisign ont activement contribués.
Microsoft est un des membres ayant contribué à l’établissement de DKIM. L’éditeur avait déjà fortement appuyé la candidature du standard « Sender ID » proposé par Sendmail.

• Comments [0]

1 minute - 5 trucs

 

Astuces de bases, que tout admmistrateur ou programmeur Lotus Notes se doit de connaitre (V8)
#1: Etendre ou reduire la retention des  Logs
 Le parametrage de la retention dans la base  log.nsf par defaut des logs peut etre trop court ou trop long
 En general 14  jours  de journaux pour un petit serveur.. 2 jour pour un tres gros ....
 Pour cela dans  NOTES.INI sur le server
 LOG=LOG.NSF, 1, 0, 14, 40000
 “14” est le nombre de jours de retention ...
 LOG=LOG.NSF, 1, 0, 2, 40000
 “2” est le nombre de jours de retention ...

#2: Redemarrage de tache
 Pour redemarrer qui n'ont pas de fonction "restart"?
 Utiliser  la commande RESTART TASK
 Exemple: restart task router
 Exemple: restart task adminp


#3: Commandes Agent Manager
Pour Voir la plannification des agents qui tournent sur votre server
 A la console  “Tell amgr show schedule” on the console
 Pour forcer un agent a tourner depuis la console
 tell amgr run “database.nsf” 'nom  agent'
 Note: Les doubles quotes ou les simple quotes sont necessaires.

Tip #4: Parametrage du Maximum de Sessions
 Preciser le nombre de sessions qu'un serveur Domino acceptera avant de refuser des requetes
 Mettre  Server_MaxSessions=n
 Par Defaut = Pas de limite
 La limitation des requetes permet :
 De ne pas saturer un serveur au ressources limitees ... :-)
 Limiter les agents filous qui ouvrent trop de sessions ...
 Faire du load balancing dans le cadtre d'un cluster (grappe)

#5 La commande Restart server redemarre le serveur au bout de 10 secondes..
 Souvent trop court ...
 Dans le cas de tache additionnelle ou de serveur particulierement charge
 Sametime
 BlackBerry enterprise server
 Changer la valeur pour plus long ....
 SERVER_RESTART_DELAY=n
 N = valeur en  secondes




T

• Comments [0]

Désactiver l’affichage de "Search IBM Technotes"

 

Suppression de l'affichage de la boîte de dialogue "Search IBM Technotes"  .
En V8 du Client la boîte de dialogue "Search IBM Technotes" apparait lorsqu'une erreur apparait permettant d'afficher les technotes relatives à cette catégorie d'erreur.
Cette fonctionnalité sympatique risque d'agacer plus d'un utilisateur non anglophone.
Pour éviter l'affichage rajouter la variable DoNotShowDetailsButton=1  dans le notes.ini du client.
Cette variable est mentionner dans le readme.nsf de la version...


New "Search IBM Technotes" button on error boxes

Clicking the "Search IBM Technotes" button that displays on a subset of error message dialog boxes will perform a search of the IBM support site's technotes about that error, and return the results.  You can suppress the display of the button on these dialogs by adding the Notes.ini parameter DoNotShowDetailsButton=1 to your Notes client.

• Comments [0]

Mise a jour 8.01

 

Une collection de technotes sur la mise à jour en Domino 8

• Comments [0]

Date de fin de vie des produits Lotus

 

Pour connaître les dates de fin de vie des produits Lotus : http://www-306.ibm.com/software/lotus/support/lifecycle/

• Comments [0]

Performances Serveur V8 et Client V8

 

Maintaining IBM Lotus Domino V8 mail server scalability with the IBM Lotus Notes V8 client is critical, and this article shows that Lotus Domino V8 not only equals, but outperforms the previous release. Let us show you how Lotus Domino V8 with the Lotus Notes V8 client performs across a variety of server platforms.

Learn more:
http://www.ibm.com/developerworks/lotus/library/domino8-performance/

• Comments [0]

Tips and tricks .. admin

 

Série de mini truc en anglais .. Le temps me manque
Basé sur une présentation de Paul Mooney / Blue Wave Technology.
3 minutes de lecture, des heures de gagner....

Cluster Commands: Créé une base ou une réplique
- Vous pouvez créer une base depuis un serveur vers un autre en utilisant les commandes consoleserveur
  CL copy serverA!!db1.nsf serverB!!db2.nsf  Créer une copie Notes (Pas une réplique)

- Utilisation de paramétres divers
- CL copy serverA!!db1.nsf serverB!!db2.nsf REPLICA créé une réplique
- CL copy serverA!!db1.nsf serverB!!db2.nsf TEMPLATE créé une copy de design seul
- CL copy db1.nsf db2.nsf Créé une copie sur le serveur lui même
Fonctionne avec ou sans cluster défini - toutefois le paramètre  CLUSTER_ADMIN_ON doit être activé

Mail Configuration Updates

• Apply router configuration changes immediately
• Type “Tell router update configuration” on the console
• Get delivery stats from the router
• “Tell router delivery stats”

Saving Mail File Space with Single-Copy
- Modify the template to become a single-copy template
- Run the design task
- Updates mail databases’ property from the template
- Run the compact task
- Saves approx 10MB per mail file

SMTP Port Forcing
- Using multiple network cards in a Domino server, you can force SMTP traffic through a specific port to the appropriate card (or any internet port other than HTTP)
- Allows splitting of traffic by port, i.e., NRPC vs. SMTP
- Useful in DMZ environment
- Map the IP address to the port using the SMTPNotesPort ini variable
as shown in the example below
Ports=TCPIP, TCPIPSMTP
TCPIP=TCP, 0, 15, 0
TCPIP_TCPIPAddress=0,10.12.51.1:1352
TCPIPSMTP=TCP, 0, 15, 0
TCPIPSMTP_TCPIPAddress=0, 207.41.72.20:1352
SMTPNotesPort=TCPIPSMTP

Limiting the Availability of DWA Tabs
- Domino Web Access (DWA) interface loads all tabs by default
- Welcome Page, Mail, Calendar, To Do, Contacts, Notebook
- What if you want to limit the tabs?
- For instance, only have users see the Mail and Contacts tabs
- Starting in 7.0, the ini variable, iNotes_WA_Areas, allows enabling and disabling of tabs

DWA Performance — Reuse Windows
- To force DWA to reuse windows instead of opening up new browser windows every time a link is clicked, use:
- iNotes_WA_ReuseChildWindows=1
- This ini variable is available with the 6.5.3 performance fix and above

DWA Performance — Use Cached Icons
- To improve DWA performance, create a Web Site Rule document to prevent repeated retrieval of icons

Troubleshooting HTTP Configuration
- Issue a Tell command at the server console
- Tell HTTP Dump Config
- Dumps HTTP configuration to HTTPCFG.txt in:
- x\Lotus\Domino\data\IBM_TECHNICAL_SUPPORT
- Excellent method of getting full configuration of HTTP stack and includes:
- Rules
- Port settings
- Don’t forget “Tell HTTP refresh”
- Rereads HTTP config without restart

HTTP Logging — DOMLOG.NSF File Size - Don't use this stuff ... but if you have to..
- DOMLOG.NSF records all GET and POST requests, so it can become very large
- You can ignore certain requests
- All image requests
- All GET requests
- Requests from certain IP addresses
- For example, to ignore GET requests:
1. Go to the server document
2. Then, Internet Protocols/HTTP tab
- Exclude from logging section
- Requires HTTP refresh to take effect

HTTP DOMLOG.NSF Cleanup
- Another way to decrease the size of the DOMLOG.NSF database is to enable the cleanup Agent
- This purges data over 10 days old from the database

Restricting the HTTP Upload Size
- Earlier versions of Domino had no limit on uploaded attachments
- Performance and stability issues occur if no limit is set
- As of Release 5.x, you can control the POST size
- Set the Maximum POST data field in the Server document
Note: If Internet Site documents are used, the POST size can be set in the Site document instead

HTTP and Internet Passwords
- HTTP password changes are cached on the server
- Can confuse users
- At some point, both their old and new passwords work!
- HTTP_PWD_CHANGE_CACHE_HOURS=0
- Set in the notes.ini file
- Prevents both passwords from functioning
- The moment the user changes his/her password, it is the only active password

HTTP Web Agents
- Agents initiated by an HTTP application are NOT managed by the AMgr task
- They are managed by the HTTP task
- This is useful to know in order to debug major HTTP peaks

HTTP Web Agent Timeouts
- Troublesome HTTP Web Agents can hurt HTTP performance
- Reporting Agents are an example
- For example, if the user clicks a button that generates a large report over a browser, this could affect the HTTP stack (consuming resources)
- Set HTTP Agents to timeout after x seconds
- Default is not set
- Poorly configured HTTP triggered agents could “hurt” your server

Restricting Web Access
- The database property, “Don’t allow URL open,” ensures a database will not be opened from a Web client
- Restricts: http://Host/Database.nsf/* commands
- Sends 500 Not Authorized error

Database Creation
- When creating new replicas of databases, or ensuring that replicas exist, use the Admin client to create the replicas from the Files tab
- Right-click on the folder that contains the files to replicate and then choose New Replica(s)
- The request for replica creation of all databases in the folder is submitted to ADMIN4.NSF

Clustering Over Private Ports
- A typical clustering architecture has a private NIC between cluster servers and a “public” NIC for user access over LAN/WAN
- Force cluster traffic through the private NIC
- Public switch will not be flooded with traffic from clrepl task
- Public NIC accepts user/server traffic — not flooded with cluster traffic
To force the cluster traffic through a private NIC:
1. Give each NIC an IP address
2. Create two ports in Domino server
- Admin client/server tab/ports option
3. Create two ports in the Server document
- Ports section/Notes network ports
4. Map the ports to the IP address
- portname_TCPIPADDRESS=0,192.168.0.1:1352
5. Map cluster traffic to the port
- SERVER_CLUSTER_DEFAULT_PORT=portname

Cluster auxiliary port (ND8)
- What if the private NIC fails?
- You should have standard replication as a backup to cluster replication anyway
- For a few reasons!
- Server_Cluster_Auxilary_Port=*
- Tells the cluster engine to failover to alternative port if default port is unavailable

Cluster Work Queues
- Cluster performance is dependent on the work queue depth
- Type “Sh stat replica” on the console
- Look for cluster work queue depth statistics
- Work queue depth is critical to cluster performance

Customizing Client Failover Errors
- When a server fails with a database open, a user gets this message, known as Error 0807
- Or, a user might get this message, known as Error 0A02
You can change the error messages by adding these lines to your NOTES.INI file
- Err_0807=Your e-mail server is no longer responding. However, you may be able to switch to a backup server and continue working. To do this, you must close your mail file and re-open it.
- Err_0A02=Your e-mail server is no longer responding. However, you may be able to switch to a backup server and continue working. To do this, you must close your mail file and re-open it.

Clustering and Replication Settings
- Replication formulas are IGNORED by cluster replication
- All data is transferred regardless of replication formulas
- Data that “should not” be replicated will be removed by standard replication

Enable Cluster Commands (Even Without !!)
- To use some “documented” features of a cluster task
- Set config CLUSTER_ADMIN_ON=1
- A server DOES NOT have to be in a cluster for this to work!

Fixing Bookmark.nsf Corruption
- In the case of local design element corruption, you don’t always have to delete bookmark.nsf!
- For example, users get errors when opening databases from the server
- Removing the cache and bookmarks resolves it
- It really annoys users!
- Open the bookmark.nsf database
- Hold CTRL + SHIFT and click View Go To
- Select (ByURL) view
- Select all the documents
- Delete them


Collecting All Database Information from the Catalog
CATALOG.NSF database records all database information that has the following fields checked in database properties
- In fact … the catalog.nsf holds ALL database and template information!
- Hold down CTRL + SHIFT when opening a database
- Select $ReplicaID view
- All databases/templates listed
- Regardless of the db property checked
- Very, very useful for audits


Diagnostic Collection
- You can configure the diagnostic collection feature on servers
- Crash information is sent to a mail-in database!
- Build the fault reports database
- Set as mail-in database
- All .nsd and console.log information will be mailed to the database
- Fault Analyzer in ND7
- Collates and displays information relevant to the crash(es)

Troubleshooting
- You can also configure the diagnostic collection feature on clients!
- Set in the Location document on the client
- Can be forced via policy
- Client crash information mailed to you!
- No need to ask the dreaded end user!

Anti-Virus Software on Domino Servers
- OS platform AV software
- Exclude your TMP directory
- Exclude your data directory
- Exclude your Txn directory
- Exclude your view rebuild directory
- These folders constantly change
- Performance of your server can be hampered by the OS AV software
- Use Domino AV software for the Domino engine
- Alternate your AV products between the platform and Domino engine!

Performance and Transactional Logging
- Transactional Log files should NOT run on the same RAID array as the data drive
- Separate disks
- Local if possible (Raid 1)
- If on a Storage Area Network (SAN), use local drives for the Txn logs/view rebuild directory

Checking Server Connectivity Tool
- JPING
- Trace testing for Domino servers
- www-10.lotus.com/ldd/sandbox.nsf/ecc552f1ab6e46e4852568a90055c4cd/
222294a30361b72888256aa20083873e?OpenDocument&Highlight=0,connect
- Always very useful to test ports and DNS
- Similar to traceroute and ping for Domino!

Performance and Security Settings
- To aid performance, avoid using wildcards (*) in the Server security settings (Server document)

Port Compression
- Enable network port compression!
- This is especially good for server-to-server communication
- Must be enabled on both sides
- Up to 60% compression of data

View Indexes and Performance
- View index rebuild directory
- Directory used by update/updall tasks for rebuilding indexes
- Usually the windows TEMP directory
- Set path — separate array/disk if you can
- View_ReBuild_Dir=f:\views
- Huge performance boost

Policies
- Administrator wants to push down a NOTES.INI setting to all clients
- Or settings for the current location document
- The key here is that it will change the “current location”
- By modifying the desktop settings form, you can add/change any notes.ini or location setting you wish!
- Caution: Requires a developer!
- Full instructions can be found in the Admin help database

Checking Policies on Clients
- Want to check what policies have been applied to the client locally?
- Open the users’ local address book
- Hold CTRL + SHIFT and choose View
Goto from the menu
- Open the $Policies view
- For more information on policies and troubleshooting, go here:
- www.pmooney.net/blogsphe.nsf/d6plinks/PMOY-6M326J#comments

Mail Settings with Policies
- Configure and use Mail policies wisely!
- Don’t restrict all features to be changed by users
- Users don’t appreciate mail preferences being forced on them!
- Example: Letterhead
- Enable the Mail disclaimer feature
- Separate mail disclaimers per policy!
- Different departments could require different disclaimers

• Comments [1]

Copier-collerdepuis d’une vue sous forme de tableau

 

Vous pouvez copier une vue de la base de documents puis la coller de façon à ce qu'elle apparaisse sous forme de tableau dans un document. Lors du collage, une mise en correspondance est établie entre les titres de colonne du tableau et ceux de la vue. Les lignes du tableau accueillent les documents sélectionnés dans la vue qui a été copiée. Notes crée également une nouvelle colonne à gauche qui comporte un lien vers chacun des documents sélectionnés pour la copie.

Une vue avec des documents sélectionnés est représentée ci-dessous :

Lorsque vous copiez-collez cette vue sous forme de tableau, vous obtenez le résultat suivant , bien plus pratique que de simples liens doc qu'il vous faudrait commenter.



1.        Ouvrez la vue de la base de documents à copier.
2.        Sélectionnez les documents à copier dans cette vue.
3.        Choisissez Edition - Copier éléments sélectionnés dans tableau.
4.        Placez le curseur dans le document où vous collez la vue et choisissez Edition - Coller.

• Comments [0]

Nous connaître

 

Ingénierie Informatique - Messagerie et Groupware : IBM Domino - IronPort - Sametime - QuickR
	Créée en 1994, Gemme est dissoule depuis le 15 Mars 2010. Je laisse ses pages pour ceux qui y trouvent encore un intérêt.

Planning de groupe pour Lotus Notes Version d'évalution PRODUIT SANS SUPPORT: - GOP 2005 (V5.0)
	Evaluez GEMME_On-Planning un planning de groupe à partir des agendas Lotus Notes selon vos critères, la restitution se fait sous Excel. Version Anglaise et Francaise. Gemme -on-planning is available in English also. Gemme On planning provide a group calendar for Lotus Notes.Resulting Diary is in Excel's format. Nous Contacter .... GEMME SOFTWARE DEVELOPPEMENT SARL DISSOLUE

Comments Disabled

Modèle Messagerie Notes V8...

 

Beaucoup d'améliorations...
Domino 8.0.1 est sortie et de nouvelles fonctionnalités sont disponibles en 8.0.1:

• Domino Web Access light
• Amélioration interface Utilisateur pour les  " To Do's "
• Intégration de la barre Quickr.
• Gauge Quota Messagerie !!!
• Meilleure compression avec 35% de réduction de l'espace..
• 64 Bit pour  Windows et AIX
• Notes Traveler pour  mobile e-mail, calendar, contacts et to do  sur Windows Mobile  

Et Prise en compte de l'avis des utilisateurs et de ses clients quand il le sollicite  post.

• Répondre sans pièces(s) jointe(s) ... Enfin en 8.0.1 !!! (Merci à Jèrôme de commentaire ...)

• Comments [2]