197 Lotus blogs updated hourly. Who will post next? Home | Blogs | Search | About 
 
Latest 7 Posts
Fix Available: SMTP regression issue in Domino 9.0.1 FP9 can cause malformed headers
Fri, Sep 15th 2017 169
Domino Performance issue on some Linux Versions
Thu, Sep 14th 2017 207
How to resolve synchronization issues that start after upgrading to IBM Traveler 9.0.1.18 (or higher)
Sat, Sep 9th 2017 15
Traveler 9.0.1.19 with important fixes
Fri, Sep 8th 2017 16
SSLV3 disabled by default since 9.0.1 FP9
Tue, Sep 5th 2017 7
Domino 9.0.1 FP9 SMTP Issue
Wed, Aug 30th 2017 11
midpoints Let’s Encrypt for Domino (LE4D)
Mon, Aug 28th 2017 7
Top 10
Domino Performance issue on some Linux Versions
Thu, Sep 14th 2017 207
Fix Available: SMTP regression issue in Domino 9.0.1 FP9 can cause malformed headers
Fri, Sep 15th 2017 169
TLS 1.2 Connection Issues with mail.protection.outlook.COM
Thu, Jan 7th 2016 17
Traveler 9.0.1.19 with important fixes
Fri, Sep 8th 2017 16
Details about JVM 1.8 Update in Notes/Domino 9.0.1 FP8
Sun, Feb 5th 2017 15
Notes/Domino 9.0.1 FP8 IF1 released
Tue, Apr 11th 2017 15
Notes Client/Windows Crash with Windows 10 Creators update
Thu, Jun 1st 2017 15
How to resolve synchronization issues that start after upgrading to IBM Traveler 9.0.1.18 (or higher)
Sat, Sep 9th 2017 15
Solution for Notes/Domino related process is still running when applying a Fixpack or Hotfix
Wed, Mar 25th 2015 13
IBM Notes V9.0.1 Mac 64 Bit English (CN6VDEN )
Tue, Sep 29th 2015 12


Current Information about NIFNSF
Twitter Google+ Facebook LinkedIn Addthis Email Gmail Flipboard Reddit Tumblr WhatsApp StumbleUpon Yammer Evernote Delicious
Daniel Nashed    

Domino 9.0.1 Feature Pack 8 introduced "NIFNSF" which allows to separate the view/folder index into a separate file.

Let me try to summarized my current experience from my tests and from the field.


There are multiple benefits moving the index to a separate file.

1. Backup Storage Reduction

First of all having the index in a separate file reduces the amount of data that you need to backup.
For mail databases the index is around 10%. If you have DAOS enabled from the remaining data it's about 30%.
So the backup time and backup storage in total is reduced.

2. Size Limit of the data above 64 GB

The total size of a NSF is 64 GB. With DAOS enabled you can increase the logical size of a server based database by moving attachments to the DAOS store.
For DAOS you can have external attachments up to 1 TB. Beyond that size the internal counters might overflow.

But in some cases you still need more that 64 GB for NSF data and the view/folder indexes. With NIFNSF the limit is the 64 GB data in the NSF without the view/folder index.

3. Performance

NIFNSF is intended to deliver better performance than having all data in a single NSF file.

There is a current performance issue. For mail databases there should not be big difference.
But for more complex views in applications the performance with NIFNSF might be not as good as without it.
Tests have shown that it can take double the time.

There is a pending fix that might be delivered with an IF for FP8 which should bring back the performance to almost the same as without NIFNSF.

And for FP9 there is optimization planned to have better performance for concurrent operations. Those changes did not make it into FP8.


So for now you might want to wait at least for an IF before enabling NIFNSF for complex applications.



-- Storage Location for NIFNSF --


There are multiple options to configure where to store the .NDX files which store the NIF data.
What you choose depends on your environment,platform and your requirements.

a.) Have NDX files stored next to your NSF files

b.) Have NDX files stored in a separate folder in the data directory

c.) Have NDX outside the data directory on the same disk

d.) Have NDX stored on a separate disk

There are no one size fits all recommendations. It really depends what storage situation and platform you are running on.

If you can for example on Windows I would store NDX files at least outside the data directory.
On Linux often without a new mount point you might not be able to move the NDX files outside the data directory, because often the data directory is a mount.

If you need to increase your storage anyway because the NSF disk is full, having a separate disk (most of the times virtual disk) makes sense.,
This is a good way for a clean new allocation and it will separate the I/O operations.



-- Enabling NIFSNSF on your Server --


Translog

First requirement is that you are using transactions logging. Circular translog is perfectly OK for that.
And translog is general recommendation for Domino anyway! For stability, fault recovery and also for performance!

ODS 51 or higher

You will need at least ODS 51 for NIFSNSF. But I would recommend using ODS 52 for all databases on your server.

notes.ini Create_R9_Databases=1 will ensure the ODS is updated the next time you run a copy-style compact.

Notes.ini Settings

There are a couple notes.ini settings. The most important setting  NIFNSFEnable=1 enables NIFNSF on your server.

To store the NDX files in different locations (see options above) you can leverage NIFBasePath=path depending on your preferences.

In addition if you want all new databases to be NIFNSF enabled there is another notes.ini setting CREATE_NIFNSF_DATABASES=1 which will ensure that all new databases are automatically NIFNSF enabled.



-- Enabling NIFSNSF on a Database --


Once your server is NIFNSF enabled you can start enabling NIFNSF on your databases via compact.

Please take care not to run the compact operation on all databases. We have seen customers who enabled NIFSNSF also on the DAOS catalog -- even the special database has no views.

I would currently start with mail databases only! And you just specify the right mail directory.

The normal recommendation is to use

compact -c -NIFNSF ON mail/

This will enable the feature and also move existing indexes out of the NSF.
But if the database is in use, the copy-style compact will not be possible.

Instead you could enable NIFNSF on databases without copy-style compact and have a copy-style compact later on with either compact -c or leveraging the DBMT tool which you might have configured anyway.

Once the database is on ODS 51 or higher and NIFNSF is enabled new indexes are created in the NDX file.
But only the copy-style compact will move the views to the NDX file.



-- Checking NIFNSF --


You can check which databases are already NIFNSF enabled and there is also a way to see the size of the NDX. But this command shows all databases.

The most useful commands shows all NIFNSF enabled databases.

show dir -nifnsfonly

show only NIFNSF enabled databases

show dir -nifnsf

show all databases with NDX files also



-- Maintaining Databases with NIFNSF enabled --


I have done some tests. Only with copy style compact the NDX will be compacted.
Many customers are still using compact -B for an inplace, space reduction compact.

There are also other reasons to leverage DBMT which is using copy style compacts and does use space pre-allocation to ensure the NSF is not allocated fragmented.

The copy style compact will also shrink the NDX if needed. A compact -B did not free any space from the NDX file in my tests.

However the free space in a NDX file should be still be reused if released from a purged view/folder index during normal runtime.



-- Tuning for NIFNSF --

A NDX file is a NSF file. The index data needs a container. Therefore if you are running a large server you have to make sure you have sufficient dbcache entries, because the NDX file will also need a cache entry.

By default the dbcache handles depend on the size of the NSF Buffer Pool (which is 1024 MB for 64bit). The number of cache entries is around 3 times the buffer pool size in MB.

3000 DbCache entries should be OK for most servers. But if your server is already on the limit you have to increase the limit.

Here are the relevant server statistics from a current customer example:

        Database.DbCache.CurrentEntries = 4498
        Database.DbCache.HighWaterMark = 4500
        Database.DbCache.MaxEntries = 3000
        Database.DbCache.OvercrowdingRejections = 15220

Your CurrentEntries and HighWaterMark should be alwass below the MaxEntries.
And the OvercrowdingRejections should be always zero!

So in this case it would make sense to increase the number of cache entries to 6000 via:

notes.ini NSF_DbCache_Maxentries=6000

 

---------------------
http://blog.nashcom.de/nashcomblog.nsf/dx/current-information-about-nifnsf.htm
Mar 31, 2017
5 hits



Recent Blog Posts
169
Fix Available: SMTP regression issue in Domino 9.0.1 FP9 can cause malformed headers
Fri, Sep 15th 2017 11:43p   Daniel Nashed
Finally we got IF1 for 9.0.1 FP9 for the issue I reported in an earlier blog post . The regression was introduced by a fix that IBM has removed in IF1 (and I got a hotfix earlier as mentioned in an earlier blog post). The root cause is an issue with malformed headers -- specially the from header that are generated at message itemization. Depending on your configuration this causes garbage chars in your headers. In any case some functionality like SMTPVerifyAuthenticatedSender=1 or capt
207
Domino Performance issue on some Linux Versions
Thu, Sep 14th 2017 10:13a   Daniel Nashed
When working on a larger Domino migration and consolidation project I ran into an new Linux specific performance issues that might hit some of you depending on your Linux version. I have tested with current RHEL 7 servers which are not affected. But on customer site we are using the latest patch level of RHEL 6.9 and I have also seen it with SLES 11 SP2/3. I did not yet test with SLES 12 (maybe someone volunteers to do some testing). There has been an issue in the 8.5.3 code stream which ha
15
How to resolve synchronization issues that start after upgrading to IBM Traveler 9.0.1.18 (or higher)
Sat, Sep 9th 2017 9:21a   Daniel Nashed
If you are running on Traveler 9.0.1.18 and higher you should read the following support flash technote in detail. http://www.ibm.com/support/docview.wss?uid=swg22005703 You must read this technote if you are running on 9.0.1.18 and higher. And with this new information it makes a lot of sense to move to this new version soon. As mentioned before, IBM changed the default security mode for Traveler. Traveler uses a run as user feature to ensure that all functionality is invoked in th
16
Traveler 9.0.1.19 with important fixes
Fri, Sep 8th 2017 7:15a   Daniel Nashed
We have been waiting for Traveler 9.0.1.19 for some important fixes and also updates SQL server support and push certificate update: Support for MS SQL Server 2016 Enterprise Edition. Updated APNS Certificates with expiration 8/1/2018. Improvements for the Run as User Feature. But the most important changes are for the "Run as User" Feature which has been introduced in 9.0.1.18. Some of my customers and issues with Traveler profiles which could not be read correctly in some cases.
7
SSLV3 disabled by default since 9.0.1 FP9
Tue, Sep 5th 2017 2:18p   Daniel Nashed
This change has been discussed a while ago. Now it was finally time to disable default SSLv3 in Domino. The SPR did not make it into the fixlist. Thanks Thibaud Maes for your mail! The change addressed by SPR # DKENAKNSEG will affect all connection types that utilise the native Domino security stack such as HTTPS and secure DIIOP. If you still need SSLv3 you need this new notes.ini parameter ENABLE_SSLV3=1 There are not many applications left that need SSLV3 ... Daniel
11
Domino 9.0.1 FP9 SMTP Issue
Wed, Aug 30th 2017 9:15p   Daniel Nashed
Last Friday a friend contacted me about a SMTP issue. I was able to reproduce the root cause of the issue but the emails I receive still look OK. So it depends on your STMP configuration how much impact this issue has in your infrastructure with FP9. In my environment I see in my SpamGeek log database that sender and recipient information contains some garbage chars at the beginning of the string. This can cause that the header information might get corrupted. We don't know exactly how thi
7
midpoints Let’s Encrypt for Domino (LE4D)
Mon, Aug 28th 2017 3:44a   Daniel Nashed
As posted before I am running my server with Let's Encrypt certificates. The first available client choices for requesting certificates (ACME clients) did not make me happy because I had to install Python just for that. Meanwhile there are multiple tools available including simple shell scripts and also a Java implementation. For Linux running "getssl" script (https://github.com/srvrco/getssl) with a small script to automate the process works quite well. But it is still completely serve
9
Notes/Domino 9.0.1 Feature Pack 9 shipped
Sun, Aug 20th 2017 9:39p   Daniel Nashed
Notes and Domino 9.0.1 Feature Pack 9 is available. The client side and server-side introduces fixes and also new features. The official "flixlist" can be found here --> http://www.lotus.com/ldd/fixlist.nsf/0/12d957b7c277fc728525816300434c53 Here are the highlights and some important comments. JVM Update in Notes Client & Domino Server The security fixed version introduced with a JVM patch for FP8 is included in FP9: Notes/Domino - Java 1.8 SR4 FP5 But this is sti
5
Blog Certificate updated and Let’s Encrypt Update
Tue, Aug 8th 2017 9:30a   Daniel Nashed
My certificate expired after 90 days because I did not track it. And the Let's Encrypt original client configuration did not work any more when I was looking into renewal today. The client was Python based and there is a newer client --> https://certbot.eff.org/ which is officially recommended by Let's Encrypt. It's still complicated to use and you need to have Python installed. But since I first implemented it there are many other ACME clients that properly integrate with Let's Encr
10
SLES 12 SP2 Issues with Domino running with Systemd
Mon, Jul 24th 2017 10:01a   Daniel Nashed
There is a new feature introduced in SLES 12 SP2 which could lead to issues with larger Domino or Traveler servers. The default nproc size is still set to 7400. So in most cases this tunable does still not need to be set in your Domino service file. But there is a new security feature introduced in SLES 12 SP2 which will cause processes fail to start or not able to span more threads. The error you might see is the following: Jul 20 11:02:41 dom-srv kernel: cgroup: fork rejected by pi




Created and Maintained by Yancy Lent - About - Planet Lotus Blog - Advertising - Mobile Edition