Expanding Domino resources in backup selections fails with a Pop-up error "An error was encountered while attempting to browse the contents of Databases on SERVERNAME|C:"
| Article:TECH147999 | | | Created: 2011-01-12 | | | Updated: 2012-07-16 | | | Article URL http://www.symantec.com/docs/TECH147999 |
Problem
When attempting to expand one of the volumes displayed beneath the Lotus icon in backup selections for a Domino 8.5.x server an error popup is received:
An error was encountered while attempting to browse the contents of Databases on SERVERNAME|C:.
An error occurred during backup. See the job log for details.
Error
"An error was encountered while attempting to browse the contents of Databases"
"An error occurred while attempting to browse the contents of databases. Connection with server failed. Hit <F5> to retry"
Environment
Domino Server 8.5.X
Cause
DAOS is Domino attachment and object service. This is a file space saving method that Domino server uses to store attachment data common (identical) among databases. This data is saved in *.NLO files separate from the Domino databases and the Backup Exec Domino agent must have a way to find it for backup and restore. In this condition, when DAOS is configured within Domino server, the location is not specified which causes the Backup Exec Lotus Domino agent error in attempting to locate the DAOS path.
Debugging the Lotus Domino server will show the following in the beremote.log:
54:00 [fsys\shared] - Attach to F:
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: CLNPartitions::InitLNInfo
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::InitiatePartition
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: NSFGetTransLogStyle Call.
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::InitiatePartition - Partition 0: - Archive logging
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: OSGetEnvironmentString Call.
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: OSGetEnvironmentString Call.
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::InitiatePartition - Partition 0: DAOS Serviced []
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: OSGetEnvironmentString Call.
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: OSGetEnvironmentString Call.
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: CLNPartitions::ReleaseInfo
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::InitLNInfo - Exiting[-536836936]
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::CloseFKFS
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent: CLNPartitions::ReleaseInfo
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::AttachingToLNVolume - Exiting[-536836936]
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNPartitions::CloseFKFS
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\shared] - Detach from F:
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [fsys\notes2] - Notes Agent:CLNFileSystem::AttachToDLE - Exiting[-536836936]
BEREMOTE: [03.24.11 15:54:00] [0000] 03/24/11 15:54:00 [ndmp\ndmpsrvr] - DSEnumerator failed with -536836936: An error occurred during backup. See the job log for details.
*In this particular instance, F: was the volume where the Lotus Domino databases resided.*
Solution
Workaround:
Review the NOTES.INI file from the Domino server to verify whether a path to DAOS has been configured. If an entry for "DAOSBasePath" is not found in NOTES.INI, then DAOS will need to be configured with a location path. It is advisable to place entry for "DAOSBasePath" from Notes Administration console instead of directly editing notes.ini file. The reason for not editing notes.ini file is because its overwritten at specific intervals by Notes Administration console.
Note: Also it is advisable to remove any trailing backslash. Please see : http://www.symantec.com/docs/TECH165823
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
There are no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. However, the issue is currently scheduled to be addressed in the next major revision of the product. Please be sure to refer back to this document periodically as any changes to the status of the defect will be reflected here. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.
Please contact your Symantec Sales representative or the Symantec Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue. For information on how to contact Symantec Sales, please see http://www.symantec.com
|
|
| Source | ETrack |
| Value | 2240588 |
| Description | LOTUS: Default DAOS path should be used if daosbasepath is not defined in notes.ini. |
Related Articles
Article URL http://www.symantec.com/docs/TECH147999
Terms of use for this information are found in Legal Notices
Thank you.