I have implemented DAOS on a Lotus Domino Server (8.5.3 FP2) as follows:
Lotus Domino Server Document:
- Store file attachments in DAOS: Enabled
- Minimum size of object before Domino will store in DAOS: 64000 bytes
- DAOS base path: E:\DAOS
- Defer object deletion for: 30 days
Transaction logging is running, and the specific test database has the following advanced properties set:
- Domino Attachment and Object Service (ticked)
- Use LZ1 compression for atachments
- Compress Database Design
- Compress Data
I have restarted the server. When I run a compact -c, it compacts the database, but does not reduce the size. I have checked the DB in Windows Explorer (60Gb) and the size is the same pre and post. I have checked the directory (E:\DAOS) and it is 35Gb in size.
When I run the command 'Tell DAOSMgr Status tmp\test.nsf', I get the following response. From looking up on the net, I believe ticket count = 0 means that the db is not really DAOS'ed?
Admin Process: Searching Administration Requests database
DAOSMGR: Status tmptest.nsf started
DAOS database status:
Database: E:\Lotus\Domino\Data\tmp\test.nsf
Database state = Synchronized
Last resynchronized: 03/09/2012 02:49:13 PM
Ticket count: 0
DAOSMGR: Status tmp\test.nsf completed
I have run fixup on the database. When I have tried to run the DAOS estimator it has always crashed. This was a problem with larger databases on earlier versions of domino, but not anymore.
Can anyone tell me why the size has not reduced? Am I missing anything?
Best Answer
I think you have DAOS slightly mixed up. DAOS removes the attachments out of documents and stores them on the server, so if one emails is sent with a large attachment it is not stored in every database, just one file in DAOS.
Here are some links:
http://www-01.ibm.com/support/docview.wss?uid=swg21449358 this is to reduce the number of nlo files.
Also someone on IBM support ask the same question, I would recommend reading it here