Lotus Domino 8.5 incorporates the Domino Attachment and Object Service (DAOS). DAOS-enabled databases (DAOS databases) save significant hard drive space by sharing data between applications on a server. DAOS databases do not save separate copies of every document attachment. Instead, DAOS databases save a single copy of a file attachment to an internal repository. The databases then create and save reference pointers to the stored file attachments.
File attachments are saved to the internal repository with the .nlo file extension. During a full backup of the entire Lotus Domino server, Backup Exec backs up all .nlo files, along with the Domino
Backup Exec adds one container per partition under Lotus Domino Databases called Domino Attachment and Object Service in the restore selections view. All backed up DAOS NLO files reside in backup sets under Domino Attachment and Object Service. In addition, all backed up <server>.id files reside in the Databases container under Lotus Domino Databases.
During a full DAOS-enabled Domino database restore, all database data, .nlo files, and the
<server>.id file are restored. When you restore individual DAOS-enabled databases, Backup Exec restores all database data, including the .nlo files. However, Backup Exec does not restore any .nlo files that match .nlo files in the internal repository. After the DAOS-enabled databases are restored, Backup Exec resynchronizes the Domino DAOS catalog.
During a point-in-time restore of a DAOS-enabled database, some required .nlo files may not be generated when the archive transaction logs are replayed. When this condition occurs, Backup Exec reports the names of the missing .nlo files. You can individually restore the missing .nlo files and then start a Domino DAOS catalog resynchronization operation at the Domino server.