Domino @ Symetrik Design

I’ve recently stumbled upon using compact -S5 in our weekly Saturday compact program document.

Like most shops, we run Fixup on Fridays and then Compact on Saturdays on all databases.

We found that a couple of servers that have about 400GB worth of mailboxes were not finishing their compact jobs. The compact was taking somewhere in the range of 36 to 48 hours. We weren’t sure how long it was taking because we had to shut it down on Monday morning when people got into the office and starting trying to access their databases.

I found the -S switch which will compact only database which will only compact databases with more white space than you specify in the . Read the rest of this entry »

I was taking a look at this article at IBM.

I noticed that they added these variables to R6.5.x server:
NSF_DBCache_MaxEntries=4100
Server_pool_tasks=60
Server_max_concurrent_trans=60
Server_show_performance=1
Server_TransInfo_Range=9

and these notes.ini variables to 7.0x server:
NSF_DBCache_MaxEntries=4100
server_pool_tasks=60
server_max_concurrent_trans=60
server_show_performance=1
Server_TransInfo_Range=9
Cluster_replicators=3
FTUpdate_Idle_Time=25
Update_Idle_Time=25
EnableForcedFillOnFileExtend=1
NSF_DBCache_Max_Clean_Hold_Time=9999

Just wondering exactly what they do. It would have been nice if they would have explained the benefits of the performance improvement instead of just comparing the two versions of Domino.

In a recent disaster at our organization, we had to restore the program directory of a server. Since someone built the server with the default d:\lotus\domino and d:\lotus\domino\data, the outsource host facility restored the whole d:\lotus directory and it took us 4 hours waiting while the server was down.

This highlights some points that I always try to make about Domino disk installation: Read the rest of this entry »