BUG REPORT: After installing the NetBackup 6.5.2 release update, there may be a delay before User and Manual Immediate jobs start.

Problem

BUG REPORT: After installing the NetBackup 6.5.2 release update, there may be a delay before User and Manual Immediate jobs start.

Solution

Bug: 1375497

Detail/Symptoms:
After installing the NetBackup 6.5.2 release update, there may be a delay before User and Manual Immediate jobs start.

Master Server Log Files:
nbpem:
At 6.5.2 nbpem initialization will begin to accept User and Manual Immediate requests from bprd after the nbpem PemNameMgr subsystem performs host name lookups and comparisons on each client name referenced in a backup policy and in the clientDB (/usr/openv/netbackup/db/client).

Here we see nbpem starting:
08/05/08 00:00:00.005 [Application] NB 51216 137 PID:4240 TID:1 File ID:116 [No context] [Info] V-137-20         Now Running as Daemon: nbpem

Here we see nbpem opening the gate to receive User and Manual Immediate requests from bprd after approximately 15 minutes:
08/05/08 00:15:00.000 [Diagnostic] NB 51216 nbpem 116 PID:4240 TID:12 File ID:116 [No context] 1 V-116-260 [BprdComm::advertise] interface for BPRD adveritsed

Note: The misspelled "adveritsed" above is as it appears in the log.

With DebugLevel for nbpem (OID 116) at 4 or higher, delays may be observed between iterations of this message while the nbpem PemNameMgr subsystem performs vnet host name lookups and comparisons on each client name referenced in a backup policy and in the clientDB (/usr/openv/netbackup/db/client):
08/05/08 00:00:01.629 [Debug] NB 51216 nbpem 116 PID:4240 TID:4 File ID:116 [No context] 4 [PemNameMgr::getHostname] (ID:017D7880) adding new hostname alias "clientname"(PemNameMgr.cpp:639)

With DebugLevel for libraries (OID 137) at 1 or higher, references to hostnames for decommissioned or unresolvable client names can be seen:
08/05/08 00:00:00.709 [Debug] NB 51216 137 PID:4240 TID:4380 File ID:116 [No context] 1 [vnet_cached_gethostbyname] vnet_hosts.c.365: gethostbyname failed: bad_clientname

Workaround:
  • Given time, nbpem PemNameMgr subsystem initialization will complete.  Subsequent job scheduling will proceed normally.
  • To boost performance, remove references to clients with host names that cannot be resolved from backup policies and the clientDB.

Note:
To list the contents of the clientDB, use the following command:
# /usr/openv/netbackup/bin/admincmd/bpclient -All

To remove a clientDB entry:
# /usr/openv/netbackup/bin/admincmd/bpclient -client <client_name> -delete

If this workaround is not adequate, please contact Symantec Technical Support for a code based workaround allowing nbpem to receive User and Manual Immediate job requests from bprd while PemNameMgr initialization completes asynchronously.

ETA of Fix:
The formal resolution to this issue (Etrack 1375497) 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)