Good suggestions...more
What John said... I'd stick to a
larger minimum participation size (1Mb is a good start) than his examples,
but the rest is dead on.
plus...
- Is everything DAOS-enabled? Double
check that all files on both servers DAOS enabled (or not) as you expect
them to be.
- Storage format - DAOS gets the data
*after* all NSF-level encoding/compression/encryption options have been
applied, and considers the uniqueness based on that stream of bytes. Differences
in encoding (MIME, native) and compression (none, huffman, lz1) will cause
different NLO files to be created. Encrypted data (NSF-level, not
DAOS encryption) can cause multiple unique NLO files to be created depending
on the way they were created.
- Mail routing - it's possible for 'transient'
objects to appear in the DAOS repository as a side effect of mail routing.
These are 'just passing through' attachments that are stored for
mail.box, and were deleted after being sent on to somewhere else. The
DAOS deferred deletion interval will retain these until they are pruned.
- IMAP/POP and MIME - If you have mail
clients polling the server, MIME formats the messages for the client and
stores them temporarily in an attachment in the user's mailfile. These
can end up being stored in DAOS, and can build up. Please see PPOR8XZLPN
(included in 9.x and newer) and enable DAOS_AVOID_MIME=1 if this is the
case
-