Domino Database(s) get excluded from backup view without any warning if the Database(s) added in the registry EXCLUDED FILE LIST contains the similar alphabetical string with it

Problem

Domino Database(s) get excluded from backup view without any warning if the Database(s) added in the registry EXCLUDED FILE LIST contains the similar alphabetical string with it

Solution

Introduction:
Domino Database(s) may get excluded from the backup view, without any warning and hence is not available for backup, if a database with the similar alphabetical string has been added in the registry value EXCLUDED FILE LIST.

The registry 'Excluded File List' is located under HKLM/Software/Symantec/Backup Exec for Windows/Backup Exec/Engine/Domino. By default this registry contains the database DBDIRMAN.NSF. If a database MAN.NSF exists on the Domino server, it will be no longer be visible in Lotus Domino backup selection and hence would not be available for backups as the name man.nsf is a subset of the name dbdirman.nsf.

Similarly if Domino Databases "BRYAN.NSF" and "RYAN.NSF" exist on the Domino Server and the database BRYAN.NSF has been added in the registry 'Excluded File List' then the database RYAN.NSF will no longer be seen in Lotus Domino backup selections.  

How to determine if affected:
The issue outlined in this article only occurs if:
 

  • Backup Exec 2010 is installed.
  • The registry value 'EXCLUDED FILE LIST' contains any non-blank value.

    Determining Your Product Version:
    The installed version of Backup Exec can be verified by selecting the "About Backup Exec" option from the Help menu.

    Workaround:
    Remove any exclusions added in the Domino "Excluded File List" registry key value that can possibly cause other valid databases to be excluded from the backup selection screen.

    Formal Resolution:
    This issue has been resolved in Backup Exec 2010 Hotfix 351870
    http://support.veritas.com/docs/351870

    Best Practices:
    Symantec strongly recommends the following best practices:
    1. Always perform a full backup prior to and after any changes to your environment.
    2. Always ensure that your environment is running the latest version and patch level.
    3. Perform periodic "test" restores.
    4. Subscribe to technical articles.
     

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

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

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

No
Yes

How can we make this article more helpful?

Email Address (Optional)