Backup of Lotus Domino database with DAOS enabled, fails with error: "0xE0009A91 - 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."

Article:TECH130647  |  Created: 2010-01-28  |  Updated: 2013-02-25  |  Article URL http://www.symantec.com/docs/TECH130647
Article Type
Technical Solution

Product(s)

Subject

Issue



Backup of Lotus Domino version 8.5.1 or later database with DAOS enabled, fails with error: "0xE0009A91 - 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."


Error



0xE0009A91 - 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.

 


Cause



Depending on the Domino server's DAOS settings and workload, Backup Exec may display this error due to a timeout threshold being exceeded while enumerating the DAOS store contents.

 


Solution



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.  
 
On the Domino Server, increase the 'DAOS listnlo timeout' registry key.

1. Click Start | Run | REGEDIT

2. Find and edit this registry key:
 
HKLM | SOFTWARE | Symantec | Backup Exec For Windows | Backup Exec | Engine | Domino | DAOS listnlo timeout

3. Double-Click the registry DWORD key 'DAOS listnlo timeout' and set the decimal value to 600000 or larger value for example 1200000.
*Note - The 600000 decimal entry is a default value in Backup Exec 2012 R2 or later. It is not the maximum limit. You may experience success by increasing the listnlo timeout threshold past 600000 or 1200000.
 

4. Click 'OK'

5. Restart the Backup Exec Remote Agent Service

6. Re-run the Lotus Domino Backup

 
 
Should this fail to resolve the issue, the root cause may be thresholds set too low within the DAOS configuration.
 
For assistance with DAOS configuration, please see the IBM DAOS Best Practices wiki site:

Contact IBM support if further assistance is needed to properly configure DAOS thresholds.
 
NOTE: Increasing the timeout through the 'DAOS listnlo timeout' registry key causes the Domino Agent to use the time you entered to determine the list of NLO references for databases. The Domino Agent determines the NLO references for databases in the shortest amount of time possible, up to the time period that you set. However, during the NLO reference determination operation, it may appear that the job has stopped. It has not. If increasing the timeout value does not fix the issue, please refer to TECH136835 in the Referenced Documents section below.
 
 
Deferred Deletion Interval - This value is set in the DAOS tab of the server doc. This is the amount of time that DAOS waits between when the refcount on an NLO goes to zero, and when the NLO is deleted. The default value is 30 days, but it can be configured by the administrator in the DAOS tab of the server doc. The interval should be coordinated with the server backup interval to ensure that all NLO files participate in at least one backup cycle
 
To check this settings value, please see the notes.ini file:
 
DAOSDeferredDeleteInterval=
 
The value listed is measured in days.
 

 


Supplemental Materials

SourceUMI
ValueV-79-57344-39569

SourceError Code
Value0xE0009A91
Description

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."



Legacy ID



354974


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


Terms of use for this information are found in Legal Notices