About the Lotus Domino Agent and the Domino Attachment and Object Service (DAOS)

Article:HOWTO23295  |  Created: 2010-01-01  |  Updated: 2011-06-19  |  Article URL http://www.symantec.com/docs/HOWTO23295
Article Type
How To


Environment

Subject


About the Lotus Domino Agent and the Domino Attachment and Object Service (DAOS)

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 <server>.id file.

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.

Note:

Domino uses <server>.id for NLO encryption purposes. If you enable NLO file encryption at the Domino server, the <server>.id file must be backed up.

When you select individual DAOS-enabled databases for backup, the referenced .nlo files for each database are included in the backup job. However, the <server>.id file is excluded.

With incremental backups, only the databases and the .nlo files that are created since the last Full backup of the server are backed up.

Note:

In cases where incremental backup jobs fully back up DAOS-enabled databases, all of the .nlo files that each database references are backed up. This scenario occurs when DAOS-enabled databases use circular logging, or when DAOS-enabled databases are in archive log mode and their DBIID changes.

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.

For information on Domino DAOS catalog resynchronization operations, see your Lotus Domino documentation.


Legacy ID



v26189862_be2010_adm


Article URL http://www.symantec.com/docs/HOWTO23295


Terms of use for this information are found in Legal Notices