|Latest 7 Posts
| Microsoft fixes Notes Client Windows 10 Creators Crash|
Wed, Jun 28th 2017 4
| Traveler 184.108.40.206 with new Security Mode for Mail-File Access|
Thu, Jun 22nd 2017 8
| Notes Client/Windows Crash with Windows 10 Creators update|
Thu, Jun 1st 2017 12
| Security Bulletin: IBM Domino TLS server Diffie-Hellman key validation vulnerability (CVE-2016-6087)|
Thu, Jun 1st 2017 5
| Important Security Fix for IMAP|
Sat, Apr 22nd 2017 3
| NIFNSF Supported Maximum Size above 64 GB!|
Fri, Apr 21st 2017 3
| Disclaimer Attachment Issue not yet fixed in IF1|
Fri, Apr 14th 2017 2
| IBM Notes V9.0.1 Mac 64 Bit English (CN6VDEN )|
Tue, Sep 29th 2015 26
| Details about JVM 1.8 Update in Notes/Domino 9.0.1 FP8|
Sun, Feb 5th 2017 21
| IBM Notes/Domino 9.0.1 Feature Pack 8 Preliminary Release Notice|
Fri, Jan 27th 2017 17
| Notes/Domino 9.0.1 FP8 IF1 released|
Tue, Apr 11th 2017 15
| BM mail support for Microsoft Outlook officially released|
Wed, Jun 29th 2016 12
| Notes Client/Windows Crash with Windows 10 Creators update|
Thu, Jun 1st 2017 12
| Solution for Notes/Domino related process is still running when applying a Fixpack or Hotfix|
Wed, Mar 25th 2015 11
| TLS 1.2 Connection Issues with mail.protection.outlook.COM |
Thu, Jan 7th 2016 11
| Passing a document to an agent without saving it first|
Sun, Apr 6th 2014 10
| Some Additonal TLS 1.0 Information|
Thu, Nov 6th 2014 9
||Current Information about NIFNSF
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.
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 --
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.
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:
Mar 31, 2017
| Recent Blog Posts
Microsoft fixes Notes Client Windows 10 Creators Crash|
Wed, Jun 28th 2017 8:16p Daniel Nashed
Today I got feedback from IBM that the fix that Microsoft releases does solve the blue screen issue with Notes and the customized home page issue. There have been multiple situations in which the client crashed or caused a blue screen because of some Windows UI calls in Notes after the Windows creators update. I am interested to get feedback if the fix does solve all your Notes Client on Windows creators update. Here is a link for the update: https://support.microsoft.com/en-in/help/
Traveler 220.127.116.11 with new Security Mode for Mail-File Access|
Thu, Jun 22nd 2017 9:07a Daniel Nashed
Traveler 18.104.22.168 comes with a couple of minor fixes and a big change in the way Traveler Server access mail-databases. In 22.214.171.124 IBM introduced a new check if the Traveler server is listed in Trusted Servers (Server Security Tab) to show a warning if not. Now we know what IBM was preparing for. The server now acts as the user instead of the server. That's only possible if listed in Trusted Servers. You still need the Traveler server to be listed in the ACL of the mail databases. Trus
Notes Client/Windows Crash with Windows 10 Creators update|
Thu, Jun 1st 2017 12:00p Daniel Nashed
Just got that question today at DNUG. There is an issue with the Notes Client with the current Windows 10 Update - aka Creators Update (Build 1703). According to the responsible person who is at DNUG today, this happens because of changed Windows graphics APIs. IBM is working on a fix which will be available in FP9. FP9 will also have full High Resolution support! We saw a demo with FP9 which really looked great! Here are the two relevant SPRs: SPR LHEYALMCEP : Domino Designer cra
Security Bulletin: IBM Domino TLS server Diffie-Hellman key validation vulnerability (CVE-2016-6087)|
Thu, Jun 1st 2017 6:27a Daniel Nashed
There is a vulnerability in the TLS stack which could lead an exploit which could lead a less secure connection. The good news is that the fix is already included in FP8. So you should upgrade to 9.0.1 FP8 if you have a public facing Domino Server with HTTPS. See the details and reference below. -- Daniel A vulnerability in the IBM Domino TLS server's Diffie-Hellman parameter validation could potentially be exploited in a small subgroup attack which could result in a less secure conne
Important Security Fix for IMAP|
Sat, Apr 22nd 2017 9:13a Daniel Nashed
In case you are running IMAP on a server that is reachable over the internet you should look into this fix ASAP. It might not be that critical for internal services. See details about this vulnerability here --> http://www.ibm.com/support/docview.wss?uid=swg22002280 All versions of Domino are affected!
NIFNSF Supported Maximum Size above 64 GB!|
Fri, Apr 21st 2017 9:02p Daniel Nashed
After getting that question offline and having a discussion on my blog, I checked with IBM if they plan support NIFNSF sizes above 64 GB. Since it is kind of a database container and needs a database handle someone could think that the maximum limit is also 64 GB. That would give us at least 64 GB room for the NIF index -- which would be already a big improvement. But from what I recall from some comments at Connect some years ago the maximum limit was not around 64 GB when they designed it
Disclaimer Attachment Issue not yet fixed in IF1|
Fri, Apr 14th 2017 6:28p Daniel Nashed
As Rob Kirkland commented in one of my last blog posted, the fix in IF1 does not solve the iusse. We both checked with IBM and got the reply that the SPR just changes back the default and disables the change introduced in FP8 for Google calender integration. IBM is working on a fix hopefully makes it into FP9. So for now you should keep the notes.ini Parameter MIMEDisclaimersNoEncode=0 disabled. Thanks to Rob to bring this up! -- Daniel TPONAKFJLP After upgrade to FP8, with
Get Notes FP Version in @Formulas |
Wed, Apr 12th 2017 6:19a Daniel Nashed
In C-API and Lotus Script, Java developers the version information already shown for each FP. For example Lotus Script returns the full version string with session.NotesVersion. But if you want to check the version information in @Formulas @Version will still return 405. There is a new optional parameter which returns the Feature Pack version. So you use @Version to check the version and if it is 405 you check @Version(1) which will return 8 for Feature Pack 8. It is used in the new ma
Notes/Domino 9.0.1 FP8 IF1 released|
Tue, Apr 11th 2017 5:06a Daniel Nashed
Notes and Domino 9.0.1 FP8 IF1 has been shipped and there is also a separate fix for iNotes. All those IFs have the same version number but contain different SPRs! The most important IF is for the Domino Server. It fixes the disclaimer issue I reported before. And also the performance fix for the new feature NIFNSF which was introduced in in FP8. Be aware that NIFNSF is a server feature and not a client feature. It requires translog enabled on your server! Translog is not officially
Current Information about NIFNSF|
Fri, Mar 31st 2017 10:42p 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 dat