Best practices for the Backup Exec 2014 Agent for Lotus Domino

Article:HOWTO74433  |  Created: 2012-03-07  |  Updated: 2014-07-15  |  Article URL http://www.symantec.com/docs/HOWTO74433
Article Type
How To


Subject


Best practices for the Backup Exec 2014 Agent for Lotus Domino

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

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

  • Symantec recommends that you run Domino compact and fix up tools regularly 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. This lets Backup Exec synchronize the databases before they are backed up.

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

  • Ensure that the notes.ini, cert.id, and <server>.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.

  • 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 gap between two Domino backups.

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

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

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 re-synchronization 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 2014 Administrator's Guide.


Legacy ID



v70444687_v72686290


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


Terms of use for this information are found in Legal Notices