Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
the DAOSMgr can list NLOs missing and existing NLO per database.
If you don't specify the "missing" keyword it will show all NLOs.
There are debugging options available to see more NLO information.
The main questions here is -- as Thomas says -- what type of troubleshooting you want to do.
With Domino 12.0 there is restore integration for Domino backup.
In Domino 12.0.1 3rd party restore is added to allow to integrate with your exisitng backup solution which is leveraging the Backup C-API and you can use the UI components of the Domino backup&restore to restore databases including an option to integrate NLO restore.
In addition with 12.0.1 there is a separate NLO restore per database, directory and also the whole server.
The restore always works in the same way:
1. Check the number of missing NLOs
2. Provide the list to the restore application and get them restored
3. Check again for missing NLOs
Most of the times this is what an admin might want. But you can also list existing NLOs as explained above.
And there is also a diagnostic command that dumps a lot of information.
I don't see any documentation for the command or the notes.ini
But you find it in a couple of business partner blogs.
Here are the details how to run it:
set config DEBUG_DAOS_DIAGNOSTICS=1
tell daosmgr LISTNLO MAP -V mail/nsh.nsf
This shows a ton of information.
Have a look at Ulrich's blog --> https://www.eknori.de/2016-03-08/daos-find-a-note-for-a-missing-nlo-file/
This should be added to documentation, but the feature is there.
Daniel Nashed
[https://blog.nashcom.de]