Duplications fail with Status 191/44/213 after upgrading a Windows Master Server to 7.0.1. Image Cleanup completes (Status 0) but is not cleaning images.
bpdbm log will display the following sequence of messages:
12:47:28.863 [10364.10564] <4> bpdbm: Call to OpenProcess failed.
12:47:28.863 [10364.10564] <2> logconnections: BPDBM ACCEPT FROM
169.254.250.221.58786 TO 169.254.250.221.1556 fd = 844
12:47:28.863 [10364.10564] <2> image_db: Q_IMAGE_FORK_LOCK_DBM
12:47:28.878 [10364.10564] <4> fork_lock_dbm: Starting to monitor copy
12:47:28.878 [10364.10564] <4> IsParentBpdbmDead: Unable to obtain handle to
12:47:28.894 [10364.10564] <8> fork_lock_dbm: Finished monitoring copy because
parent bpdbm process died.
12:47:28.894 [10364.10564] <2> process_request: request complete: exit status
150 termination requested by administrator; query type: 110
A hotfix for this issue for NetBackup 7.0.1 can be found attached to this document and should be installed on the NetBackup master server.
The formal resolution for this issue (Etrack 2107011) is included in the following release:
- NetBackup Enterprise Server 7.1.
This release is now available.
Note: This TechNote contains legacy information only. This hotfix is no longer publicly available, as its fixes are included in a more recent NetBackup release. If this issue is experienced, the supported resolution is to upgrade NetBackup to the latest version and apply the latest maintenance release.
Symantec Bug ID: 2106924
Installation Location: Master Server
Please follow the EEB Installer instructions available on http://support.veritas.com/docs/313221
Please choose the appropriate platform after download:
eebinstaller.2106924.5.x86.exe Windows x86 Installation
eebinstaller.2106924.5.AMD64.exe Windows x64 Installation
2549364670 1749504 AMD64/bpdbm.exe
1182812259 1253376 x86/bpdbm.exe
Recommended service state:
Stop NetBackup Services on the Master server before applying.