Check the bpbkar log from client.
Bpbkar
10:54:05.938: [3508.4052] <4> tar_backup::V_SetupJobData: INF - dwJobData: ffffffff
10:54:05.938: [3508.4052] <4> tar_backup::V_SetupJobData: INF - dwJob: ffffffff
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - backup privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - restore privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - security privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - tcb privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - create token privileges enabled, previous = 0
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - user name: root
10:54:05.953: [3508.4052] <4> dos_backup::V_PreProcessing: INF - no access token: scheduled backup
10:54:05.953: [3508.4052] <2> ov_log::V_GlobalLog: INF - BEDS_Init() Enter InitFlags:0x0
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: C:
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: D:
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Terminal Services
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Microsoft Windows Network
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: VMware Shared Folders
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Web Client Network
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Shadow?Copy?Components
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: System?State
10:54:05.984: [3508.4052] <2> ov_log::V_GlobalLog: INF - DumpDleInfo() DLE Device Name: Active Directory Application Mode
10:54:06.156: [3508.4052] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received
10:54:06.281: [3508.4052] <2> tar_backup_tfi::setupFileDirectives: TAR - backup filename = D:\Program Files\Lotus\Domino\data
10:54:06.281: [3508.1940] <4> tar_base::keepaliveThread: INF - keepalive thread is active with an interval of 60 seconds
10:54:07.297: [3508.4052] <4> UpdatePath(): INF - Path updated with Lotus Program Dir 'D:\Program Files\Lotus\Domino\nserver.exe'
10:54:07.297: [3508.4052] <2> tar_base::V_vTarMsgW: FTL - The NetBackup Extension for Lotus Notes is not properly installed:SetCurrentDirectory (WIN32 267: The directory name is invalid. )
10:54:07.297: [3508.4052] <2> tar_backup_vxbsa::add: INF - called with 'D:\Program Files\Lotus\Domino\data'
10:54:07.297: [3508.4052] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 9: an extension package is needed, but was not installed
10:54:07.297: [3508.4052] <4> backup_create: INF - NetBackup Temp Directory: 'C:\Program Files\Veritas\\NetBackup\Temp'
10:54:07.297: [3508.4052] <4> OVStopCmd: INF - EXIT - status = 0
10:54:07.297: [3508.4052] <2> tar_base::V_Close: closing...
Check some steps
* The most common cause of Status 9 on Lotus Notes backup is incorrectly configuring the INI and PATH information. To add/modify the registry values using REGEDIT32:
1. Click on the Windows Start menu and click Run. In the Run box, type REGEDT32 and press Enter.
2. Select the HKEY_LOCAL_MACHINE key, and navigate the tree and select the SOFTWARE\VERITAS\NetBackup\CurrentVersion\Config key
3. Click on the Config key.
4. Look for a LOTUS_NOTES_PATH value - if it does not exist, from the Edit menu, select Add Value. If it does exist, double-click on it and go to step 7.
5. Set the Value Name to LOTUS_NOTES_PATH.
6. Select REG_SZ for the Data Type, and press OK to add the value.
7. Enter the value data. This is the full directory path to where the nserver.exe file is located. So if, for example, in the environment, the nserver.exe file was located in D:\Lotus\Domino, the value for the LOTUS_NOTES_PATH would be D:\Lotus\Domino.
8. Press OK to accept the value.
9. Repeat steps 4 to 8 for the LOTUS_NOTES_INI value. Please note the value for the LOTUS_NOTES_INI value is the full directory path to the notes.ini file, along with the file name. So if, for example, in your environment, the notes.ini file was located in D:\Lotus\Domino, the value for the LOTUS_NOTES_INI would be D:\Lotus\Domino\notes.ini.
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.
* Look to see if there are multiple copies of the files named js32.dll and nlsccstr.dll available to NetBackup (tm). In some cases, the NetBackup for Lotus Notes agent initiates, using older versions of these files found in the C:\winnt\system32 directory, causing the Status 9 error. By default, these files are not located in C:\winnt\system32 after a base Windows install.
By using the third party utility Dependency Walker (http://www.dependencywalker.com/), Support was able to determine that the nnotes.dll (from Lotus) and the nblotusnotes.dll (from Veritas) files were searching for and using two different versions of the same file names from different locations.
The nnotes.dll file (a Lotus installed binary used by NetBackup during the backup and restore process) was looking for the js32.dll and nlsccstr.dll files, and finding them in the d:\lotus\domino directory. In contrast, the NetBackup nblotusnotes.dll file was looking for them in the c:\winnt\system32 directory. Furthermore, when Dependency Walker was run against the nblotusnotes.dll file, both the js32.dll and nlsccstr.dll files displayed in red, indicating a problem with the relationship between NetBackup and the relative version of these DLL files.
Resolve this by renaming the js32.dll and nlsccstr.dll files in the c:\winnt\system32 directory to js32.old and nlsccstr.old, and then copy js32.dll and nlsccstr.dll from the
:\lotus\domino directory into the C:\winnt\system32 directory.
make clearing the path and ini path in the client's properties
host properties -> client properties -> Windows Client -> Lotus Notes
clear the Lotus Notes Path and Lotus Notes INI Path fields
