Screencasts - Hilfsvideos

Backup Status Report emailed on Windows NBU

Created: 24 Jan. 2013 • Aktualisiert: 11 Apr. 2013 | 1 Kommentar
Dieses Problem wurde gelöst. Siehe Lösung.


I have recently taking over a NBU environment and I am trying to find out how the following report is/was being emailed out so I can update where it is being sent to.  I can't seem to find a script on the NBU server and this environment does not have the reporting tool.  I know there is nothing scheduled in the windows task manager. 

Hi Maria,

Below is an example of the report in question.

From: NetBackup@trnbu01 [NetBackup@trnbu01]
Sent: Monday, December 31, 2012 11:48 PM
Subject: MISPW1002 Backup Results (Policy: MTL_Servers)

Mon 12/31/2012  11:48 -----------------------------
Mon 12/31/2012  11:48        CLIENT:  MISPW1002
Mon 12/31/2012  11:48        POLICY:  MTL_Servers
Mon 12/31/2012  11:48      SCHEDULE:  Daily
Mon 12/31/2012  11:48 SCHEDULE TYPE:  INCR
Mon 12/31/2012  11:48        STATUS:  1
Mon 12/31/2012  11:48        STREAM:  0
Mon 12/31/2012  11:48   DONE_TRYING:  1
Mon 12/31/2012  11:48 PRIMARY JOBID:  312695
Mon 12/31/2012  11:48 -----------------------------

the requested operation was partially successful
A problem was detected that may require corrective action during the requested operation.

Backup Selection:

Backup Problems:
    TIME            SERVER/CLIENT                      TEXT
12/31/2012 22:06:48 trnbu01 MISPW1002  from client MISPW1002: WRN - can't open
                    file: C:\Documents and Settings\AUTOSYS\ntuser.dat.LOG
                    (WIN32 32: The process cannot access the file because it
                    is being used by another process. )
12/31/2012 23:48:15 TRNBU01 MISPW1002  backup of client MISPW1002 exited with
                    status 1 (the requested operation was partially

Kommentare 1 CommentZum neuesten Kommentar

das Bild der RamNagallas

it looks like the backup_exit_notify script is configured.

Please check the script in below location Insall Drive/Veritas/netbackup/bin/backup_exit_notify.

move this to the another location if you dont not what to get the mails

III. backup_exit_notify -- A script that gets called by bpsched at the end of every backup job on the master
The /usr/openv/netbackup/bin/backup_exit_notify script is called by bpsched at the end of every backup on the master server. This script can be configured to send email for status 96, 219,  and other statuses that the Global Attributes or Universal setting miss. At the end of the backup, thebackup_exit_notify script is passed six variables:
$1 -- The client hostname.
$2 -- The policy name.
$3 -- The schedule name.
$4 -- The type of schedule: FULL, INCR, UBAK, UARC
$5 -- The backup status for the job.
$6 -- The backup stream number for the job.
A VERBOSE = 5 bpsched log will show an entry similar to:
00:03:37.594 [25366] <2> ?: /usr/openv/netbackup/bin/backup_exit_notify client policy sched FULL 0 0 &
By default, the script will write this information to/usr/openv/netbackup/bin/BACKUP_EXIT_CALLED. This script can be customized to send mail based on any of the variables passed to the script. The bpsched daemon just passes the script six variables and does no checking to see if the script runs successfully. To test, simply run thebackup_exit_notify and pass it six options (client, policy, schedule, type, status, stream number).
Note: Customizing this script is not supported by NetBackup Technical support. An example of the/usr/openv/netbackup/bin/backup_exit_notify script is provided as part of the default installation on the master server and can be used as a reference to customize the script.