After applying the NetBackup 188.8.131.52 maintenance release to a master server or applying the 2.5.2 patch to a NetBackup 5200/5220 Appliance used as a master server, the activity monitor is reporting inconsistent information on job status for some jobs. The main job status or job overview window may indicate that a job is active or queued; however, the Detailed Status tab in the Job Details show logs indicating that the job has completed. Additionally, some jobs may not appear in OpsCenter.
This issue occurs regardless of the operating system or version of the client and is seen when a file path on the client is encountered which contains an apostrophe ('). Timing is an additional contributing element to the experience of this issue - when an affected file path is encountered, the issue may be seen - but it also may not.
In addition, encountering an affected file path may lead to the unexpected result of a different job displaying inconsistent information, including jobs which may not include an affected file path.
Additionally, if services are restarted, affected jobs may appear to fail with a report of status code 50 (client process aborted).
This figure illustrates an example of a completed job in the logs of the Detailed Status while, at the same time, the Activity Monitor row for this job indicates it is still active (it is not):
The following figures demonstrate how the Activity Monitor may incorrectly display the status of jobs which have successfully completed.
In this figure, all of the jobs have completed, but some jobs are still showing Active under Job State, with a corresponding icon:
This figure demonstrates the result of stopping and restarting NetBackup - the previously "active" jobs now show a failure icon, status code 50 and Waiting for Retry under Job State. Again, all of the jobs in this graphic completed successfully and checking individual jobs' Job Details will show success and a status code 0.
Finally, in this figure, a job displaying a Queued Job State in the Activity Monitor is compared with its Job Details, which - once again - show that the job has actually completed and succeeded (note status code 0 entries).
A "status 2007079" can be found in the bpjobd log:
At VERBOSE level 0:
10:03:54.428 [5288.5340] <16> JobDBM::update: unable to update job record(s), status 2007079
10:03:54.428 [5288.5340] <16> ProviderTask::processRequest: unable to update job ID 1632354
10:03:54.428 [5288.5340] <4> ProviderTask::svc: closing PROVIDER connection (socket 1200) from host NBU-MASTER.example.org, pid 12628
At VERBOSE level 5, the affected file path can be found just before the status 2007079 is reported:
12:27:42.571 [2056.1828] <2> parse_packet: Index 60 Field m_nCompletion Value <100>
12:27:42.571 [2056.1828] <2> DbConnection::Execute: SQL - retval=DB_ERROR_SQLSyntaxErrorOrAccessViolation(2007079) retdal=-1 native=<0> sqlerror=<[Sybase][ODBC Driver]Syntax error or access violation> sqlstate=<42000>
12:27:42.571 [2056.1828] <2> DbConnection::Execute: stmt=<UPDATE JOBD_MAIN.JOBD_Job SET PercentComplete = 100, CurrentFile ='/C/nntest/rrrdir/quote'ndir/000 directory space/000/494.txt', BitField = 0xa5ef5f847d0c027906000000 WHERE (MasterServerKey = 1000002) AND JobId = 6111>
12:27:42.571 [2056.1828] <16> JobDBM::update: unable to update job record(s), status 2007079
12:27:42.571 [2056.1828] <16> ProviderTask::processRequest: unable to update job ID 6111
The formal resolution for this issue (Etrack 3106821) is included in the following release(s):
- NetBackup 7.5 Maintenance Release 6 (184.108.40.206)
- NetBackup 5200/5220 Appliances 2.5.3
These releases are now available - please access the Related Articles below for more information.
It has been observed that when this issue occurs, the detailed status of the job will display the correct status. However, it is recommended to apply a fix to ensure the issue is resolved. Please apply the hotfix attached to this document.
Note: This hotfix is no longer publicly available, as all of its fixes are included in the NetBackup 220.127.116.11 Maintenance Release. If any of these issues are experienced in a NetBackup 7.5.0.x environment, the supported resolution is to apply the latest maintenance release.
Symantec Bug ID: ET 3106719
Installation Location: master server
Please follow the EEB Installer instructions available on http://www.symantec.com/docs/TECH64620
Please choose the appropriate platform after download:
eebinstaller.3106719.1.hpia64 HP-UX Itanium Installation
eebinstaller.3106719.1.linuxR_x86 RedHat x64 Installation
eebinstaller.3106719.1.linuxS_x86 Suse x64 Installation
eebinstaller.3106719.1.rs6000 AIX Installation
eebinstaller.3106719.1.solaris Solaris SPARC Installation
eebinstaller.3106719.1.solaris_x86 Solarix x64 Installation
eebinstaller.3106719.1.AMD64.exe Windows x64 Installation
eebinstaller.3106719.1.x86.exe Windows x86 Installation
2605627361 9644952 hpia64/bpjobd
1860491864 2191333 linuxR_x86/bpjobd
2453072404 2197473 linuxS_x86/bpjobd
1583284180 5290415 rs6000/bpjobd
3160777503 3137544 solaris/bpjobd
374119478 3558256 solaris_x86/bpjobd
173605094 647680 AMD64/bpjobd.exe
3944267561 608256 x86/bpjobd.exe
Recommended service state: Shut down services on the master server before applying
NetBackup 5200/5220 Appliances:
Note: This hotfix is no longer publicly available, as all of its fixes are included in the NetBackup Appliances 2.5.3 Release Update. If any of these issues are experienced on a NetBackup Appliances, the supported resolution is to apply the latest release update.
This issue only affects NetBackup 18.104.22.168 master servers, including NetBackup 5200/5220 Appliances in the master server role running at version 2.5.2.