"Bpsched" hangs at the end of the daily backup session and must be stopped and restarted the next day, before the backups for that day will successfully execute.

Article:TECH5904  |  Created: 2000-01-15  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH5904
Article Type
Technical Solution


Environment

Issue



"Bpsched" hangs at the end of the daily backup session and must be stopped and restarted the next day, before the backups for that day will successfully execute.


Solution



The NetBackup (NBU) database backup is scheduled to run after every successful backup session and there is some problem associated with the tape whose volume ID has been specified, via "xbpadm" in "NetBackup DB Backup Attributes", to be used for NetBackup database backups.


1) Run "xbpadm" and choose file ->Change NetBackup DB Backup Attributes.  When the "NetBackup DB Backup Attributes" window comes up, note the date specified  under "Date Written" for Media 1 (and for Media 2 if NetBackup DB backups are configured to alternate between media from backup to backup).
If there is a problem associated with the tape(s) used for the NetBackup database backup, the "Date Written" for the tape(s) will be one or several days behind the current day's date (assuming that backups are executed normally on a daily basis).  If the "Date Written" is not current, make note of the Media ID of the tape(s) that is specified for the NetBackup database backup.


2)  Exit the "NetBackup DB Backup Attributes" window and choose reports->all log entries in the "xbpadm" window.  In the "all log entries" report look for text that contains the media ID specified for the NetBackup database backup( e.g. C0044) and or look for text that contains the string "NB database backup".  A sample of text from the "all log entries report" that indicates a problem with the volume ID specified for the NetBackup database backup is as follows:


12/19/99 00:03:40 rcnfs -  **************** GOOD MORNING ****************
12/20/99 00:07:06 rcnfs -  **************** GOOD MORNING ****************
12/20/99 14:17:59 rcnfs -  scheduler exiting - termination requested by
                   administrator (150)
12/20/99 14:18:07 rcnfs -  media manager terminated by parent process
12/20/99 14:18:07 rcnfs -  load of media id C0044 failed, media manager
                   killed by signal
12/20/99 14:18:07 rcnfs -  NB database backup to media id C0044 FAILED
12/20/99 14:18:35 rcnfs -  bprd TERMINATED
12/20/99 14:18:38 rcnfs -  bpdbm TERMINATED
12/20/99 14:19:08 rcnfs -  INITIATING bpdbm: NetBackup 3.1.1GA HP-UX 99052814
                   on rcnfs (verbose) IDIRSTRUCT=1
12/20/99 14:19:16 rcnfs -  INITIATING bprd: NetBackup 3.1.1GA HP-UX 99082411
                   on rcnfs
12/20/99 14:19:28 rcnfs -  scheduler found no backups due to run

A preliminary look at the all_log_entries report show that there is a problem with media id C0044:

3) Check to see if the tape volume ( i.e C0044 in the example) is in fact physically present in the standalone tape drive or tape robot. This can be done by visual inspection of the drive and/or robot.  It can also be done by running "xdevadm" and looking for a pending mount request for the NetBackup database backup tape volume. This latter operation has to be done before the "hung" bpsched is killed by the Systems Administrator (as indicated by the text: 12/20/99 14:17:59 rcnfs -  scheduler exiting - termination requested by administrator (150) in the "all log entries report" example above).  If such a pending mount request exists, then the required tape volume is not physically present in the robot or the drive.  Load the required volume.


4) If the tape volume is in fact physically present in the standalone tape drive or tape robot, check to see if there are errors associated with the tape volume in the output of the support script.  Execute the support script directing its output to an output file:

/usr/openv/netbackup/bin/goodies/support  >> support.dat


Edit the output file and search for the media ID (e.g.C0044) or search for the text: =============== MEDIA ERRORS ============== .
and look for the media ID in the list under MEDIA ERRORS.  ( An option to executing the support script is to check the file /usr/openv/netbackup/db/media/errors for the media errors.  This option is usually less time consuming than running the support script.)
If the media ID appears with read or write errors, introduce a new tape with a unique media ID into NetBackup via "xvmadm" (actions->new->single volume) and place the tape in the NetBackup volume pool.  Finally, run "xbpadm" choosing file->Change NetBackup DB Backup Attributes.  In the  "Netbackup DB Backup Attributes" window  highlight the name of the defective media ID in the Media ID" box and delete the ID.  Then enter the media ID of the new tape to be used fro NetBackup database backups. Finally, click on "OK" to save the ID and exit the "NetBackup DB Backup Attributes" window.
 



Legacy ID



197602


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


Terms of use for this information are found in Legal Notices