How to determine whether or not a nlo is really active

I have some rather dated nlo files. I ran:

tell daosmgr resync force

tell daosmgr prune 0

but if I have a file named:

E8DA75C5ABE6119F8B879D6D8D2505E9370F084212C0E186.nlo

in DAOS/0001

and I have no clue what nsf(s) it came from how do I determine that?

Subject: By design it’s transparent…

If you want you could probably bring Domino down and rename the .nlo in question to .sav and run

daosmgr resync force

standalone and I’m pretty sure it would complain in the console log about the missing .nlo file… Then you could put it back when you were done…

I think it’s safe to say that the prune 0 operation you mentioned got rid of all .nlo files that were not active anymore…

Subject: Using the listnlo parameter

You can go the opposite way. This need some handwork and provides only a snapshot, but it works.

  • Create a batchfile with one entry for every DAOS enabled database:
    “C:\Program Files\IBM\Domino\nserver.exe” -c “tell daosmgr listnlo -o output_mailfile1.txt ALL mail/mailfile1.nsf”
    “C:\Program Files\IBM\Domino\nserver.exe” -c “tell daosmgr listnlo -o output_mailfile2.txt ALL mail/mailfile2.nsf”

  • Run batch

  • Do a text search for the required nlo file over all the created output_*.txt files

Subject: re How to determine whether or not a nlo is really active

FYI …
NLO’s are cleaned up (deleted) by the DAOS Prune process that is scheduled to run nightly at 2:00 AM. NLO’s are only removed when the DAOS catalog is in a ‘Synchronized’ state, the NLO refcount is zero, and the NLO was marked deleted longer than the prune interval ago…

For listing which .nlo’s are used for a specific database using the following command:

tell daosmgr listnlo -o dbname all dbname.nsf

Regards
TomOC.

Subject: How to determine whether or not a nlo is really active

I guess I can see where there may be some possible security ramifications of not exposing whom has such large attachments but I’d also like the ability, as an administrator, if I need to start restricting the size of attachments who am I most likely to start affecting. And other legitimate administrator concerns. Perhaps “leaning” on some people as to whether or not they need such stuff.