Catalog backup completes with status 1 and a WIN32 error on .lock files after the upgrade of Windows primary to 10.0 /10.0.0.1

Problem

Catalog backup is completing as partially successful with status 1, and detailed status shows there is a failure reading the file: C:\Program Files\Veritas\NetBackup\var\hostdb\hostdbcache.xxxxxxxxx.lock WIN32 33: The process cannot access the file because another process has locked a portion of the file. 

This issue only appears after upgrading  a Windows master server to:

• NBU 10
• NBU 10.0.0.1

Error Message

Job details:

Apr 22, 2022 7:50:53 AM - Error bpbrm (pid=64323) from client xxxxxxx: ERR - failure reading file: C:\Program Files\Veritas\NetBackup\var\hostdb\hostdbcache.xxxxxxxxx.lock (WIN32 33: The process cannot access the file because another process has locked a portion of the file. )

Bpbkar log is clearly showing that it is not  able to read hostdbcache.lock file :-

BPBKAR log location on master server

Windows: install_path\NetBackup\logs\bpbkar

17:34:25.334 [8760.8700] <4> tar_backup_tfi::backup_arg_state: INF - V_MODE_BACKUP:No need to do the estimate.  Just continue the backup with the next file
17:34:25.334 [8760.8700] <4> V_CatBackupWin::V_NextCatBackupDirective: INF - Catalog backup: D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock
17:34:25.334 [8760.8700] <4> tar_backup_tfi::backup_arg_state: INF - remember start error count: 0
17:34:25.334 [8760.8700] <4> tar_backup_tfi::backup_arg_state: INF - remember start fatal count: 0
17:34:25.334 [8760.8700] <2> tar_backup_tfi::backup_arg_state: Is ALL_LOCAL_DRIVE Backup  = 0
17:34:25.334 [8760.8700] <4> dos_backup::tfs_scanstart: INF - starting scan for file directive:<D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock>
17:34:25.334 [8760.8700] <4> dos_backup::tfs_scanstart: INF - starting scan using name:<D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock>
17:34:25.334 [8760.8700] <4> dos_backup::tfs_scanstart: INF - in 'backup' mode
17:34:25.334 [8760.8700] <4> dos_backup::tfs_startdir: INF - volume guid:<\\?\Volume{60fa285f-0000-0000-0000-000014000000}\>
17:34:25.334 [8760.8700] <4> dos_backup::tfs_startdir: INF - volume mount point:<D:\>
17:34:25.334 [8760.8700] <4> dos_backup::tfs_network_drive_check: DAT - GetDriveType(D:\) returned 3
17:34:25.334 [8760.8700] <4> dos_backup::_mod_include: INF - <D:\Program Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock>:detected
modification. It will be backed up
17:34:25.334 [8760.8700] <2> tar_backup_tfi::backup_startfile_state: TAR - Backup: D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock
17:34:25.334 [8760.8700] <4> folder_access::V_OpenForRead: INF - non-DFSR file name (\\?\D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock)
17:34:25.365 [8760.8700] <4> dos_backup::tfs_readopen: INF - NT Security information obtained for: 'D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock'
17:34:25.365 [8760.8700] <4> tar_base::V_vTarMsgW: INF - tar message received from dos_backup::tfs_readdata
17:34:25.365 [8760.8700] <2> tar_base::V_vTarMsgW: ERR - failure reading file: D:\Program Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock
(WIN32 33: The process cannot access the file because another process has locked a portion of the file. )
17:34:25.365 [8760.8700] <2> dtcp_write: TCP - success: send socket (680), 214 of 214 bytes
17:34:25.365 [8760.8700] <4> dos_backup::V_AddToExcludeAfterList: INF - file will be skipped during cleanup processing:<D:\Program
Files\Veritas\NetBackup\var\hostdbcache.xxxxxx.xxxxxxx.xxx.lock>
17:34:25.365 [8760.8700] <4> dos_backup::tfs_scannext: INF - no more path list entries
17:34:25.365 [8760.8700] <4> tar_backup::backup_endarg_state: INF - finish error count: 1
17:34:25.365 [8760.8700] <4> tar_backup::backup_endarg_state: INF - finish fatal count: 0

Cause

The nbhostdbcmd command is putting an unnecessary lock at the hostdbcache.lock file during the catalog backup, causing the error above.

Solution

 This issue does not occur in NetBackup 10.1 and higher versions.

An EEB binary is available to address this issue in NetBackup 10.0 and 10.0.0.1, please contact technical support to obtain this hotfix:

 NetBackup 10:         Etrack 4072819

Netbackup 10.0.0.1: Etrack 4090050

The EEB needs to be installed on the affected master server. Once the EEB has been installed, run the catalog backup again.

Please contact Veritas Technical Support to obtain this fix.Please note that Veritas Technologies LLC reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Veritas’ 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 Veritas Sales representative or the Veritas Sales group for upgrade information including upgrade eligibility to the release containing the resolution for this issue.