Error backing up Daos files in Lotus Notes with BE 2010

You may also refer http://support.veritas.com/docs/357175 but I am not sure if you would be able to access this document or not. So here is the information:



During backups and restores of Lotus Domino databases that include a large number of NLO references, the backup jobs or restore jobs fail. The jobs fail because the Domino Agent terminates the jobs early when attempting to determine all of the NLO references to back up or restore.

 

Because the determination of the NLO references can take time due to slow responses from Domino servers, the Domino Agent's default LISTNLO timeout value (per database) of one minute in Backup Exec 2010 may not be sufficient. If the Domino Agent attempts to determine the NLO references after the LISTNLO timeout period has elapsed, the jobs fail.

 

NOTE: When the timeout period elapses before the NLO reference determination completes, the following error messages appear during the respective backup and restore jobs:

 

• Backup Exec cannot determine the NLO files that one or more Lotus Domino databases refer to. On the Lotus Domino server, resync the DAOS catalog and then try the operation again.

• The Lotus Domino server failed to provide a list of the NLO files that are required by the restored and recovered databases. Determine which NLO files are missing, and then individually restore them.

 

For example, a Domino database backup job that includes 200,000 associated NLO references will fail because on a busy Domino server, the LISTNLO timeout period may prove inadequate to enable the Domino Agent to successfully determine the NLO references to back up. In this case, a LISTNLO timeout value greater than 30 minutes may be sufficient. However in some cases, the aggregate of time required to determine the NLO references for all databases in a selection list may be enormous. As a result, NLO reference determination may take many hours, which may not be desirable.

 

Solution:

 

With Backup Exec 2010 R2, the way the Domino Agent calls LISTNLO can be controlled by changing the values in a new registry key called "DAOS listnlo mode."

 

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

 

HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Domino\DAOS listnlo mode

 

The new registry key offers four values from which to choose. They include the following:

 

Value: 0

Description: Default value.

 

Using this value does not change the Domino Agent's default behavior. Backup jobs continue to function as normal. The NLO references are determined for each database selected for backup. However, large numbers of NLO references can cause the backup jobs to fail due to the LISTNLO timeout period being exceeded. This value should be used when a small number of NLO references are associated with the Domino databases. Use this value if each database is expected to have less than 30,000 NLO references. Note that this number can be higher for full Domino server backup jobs as the Domino Agent can optimize full Domino server backups. It cannot, however, optimize partial Domino server backups.

 

Restore jobs run normally. The required NLO files are restored even with partial Domino server restore job. Any missing NLO reference files that cannot be recovered in a Domino recovery are reported for each Domino database that is restored. Keep in mind that by using the value of 0, a large numbers of NLO references from a restore attempt can cause the restore job to fail due to the default LISTNLO Timeout period elapsing.

 

Value:  1

Description:  No LISTNLO during backups

 

Using this value forces the Domino Agent not to call LISTNLO during backups. Although the NLO files are backed up, no NLO references are backed up. When this value is set, LISTNLO is never called for either full or partial Domino server backup jobs. As a result, NLO references do not need to be determined for the Domino databases. Additionally, partial Domino server backup jobs result in all NLO reference files in DAOS folder being backed up since NLO references for databases selected for backup have not been determined. Sometimes, restores from such backup sets also shows changed behavior, especially with partial Domino server restores. This occurs due to the non-determination of NLO references at backup time. Not all NLO files referenced by databases may be restored; however the Domino Agent will generate a warning and report the missing NLO files. Using this value does not change the Domino Agent's default behavior for restore jobs that involve backup sets that were created using the value of 0 or 2 with this registry key.

 

Value: 2

Description:  No LISTNLO during restore

 

Using this value does not change the Domino Agent's default behavior. Backup jobs continue to function as normal. The NLO references are determined for each database selected for backup. However, large numbers of NLO references can cause the backup jobs to fail due to the LISTNLO timeout period being exceeded. This value should be used when a small number of NLO references are associated with the Domino databases. Use this value if each database is expected to have less than 30,000 NLO references. Note that this number can be higher for full Domino server backup jobs as the Domino Agent can optimize full Domino server backups. It cannot however, optimize partial Domino server backups.

 

Full and partial Domino server restore jobs run normally. However, LISTNLO is not called to determine missing NLO references; hence missing NLO references are not reported for any Domino database that is restored. Instead, the Domino Agent reports an exception with the following message: "The Lotus Domino server failed to provide a list of the NLO files that are required by the restored and recovered databases. Determine which NLO files are missing, and then individually restore them."

 

Value: 3

Description:  No LISTNLO during backup or restore

 

Using this value forces the Domino Agent not to call LISTNLO during backup. When this value is set, LISTNLO is not called during full or partial Domino server backup jobs. As a result, NLO references are not determined for the Domino databases. Additionally, partial Domino server backup jobs result in all NLO files in DAOS folder being backed up since NLO references for databases selected for backup have not been determined. However, with incremental backups, only the NLO files that are created after the last full backup job are backed up.

 

Sometimes, restores from such backup sets also shows changed behavior, especially with partial Domino server restores. This occurs due to the non- determination of NLO references at backup time. Not all NLO files referenced by databases may be restored; however the Domino Agent will generate a warning and report the missing NLO files.

 

Full and partial Domino server restore jobs run normally. However, LISTNLO is not called to determine missing NLO references. As a result, they are not reported for any Domino database that is restored. Instead, the Domino Agent reports an exception with the following message:

 

"The Lotus Domino server failed to provide a list of the NLO files that are required by the restored and recovered databases. Determine which NLO files are missing, and then individually restore them."

 

Symantec recommends the following best practices when considering changing the values for the DAOS listnlo mode registry key:

 

NOTE: This information applies to Backup Exec 2010 after applying hotfix 351400 because this issue has been resolved with Hotfix 351400 for Backup Exec 2010