Re: Auditing the DAOS directory.

[Walter Scanlan <wscanlan@xxxxxxxxxx>]

Assuming you have daosmgr debug enabled you could use

Tell DAOSMgr DAOSdiag -a <directory or filename> -v


Run this against the mail directory and you will have a list of every NLO 
in use (referenced)...
compare to the directory listing and you have an orphan list..





Of course, you could just resync force and then prune.... which would 
clear any orphaned NLOs if they existed...


Walter Scanlan
Senior Software Engineer
Office: 507-286-6088
Cell: 507-990-4539




From:
rob@xxxxxxxxx
To:
DOMINO400@xxxxxxxxxxxx
Date:
10/15/2010 10:30 AM
Subject:
Auditing the DAOS directory.
Sent by:
domino400-bounces+wscanlan=us.ibm.com@xxxxxxxxxxxx



I have an dpar with 1 mail user (me).  It also has some other test 
databases.  Using Windows Explorer tells me that on a dpar that takes 15.4 

GB that 8.77GB is in DAOS and 3.87 is in logdir.  logdir doesn't contain 
anything older than a month.  DAOS does.  Is there a way to tell if 
anything in the DAOS directory is an orphan?  Like, something which should 

have went to an archive database on another dpar or some such thing?  If I 

know that the DAOS file name is 
96CFB7906A23854F0C755B570472F7703BC4C89D041A56F9.nlo
is there some way to say that belongs to etq/Quality23/MyDatabase.nsf and 
it's document such-and-such?


Rob Berendt