After foolishly originally setting up DAOS with the base path under the Data folder (I know it’s against best practice) I came up with the predictable problem of running low of disk space on the logical partition. Adding some disks to the RAID array provided some additional space but it is not easy to resize the basic partition, under Windows Server 2003, so I created a nice new empty partition to relocate some folders to. When the new logical drive was accessible I followed the following steps to relocate the DAOS folder.

1. Open Server document and select DAOS tab.

2. Edit “DAOS base path” value and save document. For example change from DAOS to F:\DAOS (F being the assigned drive letter for the new logical partition).

3. Shut down Domino Server.

4. At OS level move DAOS folder to new location (exactly as specified in the Server document).

5. Restart the Server. Please note restarting the Domino service does not appear to pick up the new DAOS base path. A full reboot of the server appears to be required.

6. When server has started run the console command “TELL DAOSMGR STATUS”. This should list the new “baseStoragePath”.

7. Sit back and relax. Have a beer.

When I originally tried this I only restarted the Domino Service and was confused why it would not pick up the new base path from the Server document. The old magic reboot solved this problem. I am not sure why this is required.

Wishing you all a Merry Christmas and a Happy New Year!   more »

Since upgrading to 8.5.1 I have seen several occurrences of the Out of Office service generating Delivery Failure messages when replying to senders. The messages appear to have been sent to the wrong domain after previously receiving a message from that domain.

A bug in the Out of Service service? Please let me know if you have also seen this?

While Lotus Traveler uses two Notes databases (lotustraveler.nsf and ntsclcache.nsf) to store certain information most of the user state information is stored in an embedded database engine called Cloudscape. Why they have chosen to use another database engine, rather than the Domino one, is a mystery but I would guess that this is due to it requiring a relational database engine – which Domino is not – for the Java Traveler add-in task.

Cloudscape (IBM Cloudscape Referral Page) is a Java based database engine, with a very small footprint, which IBM donated to the open source Apache foundation, in 2004, which became Apache Derby.

The Cloudscape database files are stored in a folder under the Domino data directory called /traveler/ntsdb/. Please ensure that you backup this directory as any file corruption will cause your Traveler task to not work or lose state information about your users. It is not possible to access the information, that is stored in this database, as it it used by the Traveler add-in task and can only be accessed by one process at a time.

It would be nice in the future to see this information stored in a Notes database, so that it can be easily accessed, but I do not know if this would be technically possible to phase out the embedded Cloudscape engine.