Mblazar Jan 29, 2009   3:21 PM GMT

All of the information from the previous answer is good, but the concern is really about you and what you want to do. There is nothing wrong with files that big, but they certainly can become unmanageable. The bigger the data, the bigger the views, indicies, etc. And if it corrupts, you have a major concern around restoral. I would personally look to break it up into archives (I always go with yearly ones) just so that I could manage the files easier. But it's completely up to you. The files are fine as is. It's a choice of risk management at this point.

335 pointsBadges:

Fummy Jan 30, 2009   10:05 AM GMT

Huge nsf files cause some trouble. For Example, server crush, database corrpt, taking long time for maintenance, and so on. In my experience, size of database should be less than 2 GB. I took the trouble to maintain Huge nsf files.

10 pointsBadges:

Davidkillingsworth Feb 4, 2009   12:18 AM GMT

I manage an environment with 700 mailboxes that are greater than 2GB. The physical limit is 64GB as listed in the links above. However, anything beyond 2GB becomes very difficult to manage. 1. Database become corrupt very often. 2. Running Fixup or Compact on a weekly basis as part of Domino routine maintenance becomes problematic because the server is always running the maintenance on the databases. In fact, you'll need to split up fixup and compact to run on specific directories during different evenings of the weeks. 3. Backups take forever. 4. Opening the mailboxes takes a very long time because it has to index the inbox every time you open it (if the user does not file messages to folders, which most don't). 5. You pretty much can't have full text indexing turned on because the full text indexing will be continuous around the clock on your server. 6. We've had some very strange things happen with Blackberry Enterprise Server accessing very large mailboxes and causing the BES servers to crash. 7. If users have local replicas of their mailboxes, sometimes their hard drive is not large enough, sometimes the local replica becomes corrupt on the hard drive because no maintenance is ever run on it. 8. Creating new replicas onto new servers can take a week. The list goes on. These are real world examples of issues that I come up against every week. The best practice is to have quota policies in place that the upper management supports. The second major thing to note here is that a proper archiving solution needs to be implemented. The local archiving that is built into Notes is often times not sufficient if you have so many huge mail files.

175 pointsBadges:

divingdwarf May 30, 2013   10:39 AM GMT

As a Lotus Notes victim humble user, I can say nsf files above 1,5-2GB may be a bad idea. You may not lose emails, but their location (in folders) will not be the same,as they may be dislodged, if you allow me the term.

10 pointsBadges:

Magie007 Jan 22, 2015   0:04 AM GMT

Bigger the data, bigger the risk. Although the handling all comes to the performance that is beneath the database. If the performance of the server and the client and the network can manage, the database of a greater size should be handled well. But at a size near 64 GB the trouble comes in a package, once itget corrupt, most of the maintenance task (compact, fixup, updall) will not help, from this point DB can only get restored or replicated back from a working one.

215 pointsBadges: