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
Domino 12.0.0 already has DAOS restore integration for restoring a database.
Domino 12.0.1 added command line restore integration for single databases, directories and the whole server.
load restore daos xyz.nsf
will restore missing DAOS objects, if you provided the right integration script for your backup vendor.
There are very rare cases when you need a DAOS restore.
The NLO retention time should be always set higher than the backup retention time. So in theory you should not need NLO restores often.
It would be only required when restoring very old backups. Which is not what Domino backup is designed for due to the nature of integration options.
Still it would work if you keep both backups for the same retention time.
Backup of DAOS isn't something Domino should need to take care of.
It's a simple incremental forever file backup job, which is independend from a Domino NSF backup. It just should be scheduled in similar inteval.
Building an integration for backup is not needed from my experience in the field.
[ Daniel Nashed / https://blog.nashcom.de ]
The integration of DAOS in the HCL solution would significantly simplify the backup/restore process and make it more reliable.