Lotus Nut

Paul Mooney reminded us the other week that we should do this - and I agree! Over at Vaughan Rivett's blog, he's discussing some of the misunderstandings surrounding DAOS. He brings up several good points, but does question whether DAOS should be enabled on mail.box files. Of course, each situation may be a little different for every environment, so it's up to you to determine if you want to do this. But keep in mind that, like Vaughan states, DAOS is for any application - not just mail!

If I'm a daosified mail user and am using a CRM application to save a copy of an email message directly into the CRM, then if DAOS is enabled for the CRM application the attachment will be shared in DAOS! But if I want to send that email to a colleague and mail.box doesn't have DAOS enabled, then that attachment will be written to mail.box and then when it's delivered to the recipient's mail file DAOS would associate it as a duplicate from my mail file. But, if mail.box has DAOS enabled, then the attachment will never be pulled back out of DAOS (meaning there will not be the disk i/o associated with the transaction) and the router will know that it already existed in DAOS and not try to pull it back out. So, in most cases you will want to enable DAOS on your mail.box files. (Of course multiple server hops will not be aware of this currently, but for mail users on the same server it should be ok.)

Also remember that you'll need to enable transaction logging on your mail.box files. This may mean that you will need to disable the notes.ini settings for MailBoxDisableTXNLogging=1 and/or RM_NO_LOG_LARGE_OBJECTS=1. You will also need to manually enable transaction logging on the database with the router off by using load compact -T on each of your mail.box files.