DOCUMENTATION: How to manually remove jobs from the NetBackup Activity Monitor which are in a queued or stopped state, and cannot be canceled, deleted, or removed by cycling the NetBackup services/daemons.

Article:TECH43177  |  Created: 2005-01-15  |  Updated: 2013-08-15  |  Article URL http://www.symantec.com/docs/TECH43177
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION: How to manually remove jobs from the NetBackup Activity Monitor which are in a queued, or stopped state, and cannot be canceled, deleted, or removed by cycling the NetBackup services/daemons.  This procedure is valid for all versions of NetBackup up to 7.1. 


Error



This procedure should be used for jobs with Status Code 50 with "waiting for retry" or for ghost jobs, which are jobs that do not have policy, client or other details in the activity monitor and which can't be deleted by any other means.


Environment



Applicable to all supported versions of NetBackup and operating systems that have 7.1.x or earlier versions installed.  At NetBackup version 7.5 the jobs database is moved into the Sybase database and can no longer be deleted by these methods.

See HOWTO73140 in the related articles section below for instructions for versions 7.5 and above.


Cause



This can be caused by a variety of issues.  See TECH146990 in the "Related Articles" area of this technote for details.


Solution



Manual:

NetBackup 7.0 System Administrators Guide for UNIX, Volume I
NetBackup 7.0 System Administrators Guide for Windows, Volume I
NetBackup 7.1 System Administrators Guide for UNIX, Volume I
NetBackup 7.1 System Administrators Guide for Windows, Volume I
NetBackup 7.5 System Administrators Guide for UNIX, Volume I
NetBackup 7.5 System Administrators Guide for Windows, Volume I

Page:  N/A

Modification Type: Supplement.

Modification:

If there are jobs which appear "hung" in the NetBackup Activity Monitor, it is possible a stop and restart of the NetBackup services/daemons may not clear them.

Windows

For Windows master, when backups, restores and duplications are not running, please do the following on the master server:

1.  Make note of the jobids that need to be deleted.  For this example jobids 1234 and 2345 will be used - the actual jobids impacted may be different.

2. Stop NetBackup (bpdown) in the default folder: <install_path>\VERITAS\NetBackup\bin on the master and media servers. It may be neccessary to run bpdown more than one time.

3. Run bpps to verify all processes are down.  If needed, stop them using the Windows Task Manager.

4. cd to install_path\veritas\netbackup\db\jobs

5. Delete the bpjobd.act.db file  (Note: this file may appear to be named bpjobd.act if 'Hide extensions for known file types' if checked in Windows Explorer options)

6.  cd restart directory

7. Delete the files with the jobid's in them, i.e. anything with 1234 and 2345.

8. cd..\trylogs

9. Delete the ".t" files with the affected jobids in them, such as 1234.t and 2345.t.

10. cd..\ffilelogs

11. Delete the files with the correlating jobids in them.  Such as  1234.f, 2345.f, etc.,

12. Restart NetBackup (bpup) in : <install_path>\VERITAS\NetBackup\bin

 

UNIX

For Unix master, when backups, restores and duplications are not running, please do the following on the master server:

1.  Make note of the jobids that need to be deleted.  For this example jobids 1234 and 2345 will be used - the actual jobids impacted may be different.

2.  Stop NetBackup (netbackup stop) in  /usr/openv/netbackup/bin/goodies on the master and media servers.

3.  Run /usr/openv/netbackup/bin/bpps -a.  If processes are still running, run bp.kill_all.  If any processes are still active, manually kill them.

4. cd to  /usr/openv/netbackup/db/jobs

5. rm the bpjobd.act.db file

6.  cd restart directory

7. Delete the files with the jobid's in them, i.e. anything with 1234 and 2345.

8.  cd ../trylogs

9. Delete the ".t" files with the affected jobids in them, such as 1234.t and 2345.t.

10. cd../ffilelogs

11. Delete the files with the correlating jobids in them.  Such as  1234.f, 2345.f, etc.,

12. Restart NetBackup (netbackup start).

Note: Completed jobs are stored in bpjobd.db file.  Following the directions in this technote will allow job history to be maintained, to include job details.

*** If neccessary to delete all jobs, all information can be deleted from <install_path>\VERITAS\NetBackup\db\jobs (Windows) or /usr/openv/netbackup/db/jobs (UNIX)  except for the jobid file.  The jobid file contains the last jobid that was allocated to a job.   The jobid file should be left in place so that reporting tools such as OpsCenter don't have duplicate jobids in them.  This is not recommended as all data associated with previous jobs will be deleted.




Legacy ID



278498


Article URL http://www.symantec.com/docs/TECH43177


Terms of use for this information are found in Legal Notices