Within our test environment I’ve set up a number of test mail accounts and enabled Quota enforcement. I’ve set the Quota enforcement value (located on the Transaction log tab) to use the setting “Check Space used in File When Adding a Note” so that users should they exceed their quota can delete documents and start working again (as opposed to waiting for a compaction) This all works fine until I enable DAOS on the database. After sending a number of test messages the new graphical quota plug-in (within the Notes client) displays the physical space of the file and not logical size of the mail file. If you select the DB properties it says that the database is 153Mb in size but the quota plugin says its 43Mb, If however I change the quota enforcement values to be “Check file size when extending the file” or “Check file size when adding a note” then the quota plug-in starts reporting database size based upon logical size e.g. 153Mb,
From all of the information I’ve read relating to DAOS it seems to indicate that for consistency purposes the database size will always reflect the logical databases size (which is physical + DAOS data).
Can someone please confirm if the Quota UI is working as designed (to reflect physical DB size as opposed to logical) or indeed it is a bug. Any feedback welcomed.