DominoMigrationProposal

Proposal for Lotus Notes Domino Migrations
Preparedby Lynn Levash
August 28, 2013

Section I - Introduction
The purpose of this proposal is to gather and gain information about both the current Lotus Notes Domino
mail servers, the Notes Traveler server, and the new Domino allocated servers that will be provided for
migration of the Domino infrastructure. I have gathered, processed and tested data to be further provided
in this proposal. One of the questions here that is pegging everyone’s mind is WHY MIGRATE? Well,
while it is true that there is risk involved during any migration, both myself and Robert Faughnan are
Lotus Notes professionals who have participated and ran several Notes migrations. The data will be both
backed up on the current servers and tested for accuracy before the migration takes place. The details of
the servers Windows name, Windows server version, Domino server name,Domino version, Domino.doc
version, IP address and all other relevant information will be verified as well. The obvious answer to the
question WHY MIGRATE is to provide One America with Domino Servers that have accurate
performance for their network. The most important point to realize is that when it comes to performance
issues, there is no single right or wrong answer. All of the various factors must be considered, including
the unique customer environment. What works for one server environment may cause a problem for
another server environment. With that in mind, we can begin this proposal and break down the sections
of course with IBM Best Practices for server performance.
Domino is essentially a FileServer application, reading and writing documents ("notes") to and from disk
storage. Thus Domino's ability to recover documents from disk, and write any changes to those
documents back to disk, in a timely manner, is one of the most key performance factors of a ll. Any
delays to Domino's requests to read and write documents, even relatively minor delays, can have
very severe implications on both Domino's overall performance, as the Notes end user sees it, as
well asimpacting on Domino's ability to provide a stable environment. It is important to note that
technically, Domino doesn't care or know about what type of disk system lies underneath it. Domino
simply relies on the Operating System and Hardware to manage those resources. Domino is just
another application using disk. However, since Domino engages in potentially intensive disk I/O,
when slowness or bottlenecks exist in the disk subsystem, Domino will manifest those
bottlenecks through slow performance. Our goal as Lotus Notes Domino Administrators is to provide
the best performance for the Domino environment and increase performance on these servers,
decreasing slowness, bottlenecks and outages. If Domino performance is traced back to disk problems,
addressing those issues is not within the realm of Domino Support, but rather reverts to whomever
manages the Operating System and Hardware. That is why the new hardware and Operating System
of the new Domino mail servers is so integral. Let’s have a further look through the next pages of the
proposal.

Section II – Current server specifications
When there is an issue with any Domino server having performance issues, one must look at their current
server specifications and ultimately do some testing. The current server specifications are as follows:
Information on the current Domino infrastructure:
Server One:
Domino Server Name: AULNOTES2B/AUL
Windows Server Name: swpmail02
Domino Version: 8.5.3FP2HF249
Windows Server Version: 2003 Standard Edition
R2 Service Pack 2 32 bit
Current IP Address: 161.199.110.46
Server Two:
Domino Server Name: AULNOTES3BAUL
Windows Server Name: swpmail03
Domino Version: 8.5.3FP2HF249
Windows Server Version: 2003 Standard Edition
R2 Service Pack 2 32 bit
Current IP Address: 161.199.110.47
It is STRONGLY recommended as mentioned in other parts of this proposal that Lotus Notes
Domino 8.5.3x is run on 64 bit due to memory issues as well asperformance. Although, this has
been an issue with Legato, that can only run on 32 bit.
There are 2118 .nsf files are the current Notes servers.
Must be enabled – DAOS
The IBM Lotus Domino attachment and object service (DAOS) in release 8.5 reduces the total cost of
ownership and helps customers with green computing practices by storing all file attachments in a
separate repository on the server and retrieving them by reference. In databases that use DAOS, Lotus
Domino no longer saves a separate and complete copy of every document attachment. Instead, the
server saves a reference to each attached file in an internal repository, and it refers to the same file from
multiple documents in one or more databases on the same server. When an attached file is large and a
message containing it is broadcast to thousands of users, creating a separate copy of the message for
each recipient could require several gigabytes of disk space. Multiple copies of the same attachment

often also proliferated in mail threads with multiple replies. With DAOS enabled, disk space usage is
substantially reduced.
Translog enabled
Transaction logging captures all the changes made to a database and writes them to a transaction log.
The logged transactions are then written to disk in a batch, either when resources are available or when
scheduled.
NOTE: Transaction Logging dramatically improves restart times after a Domino crash on all
platforms, improves data integrity, and significantly reduces data loss after a crash.
IBM will also require that you upload these logs to them if IBM support resources are needed.
Both new mail servers must be as a cluster
A Domino cluster is a group of two or more servers that provides users with constant access to data,
balances the workload between servers, improves server performance, and maintains performance when
you increase the size of your enterprise.
Section III – Migration Plan and Process
The process of a Domino migration is a very important one to any network. While there are always risks
involved, the Domino Administrators as well as the Operating Systems and Networking staff will ensure to
use IBM’s Best Practices will migrating to new hardware. It is important that the Networking staff be
advised of these best practices and procedures with the knowledge and experience of the Lotus Notes
Administrators as well for troubleshooting, or roll-back is necessary.
As it has been noted and said that Legato can only run on 32 bit, it is STRONGLY advised that
Domino 8.5.x run on 64 bit for performance issues and for additional memory space. I just wanted
this to be documented as what IBM recommends is best practice.

BEFORE MIGRATING, HERE’S WHATS TO BE CONSIDERED:
Taking the time to do a thorough evaluation of your starting point is time well spent. Capturing
baselines of your existing server infrastructure will allow you to compare how the upgraded environment
is performing.
Evaluate
- Do a thorough investigation of the current state (starting point) and use tools to facilitate data capture
- Server infrastructure (including baseline stats, performance, etc)
- Clients / workstations
- Applications
- 3rd party Products (LEGATO)
- Document pre-existing conditions and problems
- Try to resolve outstanding issues and problems prior to upgrading
- No matter how tenuous the link, an upgrade can be held responsible for any problem whether old or
new
- Document things you want or need to address while you have the opportunity, focus and resources
available
-There is always cleanup that can be done ahead of time
Monitor
Monitoring is a critical part of any upgrade, even a point release upgrade. The goal is to understand your
current cost of running the existing environment and to predict a problem before it happens in the new
environment.
- This is really important when you are moving users and/or consolidating servers
Steps:
- Make sure you are capturing the available raw data from the servers
- Operating system capacity and performance metrics
- CPU, memory (usage, paging), disk (usage, I/O rates, performance), network
- Domino server specific statistics
- Other components (for example, SAN switches and disk metrics)
- Interpret/analyze the data and create your baselines for your current environment
- What are the typical operating parameters for your servers
- What is the data telling you about your environment?
- Execute your monitoring processes using your base lines
- Create your daily/weekly/monthly reports based on your baselines
- Create a remediation process based on outputs that exceed your baselines
One major advantage to running Domino on a 64-bit operating system is the access to additional
addressable memory space, even if running 32-bit Domino.
Are you upgrading from 32-bit Domino to 64-bit Domino?
If so, the following things will happen:
- All existing full text indexes will be discarded and rebuilt
- On Windows, all existing views currently built will be discarded and rebuilt

Because of the two items mentioned above, if the updall process is used during upgrading it will take
much longer to run so you should plan for it. This is a one time occurrence.
Okay, now enough about the pre-migration stuff, here is the task at hand, the migration itself:
How to Move the Domino Server:
1. Shut off replication and mail routing to the server that is being rebuilt or reinstalled.
2. Make a complete backup of the original Domino server. Note that the location of the program
directory can be identified from the line NotesProgram = in the NOTES.INI file.
3. Create the Lotusdomino and Lotusdominodata directories on the new server.
4. Move all the data files from the old machine (the location of the data directory can be identified
from the line Directory= in the NOTES.INI) to the appropriate place on the new server box. Data
files include:
Anything with an .NSF extension
Server's ID file
Administrator's ID file
Certificate ID file
Public Address Book for the server (NAMES.NSF)
Notes.ini
Note: It is also important to copy the Certlog.nsf over because it is used for security purposes and
for user maintenance (to some degree).
5. Move all the mail files of all the Notes mail users. By default, these are kept in the NotesDataMail
directory. Additionally, move all other databases that were created on the original Domino server.
6. Install the Domino server software on the new server box.
Be sure to use LotusDomino and LotusDominoData as the install directories on a Windows OS.
(If you are upgrading the server at the same time as moving it from one machine to another, you
would install the new server software)
7. Disconnect the new machine from the network.
8. Launch the new server to ensure that it was installed correctly and that it is properly configured.
The configuration Notes client should not launch at this time. Because the notes.ini from the
previous installation was used, the server should have the same configuration as it did on the
original Host Server.
When setting up the Domino server software, use the original server ID, admin ID, and Cert.ID
files. Remember to use the exact same Domino server name and Domain names.
When the initial Domino installation begins it may state that the Windows Registry needs to
modify some settings that are still present from the previous installation. Click “Yes” to correct
this.
9. Shut down the server.


10. When the new server has all its files, the old Domino server must be shut down before bringing up the
new Domino server with the same name. Take the old server down, put the old server's IP address on the
new server, connect the new server to the network, and restart the new server for the change to take
effect.
11. Bring up the Domino server on the new machine.
Note: The following steps should be considered a best practice to recover from a Domino server
upgrade failure or a complete reinstallation of a Domino server. These steps only relate to the
components installed by the Domino server installer. Data stored in the data directory structure
should be protected. Additionally, if there are logs that are stored in the binaries directory or if
any other products are installed and reference files in this directory, appropriate actions should
be taken to back these files up.
If you are reinstalling a Domino server, run a full installation of the Domino server and point the
install to the previously installed Domino directory on the physical server. This will not overwrite
existing system files; therefore, you do not need to perform an initial server setup because the
install files will pick up all relevant information from the existing NOTES.INI file. The Domino
Directory is not overwritten; therefore, when the server is started again, it will continue as if
nothing has changed. Server startup will continue and all previous settings will be intact.
Additional Considerations
 If the Network Configuration changes, be sure to update the Server document. If the Net
Address field on the Server document contains a server IP address, update this field if a
new computer with a different IP address is installed.
 Check for Directory Links when performing an upgrade/move.
 Check for any OS level junctions or symbolic links that are defined. Ensure new symbolic links
are created on the new server or the files for those links become part of the data directory.
 If the server name is changed, ensure that all encrypted databases are decrypted before
copying the files to the new server.
 When moving servers between different operating system platforms, use FTP to relocate
the databases or mail files to ensure the codepages are not corrupted. In some
configurations, OS copy has caused database corruption.
 If you are moving a server from one machine to another and the drive mapping changes,
for example, from drive C to drive D, change the following parameters in the file
NOTES.INI:
o Directory=d:=LotusDominoData
o NotesProgram=d:LotusDomino
 Perform a search in the server's NOTES.INI file to ensure that these parameters are changed
appropriately. Perform a "find" (CTRL + F) on the old drive references and make changes as
appropriate.
Note If you change the server's name when you move it to the new computer, you can
notify users to make the appropriate change to their Location documents, or you can
make that change for them.
Note: It is not recommended that you EVER upgrade the hardware and Domino at the same time.
You should upgrade the hardware before or after the Domino upgrade, but not at the same time
unless you have no other choice. Upgrading them separately makes it much easier to
troubleshoot when problems arise, isolating the issue to the hardware upgrade versus the
Domino upgrade.

The server identity remains the same, but will be moved to a new machine:
- Bring down the current server
- Move all data to the new hardware to the same position (same file locations and directory structure) as
the old hardware.
- Domino program directory
- Domino data directory
- Domino transactional logs
- Domino DAOS files (only if upgrading from 8.5 to 8.5.1)
- Rerun install of the current version of the Domino server and point to all of the same file locations to
mirror your previous configurations
- Once you start the copy of data to the new hardware, you should never bring up the server on
the old machine
- Before bringing up the server for the first time, switch the server host and network identities to that of the
old server
- Run this configuration for a few days to make sure everything runs correctly. If so, then you can safely
upgrade this Domino server
Option 3 - Install New Domino servers (Inherit Identities)
- Build new server independently
- Create a new temporary server identity
- Permits change of underlying hardware and operating system
- Permits testing of the configured state before cut-over
- Create replicas on temporary server and keep in synch with server to be replaced via replication
- At desired time, switch server host, network and Domino server identities
- Change is transparent to clients
- If clustered...
-repeat process for each server
-do not add temporary Domino server into cluster
Option 4 - Install New Domino server (New Identity)
- Build a new server independently
- Create a new server identity
- Permits change of underlying hardware and operating system
- Permits testing of the configured state before cut-over
- For mail users, requires some migration of users and client configurations from existing to new server
- Permits monitoring as you ramp up users to verify that you don't overload the "new" server
- For applications, requires migration of applications to new server and redirection from old server
- If clustered...
- create new servers and new cluster
- migrate users and client configurations to distribute users across the members
- migrate applications to the new cluster

Section IV. IBM Lotus Domino Best Practices
Let’s discuss a bit about IBM’s best practices and some of their current testing to see their results to gain
a better understanding how Notes can be tested in the current environment and IBM’s findings as well.
Many companies have found that their employees Lotus Notes mail files continue to grow, and are
looking for advice in controlling the performance costs associated with these larger mail files. As a result,
IBM conducted studies of the characteristics of large and active mail files. IBM also looked at the
impact related to frequency of searching, full-text indexing, and whether mail documents are filed
or kept in the Inbox.
Several recommendations mentioned below resulted in CPU improvements of over 30 percent when
implemented in IBM’s test environment. Bear in mind, however, that these tests were based on simulated
user workloads. You may see different results in your own environment. This testing information focuses
on mail databases, but it also applies to other databases as well. IBM’s benchmark testing was performed
on various iSeries servers, but most of the findings can be applied to other platforms as well.
IBM used multiple iSeries server models for the tests described below. These servers included 830-2349
(8-way 540 MHz), 840-2461 (8 processors enabled), 840-2461 (24 processors enabled), and i5 POWER5
520 (two-way) and 550 (four-way) models. IBM also tested various Domino versions. The
recommendations included at the end of this article apply to all of these Domino releases.
Load was generated by up to 16 PC clients running Server.Load. This free tool is included with the
Domino Administrator client. They also used the NotesBench tool for some of the testing. The workload
we selected was the built-in R6 Mail Routing script. This script is based on usage patterns of mail users
from many Domino customers. Each PC simulated 500 to 1000 users. Server.Load reported average
response times experienced by the simulated users. In all cases, load on the server was such that
response times never exceeded one second, and were generally much less (the heaviest user test with 2
GB mail files and everything in the Inbox had response times of 750 msec; the lightest users had 11 msec
response times).

For most tests, one new user started every second in groups of 1000. It took 17 minutes for all 1000
users to log on. We then took a 13 minute "break" before starting the next group of 1000. Actual usage
patterns (for instance, Monday morning spikes) may be even more aggressive. After the ramp-up period,
each workload was maintained at "steady state" for at least two hours.
Before each run, all new copies of the mail files were created in order to minimize run variability. For most
of the tests, mail files were populated with documents that were all 25 KB in size. This was based on
studying IBM internal users, as well as a variety of customers. In comparison, databases of the same size
with fewer large documents required much less CPU (more on this later in this article).
We created mail files of different sizes using Server.Load and the built-in NRPC Mail Initialization
workload. As mentioned, most of the testing was done with mail files built of documents of 25 KB, varying
the number of documents from 100 to 50,000, as described later in this article. Some tests used mail files
of all the same size, such as 700 MB, but were built with varying number of documents in the Inbox.
Other tests compared various sizes of mail files, such as 400 MB versus 1 GB, while keeping the number
of documents included in the mail file constant.
System performance data was monitored using iSeries Performance Tools (5722PT1), which monitors
utilization for system resources including CPU, disk, memory, and network.
Test Results from IBM test procedures above:
Based on this test, IBM concluded that large mail files require more memory, especially when starting
user sessions and during failover. Reducing mail file size improves performance of view indexing,
compact, backup and restore, and transaction logging. To measure this effect, IBM tested various
mail file sizes ranging from 15 MB up to 2 GB. They did not observe a sharp increase in steady-state CPU
as file sizes got larger, at least up to 2 GB mail files. The peak CPU seen during ramp-up increased at a
faster rate than steady-state CPU, but again they saw no sharp increase in the curve. Ramp-up simulates
when many users sign on during a short time period, for example on a Monday morning or during a
failover. In figure 1, for example, increasing average mail file size from 500 MB to 1000 MB resulted in the
CPU increasing by 12 percent at steady state, but was 55 percent higher during ramp-up. These tests
were run with all documents in the Inbox.
IBM found during their testing, that keeping the number of documents in the Inbox to a maximum
of 1000 reduced peak CPU usage significantly for both pairs of groups (50 percent compared to 72
percent for 400 MB mail files, and 62 percent compared to 75 percent for 1000 MB mail files). This
performance benefit from reduced Inbox size was even greater for peak CPU than steady-state CPU.
Here’s what IBM says about the mail files for each user:
Keeping the Inbox at 1000 or fewer documents resulted in dramatically faster response times to
end users -- 23 msec compared to 37 msec for 400 MB mail files, and 24 msec compared to 40 msec for
1000 MB mail files.
From these tests, we found that reducing the number of documents in the Inbox improves response time
to users, and reduces resources needed on the server (CPU, memory, disk I/O, and time to start or
failover a server). The effect is most dramatic at "first touch." Reducing the Inbox by 75 percent
virtually eliminated the ramp-up spike. Peak CPU dropped 50 percent, while steady-state CPU
improved 12 to 30 percent. Average response times for a 400 MB mail file were more than two times
better when the Inbox waskept at 1000 documents or less.
IBM also found that mail files of the same size can use significantly different resources, depending on the
average size and number of documents. In their test, the group with fewer documents in their mail
files consumed considerably less CPU resources than the group with 28,000 mail documents.
This test indicates that the number of documents in a mail file, and especially the number of
documents in the Inbox, has greater impact on performance than the file size itself. Of course,
these two variables are typically related in practice. Nonetheless, for a given mail file size, they observed
that users with many small documents use more resources than those with fewer large documents.

Based on IBM’s test results, they offer several recommendations for improved Domino
performance. Their tests show that reducing your Inbox size (filing documents into a folder within
the same mail file) improves response times to the end users, steady-state CPU on the server, and
especially peak CPU. Peak CPU in this case is associated with users opening their mail for the first time
(following session timeout). So you should advise your users to file documents from their Inbox to other
folders, to keep it as small as possible (preferably under 1000 documents). This will result in better
response times, as well as improved resource utilization. You can also write an agent to automatically
"trim" Inboxes. The agent can be set up to run periodically outside of business hours, such as on
the weekend.
Agent code details:
' CleanupInbox – moves older documents out of inbox
Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase
Set db = s.CurrentDatabase
Dim dr1 As notesdaterange
Dim v As notesview
Dim dc1 As NotesDocumentCollection
Dim gracedoc As NotesDocument
Dim stime1 As New NotesDateTime("0/0/0")
Dim etime1 As New NotesDateTime("Today")
Set gracedoc = db.GetProfileDocument("inboxgracedays")
Dim graceval As Variant
Dim gracedays As Integer
' if no profile doc has been prepared, default is 90 days
If gracedoc.HasItem("gracedays") Then
graceval = gracedoc.GetItemValue("gracedays")
gracedays = Cint(graceval(0))
Else
gracedays = 90
End If
etime1.AdjustDay(-1*gracedays)
' create a daterange excluding docs newer than graceperiod
Set dr1 = s.CreateDateRange()
Set dr1.StartDateTime = stime1
Set dr1.EndDateTime = etime1
'dc1: collection of 'old' documents from inbox
(before or on Today - gracedays)
Set v = db.GetView("($Inbox)")
Set dc1 = v.GetAllDocumentsByKey(dr1)
'pull out expired docs
dc1.RemoveAllFromFolder("($Inbox)")
End Sub
'SetInboxGracePeriod agent – sets the grace period for inbox
Sub Initialize
Dim s As New NotesSession
Dim db As NotesDatabase

Set db = s.CurrentDatabase
Dim gracedoc As NotesDocument
Dim gracedays As Integer
Dim inputgracedays As Integer
Dim maxdays As Integer
Dim graceval As Variant
Dim gracevar As Variant
maxdays = 1000
If gracedoc.HasItem("gracedays") Then
graceval = gracedoc.GetItemValue("gracedays")
gracedays = Cint(graceval(0))
Else
gracedays = 90
End If
getInput:
inputgracedays = -1
gracevar = Inputbox("Days to retain in Inbox? (currently " &
gracedays & ")" )
If (gracevar <> "") Then
inputgracedays = Cint(gracevar)
End If
While (inputgracedays > maxdays)
Msgbox("Maximum of " & maxdays
& " days exceeded")
Goto getInput
Wend
If inputgracedays <> -1 Then
gracedays = inputgracedays
End If
gracedoc.ReplaceItemValue "gracedays",gracedays
Call gracedoc.Save(False,False)
End Sub
Here are some important ways recommended by IBM for Mail Users –
 Archiving. Notes and Domino include client-based and server-based archiving capabilities.
Archiving can be set up to run automatically or manually; Notes and Domino handle the rest.
Older documents will be moved to the archive database, so important information will not be lost.
Check with your administrators to see if other archiving solutions are available. For OA this is
done by Legato.
 Client currency. Upgrading to the latest available version of Notes supported by your Domino
server will generally give improved performance. Often, performance improvements are made
in the newer Domino releases, which can only be fully leveraged by accompanying
changes in the client code.
 Use the right tools. Consider whether or not other document management solutions (such as
QuickPlace or Domino Document Manager) might help minimize multiple copies of the same
information, and facilitate access to the information to a wider audience.

Here’s a section from IBM regarding ways that Domino Administrators can ultimately help performance as
well. These are best practices as defined by IBM and should be considered as well.
 Mail file quotas. You can control mail file size by setting quotas on databases. A quota is the
largest size you will allow a database to grow. You can establish different quotas for different
categories of users. For example, researchers might require larger quotas than sales staff. It is
very easy to set database quotas from the Domino Administration client (choose Tools â€“
Database â€“ Quotas). You will need to establish a regular compact schedule to achieve the
benefit from quotas and other database management techniques.
 Memory tuning. Large mail files use more memory. Memory bottlenecks can cause increased
CPU, disk I/O, and slower response times. For our testing on iSeries, we were able to
dramatically improve Domino response times by making sure the machine pool was large enough
to keep page faulting under five faults per second. This is especially significant, since the default
threshold for OS/400 auto performance adjuster is 10 faults per second in the machine pool.
Reducing the memory faulting in the Base pool also has a significant benefit. Use other memory
tuning mechanisms as applicable to your operating systems.
 Domino server currency. Keep current with Domino releases, as performance
improvements are generally included with each release. You should also consider the extent
to which new features will be used and allow for any additional overhead associated with them.
 Client currency. As mentioned previously, keeping users current with Notes client versions can
result in significant performance benefits. IBM Lotus Notes Smart Upgrade makes this easy to
administer.
 Full-text indexes. Create full-text indexes on databases that are searched regularly. Maintaining
an index is almost always much less expensive than creating an index “on the fly" which also can
be done.
 Users per server. On iSeries servers, it is common practice to run multiple Domino partitions
(DPARS) within a single instance of the operating system or Logical Partition (LPAR). Generally,
the number of users on a given server is determined by the backup strategy and other
administrative factors, such as physical location of the users, storage requirements, time to
complete maintenance tasks, and failure tolerance. In terms of performance and utilization of
resources, it is usually better to consolidate onto as few DPARS as possible.
 Archiving. Administrators can archive databases by running the compact task with the archiving
option. There are a number of products available that provide advanced archiving features for
your Notes/Domino data. In OA case, is it Legato.
 End-to-end monitoring. Effective monitoring of your Domino environment should include
not only statistics of individual systems and Domino servers, but also performance of
networking components and storage subsystems (for example, SAN components if
applicable).
So, now you are probably wondering more about IBM’s specific Best Practices for an 8.5.3
environment for 25 GB of RAM and 16 cores, along with an Operating System of Windows 2003 32
Bit. Let’s talk!
Here are the hardware requirementsas found on IBM’s website:
Group Applicable OS Applicable
Component
Notes
Disk Space All Applicable Standard Install directory (C:) - 900 MB or

Component
Notes
Windows OS configuration, Basic
configuration
more recommended
Display All Applicable
Windows OS
Standard
configuration, Basic
configuration
Monitor: 1024 x 768 screen
resolution minimum
Hardware support for OpenGL
Memory Windows XP
Professional with
FDCC x86-32,
Windows XP SP2
Professional x86-32,
Windows XP Tablet
PC Edition x86-32
Standard
configuration
Windows XP - 512 MB minimum; 1
GB or more strongly recommended
Windows 7
Enterprise with FDCC
x86-32,
Windows 7
Enterprise x86-32,
Windows 7
Enterprise x86-64,
Windows 7
Windows 7
Windows 7 Ultimate
x86-32,
Windows 7 Ultimate
x86-64,
Windows Vista
Business x86-32,
Windows Vista
Enterprise with FDCC
x86-32,
Windows Vista
Enterprise x86-32,
Windows Vista for
Tablet PC x86-32,
Windows Vista
Ultimate x86-32
Standard
configuration
Windows Vista, Windows 7 - 1 GB
minimum; 1.5 GB or more strongly
recommended
All Applicable
Windows OS
Basic configuration 256 MB minimum; 512 MB or
more strongly recommended
Network
Protocols
All Applicable
Windows OS
Standard
configuration
TCP/IP (includes IPv6)
NetBIOS over IP (only Microsoft
TCP/IP is supported)
NetBIOS over IPX (Both Novell
NetBIOS and Microsoft NetBIOS
over IPX are supported.)
NetBIOS support is off by default.

Component
Notes
See separate tech note for more
information.
Processor All Applicable
Windows OS
Standard
configuration
Intel Pentium 4, 1.2 GHz or higher
and compatibles, or equivalents
Notes/Domino performance is an extremely sophisticated topic. For IBM’s purposes, "performance
tuning" is defined as the process of tuning an existing environment to obtain optimal response,
improved efficiency, or to address specific issues. Many aspects of hardware and software affect
performance, not the least of which includes the complexity of application design. For many
individuals, the classic resources come to mind when considering performance, such as CPU,
Memory, and Disk I/O.
However, other lesser known resources are just as critically involved, including the process virtual
address space, threading, semaphores, socket connections, and so forth. High level application
configurations such as database design, user load, and scheduled activities can have a
tremendous affect on both OS and application resources.
Sizing: It is crucial to realize that "sizing" is about trying to determine what is enough hardware to
handle your “worst case” peak time. It is important that you are clear about what that peak time
really is. You should understand the weekly or seasonal trends in your business, which is really part of
capacity planning (watching trends over time), but this does feed into sizing. If you cluster, then you
should consider cluster failover.
In one internal IBM system it was measured that average peak processor usage per day in August was
20% less than the peaks in February; the probable cause, August is the prime time for family vacations,
so fewer people are working. Not only were processor peaks down, but also number of messages,
concurrent users, or almost any measurement. Only by monitoring your Domino environment over a
year or two will you really know your sizing needs (again, this ties in with capacity planning). The
key here is to understand that if you look at your system on just one day or one week, and presume all
weeks are the same, or that you have established your peak, you may miss your mark by a significant
distance if you use that information to size your new servers.
Architecture can play a big part. You may require separate machines, have security requirements,
need clustering and even separation of machines to achieve desired availability and disaster
recovery needs. You may need a distributed implementation or a single site, or some combination of
consolidation yet separation. It is important to understand that implementing a solid architecture should
involve a broader view of the overall customer site, Domino, related products and interactions, network,
and so on.
You need to have a solid architecture before starting the process of sizing. While you may not know the
“size” of specific boxes or absolute number of machines, you should know how many specific, distinct
“boxes” you want with different functions. After sizing, you may yet grow in a horizontal mode by
having multiple machines that are needed for a logical “box” in an architecture, or you could have a large

machine with multiple LPARs (logical partitions), each with multiple DPARs (Domino partitions), that end
up representing a “box” in an architecture diagram.
Growth Trends:
If your capacity planning suggests that you do have growth trends, it will be important to reflect
this in your sizing. You may consider sizing for the first year or two of growth, and be sure you
understand how you will grow beyond that time. Understand that growth is not just in number of
users. It may be in mail file size, which can impact both disk and processor. It may be users
moving from light to medium or heavy use where they send and receive more mail, becoming ever
more dependent on mail in their job, putting more demands on your mail servers. Growth may
also include the implementation of new functions. There are a vast number of optional functions
in Domino and you may find need over time to implement things not done in the past. It is also
possible that you add new functions that sit on top of Domino, or access Domino remotely, for
instance Fax/Mail, or PDA devices like Blackberry. While typical “benchmarks” never reflect your real
world users, they can be an effective tool for comparing how many benchmark users different machines
can handle.
All sizing tools and methodologies are based around some concept of the “typical user”; in the
real world there is no such thing as a “typical user”. Your company will be unique. Different groups in
your company will have different ‘profiles’ of how they use Domino. That sizing, whether you do it yourself
or get someone to assist you, will have some significant margin of error. As a result, you should not be
too aggressive about sizing unless you understand your environment and your users, and the potential for
changes to a very detailed level. It is often worthwhile to perform sizing, then compare this to the
resources you are using today. If the ‘total resources’ from your sizing vary greatly (high or low) from what
you have today, you need to investigate and determine why.
Another area to be careful about when sizing is when your current system is giving you problems.
Consider two aspects.
First, if you have “response time problems”, understand if it is really caused by the limits of your current
system, for instance exhausting the processor. Understand that there are other possible culprits.
Could you have memory problems (paging, swapping)? Do you have I/O bottlenecks (waiting on
disk I/O)? Have you completely drilled down on all aspects of your current performance issue to
understand the underlying cause of the problem? Or are you just looking at a symptom that may
be several steps removed from the real problem? There are many things that can influence
response times, such as the network or the workstation itself, especially when the workstation
tries to perform certain functions with very large mail files.
Second, understand that if you do have a system that is “constrained” by lack of resources, you most
likely have significant ‘pent up demand’ from your users. They may react to this by trying to move their
usage to ‘off times’ when performance is better, or they may just use ‘less mail’ than they would like. If
you do not take this pent up demand into account as you size you may find that your users will
take advantage of the new hardware, go back to using Domino as much as they want, at the times
that they want, and your new machine that you thought had sufficient ‘growth room’ is suddenly
‘consumed’ as soon as you roll it out.

Section V - Customizations to the current Notes environment
The current customizations that I have been made aware of are:
(Please see Notes.ini files section)

Section VI - Notes.ini files
Here are a copy of the current Notes.ini files from the existing mail servers.
Let’s analyze them! The threads are grouped by how they used.
Server One:
[Notes]
;CorePart
;--------------------------------------------------------------------------
CertificateExpChecked=aulnotes3.id 10/21/2009
Directory=d:notesdata
KitType=2
NotesProgram=d:notes
;Server Configuration

;--------------------------------------------------------------------------
AdminP_last_saved_directory_time=07/06/2013 04:15:28 PM
AdminP_last_saved_policy_time=07/05/2013 08:10:13 AM
AdminP_last_saved_user_time=07/05/2013 05:34:05 PM
CONSOLE_AULNotes3/AUL=115 300 7 149 40 1097 647
Console_Log_Max_KBytes=102400
Create_R85_Databases=1
DAOS_Encrypt_NLO=0
DDMSetup=850200
ExistingServerName=CN=aulhub1/O=aul
FormulaTimeout=120
Last_Domino_Time=00512E2285257BA2
NLCache_Size=67108864
NSF_Buffer_Pool_Size_MB=
;^ this value is empty, you should remove it.
NSF_DbCache_MaxEntries=6000
NSF_Quota_Method=2
Process_Monitor_Disabled=1
PartitionNumber=1
Schedule_db_boss=1
Schedule_No_CalcStats=1
Schedule_No_Validate=1
Server_Cluster_Probe_Port=Cluster
Server_Name_Lookup_No_Update=1
Server_Session_Timeout=30
Server_Show_Performance=1
Shared_Mail=0
ServerController=0
ServerName=AULNotes3/AUL
ServerNameNative=042F042F41554C4E6F746573332F41554C
ServerTasks=Replica,Router,Update,AMgr,Adminp,Sched,CalConn,RnRMgr,ExNotesShortcutCache,ExP
rocBadDocs,IMAP,HTTP
ServiceName=Lotus Domino Server (dnotesdata)
TransLog_MaxSize=118000
FTG_Use_Sys_Memory=1
Replicators=2
Server_Pool_Tasks=80
Server_Transinfo_Range=6
;Security
;--------------------------------------------------------------------------
Admin=N administrators DB
KeyFilename=d:notesdataaulnotes3.id
ServerKeyFileName=aulnotes3.id
;Communication Ports
;------------------------------------------------------------- -------------

$$HasLANPort=1
DisabledPorts=LAN0tcpip,LAN3tcpip,LAN1,LAN2,LAN4,LAN5,LAN6,LAN7,LAN8
LAN0tcpip=NETBIOS, 0, 15, 0
LAN1=NETBIOS, 1, 15, 0
Ports=TCPIP1,Cluster
TCPIP1=TCP,0,15,0,,12288,
TCPIP1_TCPIPAddress=0,161.199.30.44,0
cluster=TCP,0,15,0,,12288,
;Router
;--------------------------------------------------------------------------
Domain=AUL
JrnlEnbld=0
MTEnabled=0
MinNewMailPoll=15
RouterDbCacheSize=6100
SMTPNotesPort=TCPIP1
;Calendaring and Scheduling
;--------------------------------------------------------------------------
NavWeekStart=1
Schedule_Version=4
Schedule_Version_Minor=10
ViewWeekStart=2
WeekStart=1
;Setup and Configuration
;--------------------------------------------------------------------------
$CreateBookmarkLastFolder=Favorite Bookmarks
AltNameLanguage=en
BCASE_SITEMAP_DISPLAY=13
Catalog_Updated_by_Build=510
CFP_Lp_Base_Version=Release 8.5.2FP4|November 17, 2011
CFP_Lp_Current=Release 8.5.2FP4 HF60|March 21, 2012
CFP_Lp_Prev=Release 8.5.2FP4|November 17, 2011
CleanSetup=1
ContentLanguage=en-US
DDETimeout=10
DeskWindowSize=31 75 1249 636
DatePickerDirection=0

DefaultMailTemplate=oamail851.ntf
ECLSetup=3
ExtMgr_AddIns=ExNotesShortcutExt,ExNotesJournal
EnablePlugins=1
ExitNotesPrompt=0
FileDlgDirectory=C:Documents and Settingst1notesMy Documents
FontIncrease=0
InstallType=4
Location=Home (Modem),A0E,1FA8
Maximized=1
MailServer=CN=AULNotes3/O=AUL
MailType=0
MenusAdvanced=1
NamedStyle0=0300426173696300000000000000000000000000000000000000000000000000000000000000010
10100000A0000000000000100A0050A0000006400A0050A00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000009404000000000000
NamedStyle0_Face=Default Sans Serif
NamedStyle1=030042756C6C6574000000000000000000000000000000000000000000000000000000000000010
10100000A000000000000000008070A000000640008070A00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000049404000000000000
NamedStyle2=0300486561646C696E6500000000000000000000000000000000000000000000000000000000010
101010B0C0000000000000100A0050A0000006400A0050A00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000009404000000000000
NeedDPABfixup=0
Preferences=32
Region=en-US
Spell_Lang=1033
Spell_Preferences=0
SUT_NEXT_UPDATE=10/22/2009 03:59:46 PM
SU_File_Cleanup=C:Documents and Settingst1notesApplication Datasmkits
SU_In_Progress=0
Su_Next_Update=10/22/2009 03:59:46 PM
ServerRestarted=0
ServerSetup=850200
Setup=850200
TemplateSetup=850200
Win32InfoboxPos=32 110
WindowSizeBookmark=453 134 374 302
WindowSizeBrowse=381 134 518 318
WindowSizeNewDatabase=445 134 389 427
XLate_CSID=52
;SMTP Configuration
;--------------------------------------------------------------------------
TNEFEnableConversion=1

;Time and Date Settings
;--------------------------------------------------------------------------
DST=1
DSTlaw=3,2,1,11,1,1
TimeZone=5
;Agent Manager
;--------------------------------------------------------------------------
ATCLastRunDate=07/08/2013 03:15:54 AM
;Clustering
;--------------------------------------------------------------------------
Cluster_Replicators=5
Server_Availability_Threshold=10
Server_Cluster_Default_Port=Cluster
Server_Cluster_On=1
MailClusterFailover=1
;Logging
;--------------------------------------------------------------------------
Console_Loglevel=2
Log_MailRouting=30
Log_Replication=0
Log_Sessions=0
Log_Tasks=1
Log_Update=0
Log=log.nsf, 1, 0, 7, 40000
Passthru_LogLevel=0
PhoneLog=2
Console_Log_Enabled=1
Log_AgentManager=0
Log_View_Events=0
;Fault Recovery
;--------------------------------------------------------------------------
Crash_LogFile_KB=10240
Crash_MSGSize_MB=20
Crash_NSDSize_MB=10
Crash_Remove_Data=0
File_Retention_Days=365
FaultRecovery=1
FaultRecovery_Build=Release 8.5.2FP4 HF60
;Transaction Logging
;--------------------------------------------------------------------------
Previous_TransLog_Path=T:NotesTransLog

Previous_TransLog_Status=1
Previous_TransLog_Style=2
TransLog_AutoFixup=1
TransLog_Path=T:NotesTransLog
TransLog_Performance=1
TransLog_Status=1
TransLog_Style=2
TransLog_UseAll=0
;Indexing
;--------------------------------------------------------------------------
FT_Binary_Filter_Off=1
Updaters=1
View_ReBuild_Dir=D:NotesDataTemp
;Statistics and Events Configuration
;--------------------------------------------------------------------------
Cleanup_events4_DDMConfig_view=0
Cleanup_events4_DDMFilters_view=0
Cleanup_events4_messages_view=0
Cleanup_events4_methods_view=0
Cleanup_events4_on_first_night=0
Cleanup_events4_stats_view=0
EventSetup=850200
Event_Pool_Size=10485760
;HTTP Configuration
;--------------------------------------------------------------------------
DominoConfigLevel=1
HTTPDisableUrlCache=1
HTTPJVMMaxHeapSize=64M
HTTPJVMMaxHeapSizeSet=1
WebAdminSetup=850
iNotes_WA_ChromeBrowserBlock=0
iNotes_WA_DisableFirefoxAwareness=0
iNotes_WA_EnableEditModeLink=1
;Directory Catalog
;--------------------------------------------------------------------------
NameLookup_Trust_DirCat=0
;LDAP Configuration
;--------------------------------------------------------------------------
DisableLDAPOnAdmin=0
;ID Vault
;--------------------------------------------------------------------------

IDVault_Count1=0
IDVault_Stamp1=10/22/2009 06:03:56 AM
KeyFileName_Owner=CN=AULNotes3/O=AUL
ServerKeyFileName_Owner=CN=AULNotes3/O=AUL
;DAOS
;--------------------------------------------------------------------------
DAOSBasePath=F:DAOS
DAOSCatalogState=1
DAOSDeferredDeleteInterval=15
DAOSEnable=1
DAOSMinObjSize=65536
DAOS_Load=1
;DB2
;--------------------------------------------------------------- -----------
DB2QueryViewRowLimit=500
DB2_DBS_Per_Schema=10
DB2_PW_EXP_Alarm_Days_Prior=15
DB_Creation_Default_Type=NSF
;Debug
;--------------------------------------------------------------------------
DAOSEST_BUCKETS=64,128,256,512,1024,2048,3072,4096,8192,16384
Debug_Capture_TimeOut=1
Debug_enable_update_fix=8191
Debug_ThreadID=1
;
;--------------------------------------------------------------------------
Cluster_TCPIPAddress=0,192.168.14.3,0
IMAPDebug=1
;Double
;--------------------------------------------------------------------------
;SERVER_SHOW_PERFORMANCE=1
;Other
;--------------------------------------------------------------------------
## FT_FLY_INDEX_OFF=1 ##
EmailXtenderBadDocsInt=60
EmailXtenderShortcutCacheInt=15
EmailXtenderShortcutDb=ExShortcut.nsf
EmailXtenderShortcutExclude=adminp,compact,update,updall,nadminp,ncompact,nupdate,nupdall
EmailXtenderTempPath=d:Temp
EmailXtenderUserName=Legato nSysAdmin/AUL
Ex_Shortcut_Compact_Dbs=1

Notes_wa_GZIP_Disable=1
imapdebugio=1
Server Two:
Notes]
;CorePart
;--------------------------------------------------------------------------
CertificateExpChecked=aulnotes2.id 06/17/2010
Directory=d:notesdata
KitType=2
NotesProgram=d:notes
;Server Configuration
;--------------------------------------------------------------------------
AdminP_last_saved_directory_time=07/06/2013 05:53:13 PM
AdminP_last_saved_policy_time=07/04/2013 11:23:24 PM
AdminP_last_saved_user_time=07/05/2013 05:33:30 PM
Cleanup_DDM_Numb_and_Par=0
CONSOLE_AULNotes2/AUL=110 300 7 128 25 1036 728
Console_Log_Max_KBytes=100000
Create_R85_Databases=1
DAOS_Encrypt_NLO=0
DDMSetup=850200
ExistingServerName=CN=AULNotes1/O=AUL
FormulaTimeout=120
Last_Domino_Time=005141CD85257BA2
NLCache_Size=67108864
NLCache_Version=4
NSF_Buffer_Pool_Size_MB=250
NSF_DbCache_MaxEntries=6000
NSF_Quota_Method=2
Process_Monitor_Disabled=1
PartitionNumber=1
Schedule_db_boss=1
Schedule_No_CalcStats=1
Schedule_No_Validate=1
Server_Show_Performance=1
Shared_Mail=0
ServerController=0
ServerName=AULNotes2/AUL
ServerNameNative=042E042E41554C4E6F746573322F41554C
ServerTasks=Replica,Router,Update,AMgr,Adminp,Sched,CalConn,RnRMgr,ExProcBadDocs,ExNotesSho
rtcutCache,HTTP
Server_Cluster_Probe_Port=Cluster
Server_Name_Lookup_No_Update=1

ServiceName=Lotus Domino Server (DNotesdata)
Show_Server_Performance=1
TransLog_MaxSize=118000
FTG_Use_Sys_Memory=1
Server_Pool_Tasks=80
Server_Session_Timeout=30
Server_Transinfo_Range=6
;Security
;--------------------------------------------------------------------------
Admin=N Administrators DB
KeyFilename=aulnotes2.id
ServerKeyFileName=aulnotes2.id
;Communication Ports
;--------------------------------------------------------------------------
$$HasLANPort=1
Cluster=TCP,0,15,0,,12288,
DisabledPorts=LAN0tcpip,LAN3tcpip,LAN1,LAN2,LAN4,LAN5,LAN6,LAN7,LAN8
PortOrder=Cluster,TCPIP1
Ports=Cluster,TCPIP1
TCPIP1=TCP,0,15,0,,12288,
TCPIP1_TCPIPAddress=0,161.199.30.100,0
;Router
;--------------------------------------------------------------------------
Domain=AUL
JrnlEnbld=0
MTEnabled=0
MinNewMailPoll=15
RouterDbCacheSize=6100
SMTPNotesPort=TCPIP1
;Calendaring and Scheduling
;--------------------------------------------------------------------------
AltCalendar=0
NavWeekStart=1
Schedule_Version=4

Schedule_Version_Minor=10
ViewWeekStart=2
WeekStart=1
;Setup and Configuration
;--------------------------------------------------------------------------
$CreateBookmarkLastFolder=Favorite Bookmarks
$DialogMode=0
$HeadlineDisableHeadlines=0
AltNameLanguage=en
AutoLogoffMinutes=0
BrowSersize=189
BackgroundPrinting=1
BookmarkDesignReplaced=0
Catalog_Updated_by_Build=510
CFP_Lp_Base_Version=Release 8.5.2FP4|November 17, 2011
CFP_Lp_Current=Release 8.5.2FP4 HF60|March 21, 2012
CFP_Lp_Prev=Release 8.5.2FP4|November 17, 2011
CalendarTimeSlotDuration=60
CalendarTimeSlotEnd=1140
CalendarTimeSlotStart=420
CleanSetup=1
CompanyName=OneAmerica
ContentLanguage=en-US
DDETimeout=10
Design_alias_width=100
Design_bytes_width=52
Design_comment_width=253
Design_lastmod_width=134
Design_modby_width=144
Design_name_width=133
DeskWindowSize=31 75 945 571
DatePickerDirection=0
DefaultMailTemplate=oamail851.ntf
DisableImageDithering=1
DontCheckDefaultMail=1
ECLSetup=3
ExtMgr_AddIns=ExNotesJournal,ExNotesShortcutExt
EmptyTrash=0
EnableActiveXinBrowser=1
EnableJavaApplets=0
EnableJavaScript=1
EnableJavaScriptErrorDialogs=1
EnableLiveConnect=1
EnablePlugins=1
ExitNotesPrompt=1
FileDlgDirectory=C:Documents and SettingsDefault UserMy Documents

FontIncrease=0
InstallType=4
Location=,22EE,CN=AULNotes2/O=AUL
Maximized=0
MIMEMultilingualMode=1
MIMEPromptMultilingual=1
MailServer=CN=AULNotes2/O=AUL
MailSetup=650201
MailType=0
MailUpgradeFolder=650201
NamedStyle0=0300426173696300000000000000000000000000000000000000000000000000000000000000010
10100000A0000000000000100A0050A0000006400A0050A00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000009404000000000000
NamedStyle1=030042756C6C6574000000000000000000000000000000000000000000000000000000000000010
10100000A000000000000000008070A000000640008070A00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000049404000000000000
NamedStyle2=0300486561646C696E6500000000000000000000000000000000000000000000000000000000010
101010B0C0000000000000100A0050A0000006400A0050A00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000009404000000000000
Names=names.nsf
NameAddressingDlgLastViewName=0,List by name
NeedDPABfixup=0
OptimizeImagePasteSize=1
PoliciesLocalViewModTime=85257A97:00538599
Preferences=32
PromptForLocation=0
QuoteLineLength=70
QuotePrefix=>
Region=en-US
ReplDefEncrypt=1
ReplDefEncryptType=2
ReplDefFullDocs=1
ReplDefPartAtchLimit=0
ReplDefPartAtchLimitAmt=40
ReplDefPartDocsLimit=0
ReplDefPartDocsLimitAmt=40
ReplDefReplImmed=1
Spell_Lang=1033
Spell_Preferences=0
SUT_NEXT_UPDATE=06/18/2010 12:54:39 AM
SU_Delay_Days=0
SU_File_Cleanup=C:Documents and Settingst1notesApplication Datasmkits
SU_In_Progress=0
Su_Next_Update=06/18/2010 12:54:39 AM

SelectNameDialogSize=259,764,153,471,
SelectNamesDialogSize=214,810,153,526,
ServerRestarted=0
ServerSetup=850200
Setup=850200
ShowAccelerators=1
TemplateSetup=850200
UNICODE_Display=1
UserName=SWPNTS02
WindowSizeWin=20 15 984 715
WWWDSP_Prefetch_Object=0
WWWDSP_Sync_BrowserCache=0
Win32InfoboxPos=32 110
WindowSizeACLAddUser=358 153 307 112
WindowSizeBookmark=325 153 374 302
WindowSizeBrowse=253 153 518 318
WindowSizeChooseServers=350 153 323 298
WindowSizeKeywords=362 153 299 268
WindowSizeOpenDoc=238 153 548 290
WindowSizeOtherServer=343 153 337 212
XLate_CSID=52
;SMTP Configuration
;--------------------------------------------------------------------------
TNEFEnableConversion=1
;Time and Date Settings
;--------------------------------------------------------------------------
DST=1
DSTlaw=3,2,1,11,1,1
TimeZone=5
;Agent Manager
;--------------------------------------------------------------------------
ATCLastRunDate=07/08/2013 03:50:53 AM
;Clustering
;--------------------------------------------------------------------------
Cluster_Replicators=5
MailClusterFailover=1
Server_Cluster_On=1
Server_Cluster_Default_Port=Cluster
Server_Availability_Threshold=10
;Logging
;--------------------------------------------------------------------------
Console_Loglevel=2

Console_Log_Enabled=1
Log_AgentManager=0
Log_Replication=0
Log_Sessions=0
Log_Tasks=1
Log_Update=0
Log_View_Events=0
Log=log.nsf, 1, 0, 7, 40000
Passthru_LogLevel=0
PhoneLog=2
Log_MailRouting=30
;Fault Recovery
;--------------------------------------------------------------------------
Crash_LogFile_KB=10240
Crash_MSGSize_MB=20
Crash_NSDSize_MB=10
Crash_Remove_Data=0
CrashLimits=3 15
Fault_Analyzer_Enabled=0
File_Retention_Days=365
FaultRecovery=1
FaultRecovery_Build=Release 8.5.2FP4 HF60
;Transaction Logging
;--------------------------------------------------------------------------
Previous_TransLog_Path=T:NotesTransLog
Previous_TransLog_Status=1
Previous_TransLog_Style=2
TransLog_AutoFixup=1
TransLog_Path=T:NotesTransLog
TransLog_Performance=1
TransLog_Status=1
TransLog_Style=2
TransLog_UseAll=0
;Indexing
;--------------------------------------------------------------------------
FT_Binary_Filter_Off=1
ReplDefFullText=0
Updaters=1
View_ReBuild_Dir=D:NotesDataTemp
;Statistics and Events Configuration
;--------------------------------------------------------------------------
Cleanup_events4_DDMConfig_view=0
Cleanup_events4_DDMFilters_view=0

Cleanup_events4_messages_view=0
Cleanup_events4_methods_view=0
Cleanup_events4_on_first_night=0
Cleanup_events4_stats_view=0
EventSetup=850200
Event_Pool_Size=10485760
;HTTP Configuration
;--------------------------------------------------------------------------
DominoConfigLevel=1
HTTPDisableUrlCache=1
HTTPJVMMaxHeapSize=64M
HTTPJVMMaxHeapSizeSet=1
WebAdminSetup=850
iNotes_WA_ChromeBrowserBlock=0
iNotes_WA_DisableFirefoxAwareness=0
iNotes_WA_EnableEditModeLink=1
;Directory Catalog
;--------------------------------------------------------------------------
NameLookup_Trust_DirCat=0
;LDAP Configuration
;--------------------------------------------------------------------------
DisableLDAPOnAdmin=1
LDAPNoAutoStartRepairDIT=1
LDAPServer=ldap://aulnotes2.aul.com:389
LDAPServerSSL=ldap://aulnotes2.aul.com:0
;ID Vault
;--------------------------------------------------------------------------
IDVault_Count1=1
IDVault_Stamp1=06/17/2010 12:54:50 AM
KeyFileName_Owner=CN=AULNotes2/O=AUL
ServerKeyFileName_Owner=CN=AULNotes2/O=AUL
;DAOS
;--------------------------------------------------------------------------
DAOSBasePath=F:DAOS
DAOSCatalogState=1
DAOSDeferredDeleteInterval=15
DAOSEnable=1
DAOSMinObjSize=65536
DAOS_Load=1
;DB2
;--------------------------------------------------------------------------

DB2QueryViewRowLimit=500
DB2_DBS_Per_Schema=10
DB2_PW_EXP_Alarm_Days_Prior=15
DB_Creation_Default_Type=NSF
;Debug
;--------------------------------------------------------------------------
DAOSEST_BUCKETS=64,128,256,512,1024,2048,3072,4096,8192,16384
Debug_Capture_TimeOut=1
Debug_enable_update_fix=8191
;
;--------------------------------------------------------------------------
Cluster_TCPIPAddress=0,192.168.14.4,0
;Double
;--------------------------------------------------------------------------
;NLCACHE_VERSION=4
;SCHEDULE_NO_CALCSTATS=1
;SERVER_SHOW_PERFORMANCE=1
;Other
;--------------------------------------------------------------------------
## FT_FLY_INDEX_OFF=1 ##
$ShowDoc=9/20/2008 9:22:42 PM
;DEBUG_OUTFILE=debug.txt
;Debug_ThreadID=1
;DisabledPorts=TCPIP1,Cluster,LAN0tcpip,LAN3tcpip,SPX,LAN1,LAN2,LAN4,LAN5,LAN6,LAN7,LAN8,CO
M1,COM2,COM3,COM4,COM5
;LOG_CONNECTIONS=1
;Ports=
^ this value is empty, you should remove it.
;Server_Cluster_Default_Port=Cluster
;Server_Cluster_Probe_Port=Cluster
;smtpclientdebug=1
EmailXtenderBadDocsInt=60
EmailXtenderShortcutCacheInt=15
EmailXtenderShortcutDb=ExShortcut.nsf
EmailXtenderShortcutExclude=nadminp,ncompact,nupdate,nupdall
EmailXtenderTempPath=D:notestemp
EmailXtenderUserName=Legato nSysAdmin/AUL
Ex_Shortcut_Compact_Dbs=1
NTS_Java_Parms=-Xms625M -Xmx625M
Notes_wa_GZIP_Disable=1
ex_log_shortcutting=1

I will be using the DCT to analyze the Notes.ini files, and when given access to the current Notes
environment, I will analyze the Server Documents as well.
What is the Domino Configuration Tuner?
The Domino Configuration Tuner (DCT) evaluates server settings according to a growing catalog of
best practices. All servers in a single domain can be evaluated together. DCT generates reports that
explain the issues DCT uncovers, suggest mitigations, and provide references to supporting publications.
DCT is intended to provide customers with easy-to-use self-service configuration analysis so that their
installations are more robust and experience better performance. A single Domino server includes
thousands of configuration options. DCT provides best practice analysis as well as worst practice
disclosure. It is our expectation that DCT will help reduce total cost of ownership by assisting in the
identification of existing configuration problems.
DCT looks at settings in Server documents, NOTES.INI, and database advanced properties.
Configuration settings are flagged when their values are know to cause problems based on prior
customer experience. Out-of-range and unexpected values are reported so that undefined behavior can
be prevented. Suggested adjustments help administrators achieve known server performance
improvements.
Some Suggestions during my analysis:
Below is my research and some of IBM’s Notes.ini Best Practice Settings for optimal performance
As you upgrade, migrate to new hardware, and implement other vender solutions in your IBM Lotus Notes
and Domino environment, the notes.ini file may collect unnecessary and obsolete configurations which
can affect stability and performance.
IBM Lotus Support recommends maintaining "clean" notes.ini configuration files as this action aids in the
troubleshooting and maintenance of your Lotus Notes Clients and Lotus Domino Servers. As workstations
and servers are upgrade, migrated and integrated with other products, unnecessary, unwanted, and
obsolete variables often build up over time.
NOTES:
 ALWAYS create a safe, backup copy of the notes.ini (for Lotus Domino Server especially) before
introducing changes.
PercentAvailSysResources
In Domino Release 5.0.4 or later, you can control the amount of memory allocated to your server by using
the PercentAvailSysResources variable.
Before the introduction of this variable in 5.0.4, each Domino server assumed it had 100 percent of
system memory available to it. With the PercentAvailSysResources variable, you assign a portion of
memory to the server by specifying a value from 2 to 100, which represents a percentage of a system's
total physical memory. For example, if you want to dedicate 75 percent of system memory to Domino, add
the following line to the NOTES.INI file:
PercentAvailSysResources=75
This effectively leaves 25 percent of memory for other applications. To follow through with the example, a
Domino server on a system with 256MB of RAM and the NOTES.INI setting
PercentAvailSysResources=75 would reserve 192MB for itself .
You can also allocate memory on partitioned servers using the PercentAvailSysResources variable. For
example, if you have a Domino server with two partitions and want to control the memory resources

allocated to each partition, you could set the NOTES.INI of Partition 1 with the line
PercentAvailSysResources=60 and the NOTES.INI of Partition 2 with the line
PercentAvailSysResources=40. In this case, Partition 1 would use 60 percent of the system memory
resources and Partition 2 would use 40 percent. Make sure that the sum of the values you specify in each
partition does not exceed 100 percent.
To reserve system memory for other applications, you can choose values that total less than 100 percent.
Another use for PercentAvailSysResources is with a Citrix MetaFrame or Windows terminal server. For
example, if there are 20 data directories on the terminal server, then the NOTES.INI file in each client
data directory could contain the parameter PercentAvailSysResources=5. This limits each user on the
terminal server to only 5 percent of the server's system memory.
Note: If you use the PercentAvailSysResources variable, you should not use the NSF_Buffer_Pool_Size
variable described below unless Lotus Support recommends it.
NSF_Buffer_Pool_Size
The PercentAvailSysResources variable in Release 5.0.4 and later is the preferred method for controlling
memory allocation in Domino. For Domino releases prior to 5.0.4, you can enhance memory allocation by
using the NSF_Buffer_Pool_Size variable-but only in certain areas and under particular circumstances.
The NSF_Buffer_Pool_Size variable has a more narrow purpose than PercentAvailSysResources. It lets
you specify the maximum size of the NSF buffer pool, a section of memory dedicated to buffering I/O
transfers between the NIF (Notes Index Facility) indexing functions and disk storage. By changing the
value of NSF_Buffer_Pool_Size, you can control the size of the memory section used for buffering. (You
can also use NSF_Buffer_Pool_Size_MB to set the size of the pool. This variable performs the same
function as NSF_Buffer_Pool_Size, but lets you specify the size in megabytes instead of bytes.)
If your Domino applications use indexing, it is tempting to think that you can simply increase the size of
the NSF buffer pool and dramatically enhance server performance. However, just as adding physical
memory to a system does not always boost performance, designating a bigger NSF buffer pool might not
produce dramatic results.
In fact, Domino does a good job by itself of allocating memory to the NSF buffer pool by
calculating a default setting based on fixed overhead and total memory available. (Depending on
the Domino version and other factors, the default usually amounts to between 25 percent and 33
percent of system memory). What's more, changes to the NSF buffer pool allocation algorithm in R5
mean that the Domino server uses only the amount of memory it needs, up to the default or specified
amount. The R4 strategy pre-allocated and reserved the entire default or specified amount of memory.
For example, in R5, when you specify a value of 10,000 for the buffer pool size and only 5,000 is needed,
only 5,000 is allocated. In Domino R4, if you specify a value of 10,000 for the buffer pool size and only
5,000 is needed, 10,000 is allocated
Both Iris and Lotus technical support recommend that you let Domino handle NSF buffer pool allocation
and stick with the default setting the program generates. There are exceptions to this rule, however.
Under Domino releases prior to 5.0.4, the following servers should have the NSF_Buffer_Pool_Size
specified in the NOTES.INI:
Partitioned servers
You should specify NSF buffer pool size on all partitioned servers. Each partition should have the variable
set in its NOTES.INI file, so that multiple partitions do not cumulatively starve the system of memory by
each taking too big a piece of the pie. The rule of thumb is to take 30 to 35 percent of the amount of
physical RAM, divide that value by the number of partitions on the machine, and use the resulting number
as the NSF buffer pool setting for each partition. This is just a starting point; you can tweak each partition
according to how it uses Domino.
Servers with more than 5GB of physical memory
In an installation with more than 5GB of physical memory, one of the two NSF buffer pool variables
should be set in the NOTES.INI for the Domino server. It is worth noting that the NSF buffer pool setting
in R5 up to and including 5.0.3 should not exceed 1920MB (or 2,013,265,920 bytes).
Every day a large message is sent to a large group of users. When this message is sent, all other mail
backs up until the large message is delivered to all recipients.
There a way to limit the number of threads allocated for sending such messages!

This issue was reported to Quality Engineering as SPR# JCHN4YCSKC, and has been addressed in
Lotus® Domino® 6.x in the form of a notes.ini parameter.
Starting in Domino 6.0, the following notes.ini parameter can be used to address this issue.
RouterMaxConcurrentDeliverySize= <size in bytes>
When enabled, this parameter will allow Router to open only one copy of a message at a time if it is
greater than the size (in bytes) specified. This way the message will be delivered to each recipient using
only one single thread.
Note: Usually several threads may process the delivery to a large group of recipients, but this parameter
will prevent this behavior.The downside being that large messages might take slightly longer to be
delivered, but it keeps down BLK_OPENED_NOTE usage in the Router and the number of pools that the
router has to create to deliver large messages simultaneously to multiple users on the same server
concurrently.
Another alternative is to set message size restrictions in the Configuration document so that mess ages
greater than a specific size are sent as low-priority. This way the delay will occur only in off-peak hours.
To capture detailed logging, enable both in notes.ini
DebugRouter =1
and
Log_Mailrouting =40
The following message will appear in the debug output:
"Router: Limiting concurrent delivery for note %d:%d, size: %d".

Section VII - Hardware specs for new servers
???? TBD As of 8/28/2013 we have been notified that these may be subject to change due to the
Legato/OneSource setup/migration

Section IIIV. OS specs for new Domino servers
Windows 2003 R2
Note the following points about Notes/Domino support for Windows 2003:
o Support for Windows 2003 server/Windows 2003 Enterprise Edition will begin with
Domino versions 6.0.3 and 6.5, including Domino 7 server. These Domino releases also
support Windows Server 2003 R2.
o Windows 2003 x64 Edition requires Domino 7.0.1 and higher.
Windows 2003 R2 x64 Bit requires Domino 7.02 or higher
o The Notes Release 6 and 7 client will not be supported on Windows 2003.
o Lotus will support any Service Packs that are released for Windows 2003
o From 6.5 Release Notes Citrix support statement: The Notes client is supported on Citrix
Metaframe XPe FR3 on Windows 2000 and Windows 2003 server using NT and MAC
ICA1 clients.
Windows Server 2003 R2 Standard Edition x86-32 and future OS fix
packs
Bitness: 32 Bit
Deployment Role: Server
Hardware platform: x86-
32
Symantec A/V:

How to configure Lotus Notes Server to work with bvAdmin Workflow Server email notification:
1. During the installation of workflow, there will be a few errors with regard to the product not being able to
find the exchange server. The errors can be IGNORED.
Simply specify lotus Notes server [Domino server] as SMTP server in workflow Server Activation Wizard.
[SMTP Port Number & Authentication needs to be changed - from Advance option in workflow SAW,
according to the settings on Domino server. Default settings - SMTP port = 25, Authentication mode -
Anonymous]
2. After the workflow server install is complete, you will need to configure your approver/user in AD such
that they will be able to map to the Lotus Notes server for their email messages.
This is done with ADSI Edit. The ADSI Edit utility can be retrieved from the Windows 2000 Server cd
under Support Tools & is detailed in the following steps.
3. Use the following command to verify if SMTP is configured and running correctly:
c:>telnet xxx.xxx.xxx.xxx 25
(where xxx.xxx.xxx.xxx is the ip of the domino server)
Here is an example:
c:telnet 10.24.4.8 25
You should get a line on the screen of the effect:
220 domino.mybvadmin.com ESMTP Service (Lotus Domino Release 6.0) ready at Wed, 8 Jan 2003
06:48:44 -0600
From here you can type (but you may not see what you are typing), the following command:
helo domino.mybvadmin.com
(helo is the command name, & not a misspelling)
This command would then come back:
250 domino.mybvadmin.com Hello
domino.mybvadmin.com ([10.24.5.11]),
pleased to meet you
If this command fails to bring back any information, then the lotus notes server is not operating
correctly.
4. Update the proxyAddresses property of approver/user to whom email notification is to be sent.
Example: If approver is NT/AD account "ldomJoe" having mail id, Joe@ldom.us.com on lotus notes

server then add "SMTP:Joe@ldom.us.com" entry in "proxyAddresses" AD property of that user. This can
be done using ADSIEdit Available in the Window
Section VIII. Lotus Notes setup for new servers
It is to my understanding that there will NOT be an upgrade to a different version of Domino on the new
servers; therefore we will be using 8.5.3x.
Mail file size: As mail files have grown at a tremendous rate over the last few years, their size has had
impact on the servers. One of the reference articles addresses this. Understand that it is not just
processor resources; many are finding that with larger mail files, and huge disk drives, they are suffering
from I/O delay. Domino mail does a lot of I/O, and it is random I/O, so the number and speed of your disk
drives becomes a sizing concern as well. If this is really becoming an issue, do you have plans for quotas,
archiving, or other controls that will have to be accounted for in the sizing?
Clustering: This can affect your sizing efforts in several ways. First, when sizing, you have to look at
"worst case"; how many users do I need to support when my failures occur at peak time. If you have a
complex cluster architecture, then you may have to think a bit about what sets of users fail where, and
how many machines failing are you trying to handle at once. If you do not load balance the clusters in
some way, or again if you have a cluster architecture that is not a simple one to one, understand that
cluster replication creates an added workload, beyond the normal workload, and you have to add that into
your calculation.
Local replicas: Using local replicas can change your equation for sizing, and it can, if done right, reduce

needed server resources. With a local replica the normal workload of user activities is moved to the
workstation. It is replaced with the load of replication. Therefore, you need to pay attention to the
replication interval you or your users specify, and if the users are actually replicating more than one
database to your server. Consider that essentially all users will now be active. If their Notes client is up it
will be replicating during the scheduled time frame. Think about xxx users replicating n times an hour,
multiplied by however many files. If the total number of replications an hour takes your breath away, think
about adjusting the interval. We would recommend 10 or 15 minutes in most cases, but the user can
always force replication from their replication tab if they need to. And a warning: if your users keep a local
replica going "just in case" but use the server copy of mail for normal work, then you have to account for
both workloads. With local replicas you are likely to see a "consistent workload" as replication happens
consistently all day, with much smaller peaks than you would see with users accessing the server copy.
Port Encryption/SSL: With so many concerns today about security you may implement these.
Understand that if done by Domino you are using software to encrypt and decrypt each message that
flows, using sophisticated formulas. Clearly this can have server impact. Some do use "devices" in their
network to do SSL, rather than adding this workload to their Domino server.
Full Text Indexing: This is a useful feature; makes things easier for your users to find. However, it will
increase the size of the mail files to contain the index. There is, of course, processor impact as well. It
takes resources to build and maintain the index, and, once there, your users will "search", thus adding a
new function to their work scenario, requiring more server capacity.
Roaming user: This function can have more or less impact depending on your implementation choices.
Understand that it adds a replication workload (back to the local replication discussion on interval), and
when a user signs on to a "new" workstation it causes the creation of new replicas as they download their
information from the server.
Transaction Logging: Transaction logging is a great function, has lots of advantages and many different
options, but is clearly something that will take some amount of resources. Understand that you are writing
updates a second time, so server resources are used. You should plan on having a separate disk drive
for this, as it is written sequentially.
Anti virus / anti spam: Often these applications are implemented on your Domino server with third party
software. You should ask the vendor for advice on the impact, and it may well vary based on parameters
you chose. Understand what it going to happen. Every message is going to be "evaluated, analyzed, and
tested" to try and determine if it is acceptable. Clearly this takes processor time, and it is probably
dependent somewhat on the amount of traffic flow in and out of your server.
Agents: Look at agents you implement (or add to the Domino system with add on products), as well as
your users, if you allow them to create/run agents. Evaluate agents you write/add before putting them into
production. Look at the agent manager load on your system today. Take that into account in your sizing.
And if you let users write agents, understand that users do whatever users want to do, and sometimes
things they really did not mean to do. Add something into your sizing to account for that, and monitor what
really happens.
In regards to Legato:
Outside applications: There are many Lotus partners who sell "add on" functions for Domino. These are
great things, and provide great functions, but are something you must account for in your sizing. They

may have minimal impact, or they may have a lot of impact. Sending and receiving faxes via Domino is
probably not much impact from the occasional fax, but would be a concern if you have users who
regularly "fax" to large groups. Mail interfaces to cell phones probably don't have much impact if this
is just for a handful of executives; however, if you have a significant number of users, think about
how many times the mail file is opened, scanned for new mail and closed (number of users,
number of times a minute/hour). Understand that these functions typically run for every user
enrolled, all day, every day, and they create a workload over and above normal user load. Look at
each application you add to your mail server and consider how much impact it might have, and
ask the vendor who supplies it for their assistance.
Growth: Here we venture a bit into the world of capacity planning, but clearly you do not want to
go through a sizing process only to find that by the time you have implemented the new hardware
it is already "consumed" at peak times. If you have been doing capacity planning over time, take your
growth rates (processor, I/O, mail file size, number of users, and so on) into consideration, and add a
year or two of anticipated growth to your sizing. Plan ahead.
NOTE: If you have plans to change your Domino environment (implement new functions, make custom
modifications, etc), think about how this might impact needed server resources. It is quite possible that a
“simple change” can have significant impact on required server resources.
If you do not run transaction logging, but plan to turn it on with a new release/hardware, understand that it
takes some resources. Understand what "roaming users" do and how you set them up can change the
amount and type of required resources. Consider also full text indexing, SSL, newer versions of the
Notes Client. or implementing local replicas. These are all great functions, but all come with some
potential impact, maybe more, maybe less, on server resources. While this is getting into
performance and capacity planning, understand that if you have ‘plans’ for these kind of things,
then when sizing for new equipment, you should take these factors into consideration
Section X: Notes Traveler server setup and migration best practice
FOR Notes Domino Traveler Server, You must have the following:
Domino Server Support
Lotus Notes Traveler 8.5.3 must be installed on a Domino 8.5.3 Enterprise Server or Domino 8.5.3
Messaging Server. The xSP (Service Provider) configuration of Domino is not supported for any level of
Domino Server.
Remote Mail Database Support
Lotus Notes Traveler server can connect to remote mail databases hosted by Domino 7.0.2 servers or
above. The Domino remote mail server can be any operating system supported by Domino.
Mail File Template Support
Lotus Notes Traveler server supports standard and iNotes mail file templates, version 6.5 and above.
Here are the definitions of “what Lotus Notes Traveler provides”:
Automatic wireless delivery of Lotus Domino ：- Email and PIM (Calendar, Address Book, To Do,
Journal), Security Settings, Two-way synchronization over the air client or profile installation
Works over all wired / wireless connections (CDMA, GPRS, GSM, Wi-Fi, etc.)

Server Requirements:
Disk
Space
Minimum of 500 MB of free disk space for database and log files.
Memory The Lotus Notes Traveler server requires a minimum of 512 MB of free RAM. This
is in addition to the memory required by the IBM Lotus Domino server itself. As
more Lotus Notes Traveler users are registered with the service, the memory
needed will increase and it is not uncommon for the total virtual memory required
for Lotus Notes Traveler and Domino to exceed 2 GB of RAM. Thus, while 32-bit
operating systems are supported, 64-bit operating systems are strongly
recommended for all deployments with a significant number of users.
Network
Protocols
Lotus Notes Traveler supports any network supported by a device that provides
an HTTP/TCP or HTTPS/TCP connection between the device and the Lotus
Notes Traveler server. Examples include: GSM, GPRS, 802.11x, and Wi-Fi. In
addition, Lotus Notes Traveler can utilize Short Messaging Service (SMS) for push
notifications instead of HTTP/HTTPS.
Operating System
Windows Server 2003 Standard/Enterprise/R2 (32 and 64 bit)
Requires Domino Enterprise or Messaging server
- Runs in 32-bit or 64-bit mode on Domino server
Windows Server 2003 R2
Enterprise Edition x86 (32-
bit)
32-bit operating systems are supported but 64-bit operating systems
are strongly recommended for all deployments with a significant
number of users.
Remote mail server
- Domino 7.0.2 servers or above
Mail file templates
- Standard and iNotes version 6.5 and above
Client Requirements:
Apple Devices and Operating Systems:
- iPhone 3G, iPhone 3GS, iPhone 4,iPhone 4S
- iPad and iPad2
- iPod Touch
- Apple OS 3.x, iOS 4.x , iOS 5.x
Android Devices

- Android OS 2.0.1 and above (including tablets and OS 3.x)
Nokia Devices
- Nokia Series 60 3rd editions (including feature pack 1 and 2)
- Nokia Series 60 5th editions
- Nokia Symbian^3 edition NEW
Windows Mobile Devices
- Windows Mobile 6.0, Standard, Professional and Classic versions
- Windows Mobile 6.1, Standard, Professional and Classic versions
- Windows Mobile 6.5, Standard, Professional versions
Best Practices – Capacity Planning
Updated capacity planning and machine guidance information
- Operating System selection and Domino Server application type (32-bit vs.
64-bit)
- CPU speed and capacity
- Disk storage configuration
- Physical RAM requirements
- Back-end network speed
Install Lotus Notes Traveler on a 64-bit operating system
Access to > 2GB virtual memory is critical in larger mobile user populations (> 300)
Review java memory usage and consider setting maximum java memory to 1024 MB or higher for Lotus
Traveler task to handle spikes
Co-locating Lotus Notes Traveler with other applications:
Avoid running multiple applications on the Lotus Notes Traveler server, unless the deployment of
users on the server is very small, typically less than 100 users.
Monitoring resource usage
- memory utilization:
tell traveler mem
- HTTP thread usage:

show stat http.
Verify HTTP thread allocation matches expected number of active devices
- Set HTTP Active Threads to 1.2 times active devices
Domino HTTP threads are allocated at startup, so do not allocate
NOTE: Extremely critical for 32-bit systems which have limited memory more threads than needed -
thresholds
If using a proxy, validate it has enough HTTP threads to handle device client push
- Similar to Domino HTTP server, proxy must be able to handle long poll-push transactions from devices
Best Practices – Database defragmentation
Internal database's files are stored under the datatravelerntsdb directory. Not recommended to
delete the ntsdb folder on the system.
NOTE: Here is a command to defragment Lotus Notes Traveler's internal database, to compact
and optimize the database for performance.
The defrag feature can only be run at startup. Recommended to run once a month.
How to run defrag:
- 8.5.2.4, 8.5.3.1 and later releases:
Add NTS_DEFRAG_INTERVAL_DAYS to the notes.ini
- 8.5.2.2, 8.5.2.3 and 8.5.3.0 releases ：
load traveler –defrag
Best Practices –Control Server Access
§ Restrict access to the Lotus Traveler service
- Access server: Users or groups
- Device types (ALLOWED_USER_AGENT_REGEX in NTSConfig.xml)
May need to update as new devices are released
NOTE: Traveler user web page can be configured to add/remove options
NTS_ENABLE_* notes.ini parameters
Notes Traveler Command References:
tell traveler <command>
➔Reset <device> <user> - Force a synchronization reset for a user's device.

➔Delete <device> <user> - Delete Lotus Traveler data for a user's device.
➔Dump <user> - Dump the information for a user to a file.
➔Mem Show - Displays current memory usage.
➔Show <user> - Display all the information for a user and the user's devices.
➔ShowActive - Display the users who are currently syncing.
➔ShowUsers - Display all registered users.
➔Shutdown - Stop accepting new work requests, allow current work to
complete, and then Quit.
➔SystemDump <options> - Save the current Lotus Traveler system state.
− Use 'Help' for more options.
➔Version - Display the version of the Lotus Traveler Server
Section XI: Why virtualize the Lotus Notes Domino servers?
Traditionally, Lotus Domino servers have very high resource utilization (disk, network, CPU and memory).
Even so, they are great candidates for virtualization. There are three critical points to successfully
virtualize Domino servers: Know your workloads, architect your virtual hardware correctly and properly
configure Domino servers and virtual host servers.
You may wonder why you would want to virtualize a busy Domino server if it's already using all resources
of a physical server at a maximum. The main point of virtualization is running multiple servers on a virtual
host to consolidate hardware and not waste resources, which can be common on many servers.
But virtualization offers many benefits beyond simple consolidation, such as protecting from hardware
failure , snapshots for easy rollbacks when upgrading, hardware provisioning when you need to add or
change hardware and more.
Knowing your workloads means that you should use performance monitoring tools on existing Domino
servers to get a glimpse of average and peak utilization of the four main resources -- CPU, memory, disk
and network. Measure this utilization for at least a week -- preferably a month -- before virtualizing so
that you have enough data to truly understand your resource requirements.
This enables you to ensure that you size your virtual hosts correctly and choose the appropriate
hardware. VMware's Capacity Planner tool can be used to assess your current environment and ensure
you build your virtual hardware correctly.
A crucial decision when choosing hardware for virtual hosts is choosing a storage subsystem, as Domino
is very I/O intensive. Using the wrong type of storage can result in a bottleneck that will reduce server
performance.

Fibre Channel storage area networks (SANs) offer the best performance, but iSCSI SANs are also a good
choice. If you choose an iSCSI storage solution, it's helpful to use a hardware initiator because it offloads
the overhead from your host's CPUs.
Note: Using a network file system (NFS) storage solution is not recommended when virtualizing
Domino servers.
You should try to use the fastest RPM hard drives that you can. RPM drives that reach 15,000 will help
reduce latency and improve disk operation performance. These will also result in higher I/O operations
per second and decreased average seek times. You should also configure RAID groups with as many
spindles (drives) as possible. This ensures that disk I/O is balanced across several drives.
If you use local storage for Domino servers, try to get the largest cache possible on your disk controller
and use a battery-backed write cache (BBWC). This will provide increased performance and write cache
data protection.
When it comes to CPU, ensure that you have enough cores available on your host server to handle a
vSMP Domino server virtual machine (VM). If you plan to use a four vCPU VM, your host server should
have more than four cores available. Otherwise, the hypervisor's CPU scheduler component will have
difficulty finding free cores when trying to schedule the CPU time for the VM. This will result in slow
performance.
Plan on at least double the number of cores compared to the greatest amount you will assign to
any VM. For example, if you're using a four vCPU VM, make sure you have at least eight cores (i.e. two
quad-core CPUs). For a two vCPU VM, you need at least four cores (i.e. two dual-core CPUs).
Domino servers prefer a large amount of memory, so make sure that your hosts have adequate physical
RAM available. However, it is possible to over-commit memory on a VMware ESX host. Be certain that
you don't run out of physical memory or your VMs will start switching to disk and performance
will suffer.
When it comes to network interface cards (NICs), make sure you have enough to ensure that there is
adequate bandwidth available for the Domino servers. Domino servers can generate a tremendous
amount of network traffic as users and servers replicate with the mail router during email delivery.
You should also try to isolate client traffic on separate NICs from the host server traffic. Be sure
that you have enough physical NICs to accommodate this. NICs are fairly inexpensive and you can get up
to four on a single physical card, so you don't want to skimp here.
After you've planned the physical hardware, you must make sure that you configure it --- and
your virtual hardware -- properly. Here are some tips to do so:
 WhenassigningvCPUstoa VM, don'tgo overboard.Most small tomediumDominoworkloadswill
run fine withasingle vCPU.LargerDominoworkloadsworkbestwithtwoor more vCPUs,as

Dominoisverymulti-threaded.Youmayhave to testconfigurationstofindthe numberthatisright
for yourhosts.
You can always add more vCPUs later, if necessary. The fewer vCPUs that a VM has, the
easier it is for the hypervisor to schedule CPU time. You should also set CPU reservations for
use shares to ensure the Domino server has priority access to host CPUs.
When assigning virtual memory to a Domino server VM, make sure to allot enough memory based on
its needs. You don't want to starve the VM if it needs more memory. Try not to use too much, as this
can be a waste of valuable resources. You'll also want to set memory reservations to guarantee that
the VM can access physical host memory and will not swap to disk if host memory is exhausted.
When creating vSwitches for Domino server VMs, create separate ones for client traffic and for
Domino server traffic. Isolate all replication and mail routing traffic between Domino servers from the
client traffic. You should also avoid connecting a single Domino server to both internal and external
networks.
If you want to access Domino servers from the Internet, create a separate vSwitch for external access
only and connect your Domino server only to that vSwitch. Users can then use the Domino pass-thru
feature to connect to internal Domino servers.
When configuring virtual disks for your VMs, there isn't a big performance difference between using
raw-device mappings (RDMs) and traditional virtual disks on VMFS volumes. I recommend using
traditional virtual disks.
You should also plan to use multiple virtual disks on Domino server VMs that are divided onto
multiple physical logical unit numbers (LUNs) or RAID groups. Make sure to put your OS, Domino
databases and transaction logs on separate virtual disks.
Be sure to align your VM file system and guest disk partitions for maximum throughput and minimum
latency.

Section XII: Conclusion
Be sure to understand the limitations and constraints that your chosen operating system, hardware
platform, and architecture bring into play. As Domino is still a 32 bit application, you will find at times that
memory is a constraint. More/faster processors may not be the answer. It may be that you need more
machines with just two processors, or more Domino partitions (DPARs) on a single machine where that is
a reasonable choice (probably not for Windows). Sizing is really about more than processors; it
requires a proper melding of processor, memory, I/O, architecture, and understanding the ove rall
picture. When you are getting new hardware because you have some performance problem, be
sure you really understand what the problem is, and that your new solution really solves the
problem.
And lastly, when you perform sizing, take time to go back and compare the new equipment to the old.
Overall, do you have more "horsepower"? Does it seem reasonable at an overall level, the new
compared to the old? If you were having performance problems on your existing hardware,
understand that your users would really like to do more but have been frustrated by poor
performance. There is some amount of "pent up demand", and when you bring in the new
equipment you will 'release' that demand and may well consume what you thought was going to
be your 'headroom' for some time.
It’s an obvious choice as you can see through this proposal, that there are many caveats to migration in a
Lotus Notes Domino mail environment, there are also so many benefits that exceed the limitations.
Migrating to new hardware is a wonderful segue to a new beginning in performance of OA’s
network. Overall, you are adding resources to the “pent up demand” of your network. AND THAT,
is a positive thing especially for your most important part of your business, your user community.

DominoMigrationProposal

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Ähnlich wie DominoMigrationProposal

Ähnlich wie DominoMigrationProposal (20)

DominoMigrationProposal