Best practices for Backup Exec 2010 Lotus Domino Agent


Best practices for Backup Exec 2010 Lotus Domino Agent

Best practices include tips and recommendations to help you use the Backup Exec 2010 Lotus Domino Agent effectively. For more information about the Lotus Domino Agent, see the Backup Exec 2010 Administrator's Guide.

The following best practices help you use the Lotus Domino Agent effectively:

  • Symantec recommends that you run Domino compact and fixup tools regularily on the Domino databases. Doing so helps reduce the size of backups, while avoiding backup job failures due to corrupt databases.

  • Keep linked databases on one volume. Keeping linked databases on one volume lets Backup Exec sychronize the databases before they are backed up.

  • Back up active databases often. Backing up active databases frequently reduces the amount of effort required to update the databases to the point following the most recent backup.

  • Ensure that the notes.ini,, and .id files are protected and available if a disaster occurs.

  • Do not use the Lotus Notes Client to open a Lotus Domino database for which a backup is running.

  • Enable transaction logging and select the archive logging style to restore the Lotus Domino server to a point in time.

  • Ensure that the transaction log does not reside on the same drive as the Lotus Domino database.

  • Assign a virtual IP address or a virtual name to the Microsoft Cluster Server in which the Lotus Domino database runs. Also, ensure that Remote Agent for Windows Systems is not part of the cluster.

  • Configure the DAOS prune period as recommended in the Lotus Domino documentation. However, Symantec recommends that you do not set the DAOS prune period to a period less than the time between two Domino backups.

  • Install Symantec Backup Exec Remote Agent for Windows Systems on all of the Lotus Domino nodes of a Microsoft Cluster Server.

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.

If you decide to individually restore missing .nlo files, Symantec recommends the following best practices:

  • Always restore the .nlo files to the internal repository of the current DAOS-enabled Domino server.

  • Instead of making random .nlo files selections, select all of them when you make your selections in the restore selections view. Then use the restore option, Skip if file exists. By using the Skip if file exists option, Backup Exec restores only the missing .nlo files.

For more information about the Lotus Domino .nlo files, see the Backup Exec 2010 Administrator's Guide.

Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)