BUG REPORT: After applying the NetBackup 6.5.2 release update, Hot Catalog Backups fail with NetBackup status codes 42 (network read failed) and 2 (none of the requested files were backed up) when the Critical Policies list contains entries.

Problem

BUG REPORT: After applying the NetBackup 6.5.2 release update, Hot Catalog Backups fail with NetBackup status codes 42 (network read failed) and 2 (none of the requested files were backed up) when the Critical Policies list contains entries.

Solution

Bug: 1295660 6.5.2 Hot Catalog Backup fails Status 42 / 2 when Critical Policies list contains entries due to bpdbm.exe fault.

Detail/Symptoms:
After applying the 6.5.2 release update, NBU-Catalog policies (also known as Hot Catalog Backup policies) start to fail with status code 42 (for the child) and status 2 (for the parent) reported in the Activity Monitor.  

If the Critical Policies list (within policy configuration Disaster Recovery tab) has entries in it, the Hot Catalog Backup will fail as described.  (Figure 1)
 

This issue has been seen on Windows masters.

Log Files:
The bpbkar log will contain an entry similar to the following:
10:59:39.578 AM: [5312.5892] <16> dtcp_read: TCP - failure: recv socket (520) (TCP 10054: Connection reset by peer)

The bpbrm log will contain entries similar to the following:
11:02:54.062 [3804.900] <2> get_long: (1) cannot read (byte 1) from network: An existing connection was forcibly closed by the remote host.
11:02:54.062 [3804.900] <2> db_getdata: get_string() failed: An existing connection was forcibly closed by the remote host.  (10054) network read error (-3)
11:02:54.062 [3804.900] <2> db_end_sts: no DONE from db_getreply(): network read failed
11:02:54.062 [3804.900] <2> db_IMAGE: db_end_sts() failed: network read failed
11:02:54.062 [3804.900] <16> bpbrm main: db_IMAGE failed: network read failed (42)

The bpdbm log will contain an entry similar to the following:
11:02:55.593 [3872.3876] <16> do_online_nbdb_backup: Error backing up files in E:\Program Files\VERITAS\NetBackupDB\staging

Additionally, a bpdbm error may be reported in the Application Event log:
6/17/2008 10:57:53 AM Application Error Error (100) 1000 N/A <serverName> Faulting application bpdbm.exe, version 6.5.2008.522, faulting module libVdb.dll, version 6.5.2008.522, fault address 0x00027d00.

Workaround:
The workaround for this issue is to remove all entries from the Critical Policies list within the Hot Catalog Policy.

If the workaround noted is not feasible, please apply the appropriate release update to resolve this issue.

ETA of Fix:
The formal resolution to this issue (Etrack 1295660) is included in the following patch release:
  • NetBackup 6.5 Release Update 3 (6.5.3)
This release is available at the support web site at:
 http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143

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)