VMWARE BACKUPS ARE FAILING WITH ERROR 73 AND 13

>>73: bpstart_notify failed     

Something wrong with your bpstart script.  Move it or rename it and try the job again to verify. 

Large number of Solved threads on this topic to help troubleshoot the root cause:

https://www-secure.symantec.com/connect/search/apachesolr_search/bpstart_notify%20status%2073?filters=type%3Asc_forum%20tid%3A711%20tid%3A1741%20is_cck_field_forum_solved%3A1

This does not look like a VMware backup but like a normal client backup (MS-Windows), right?

Someone has created a bpstart_notify.bat script on the client. It does not exist by default.

There seems to be a problem with the script. Speak to the server owner to find out what the purpose is of the notify script and to check why the script is failing.

Why did you start a new discussion one day later?

https://www-secure.symantec.com/connect/forums/vm-ware-backups-failing-error-73

this is a standard policy error 73.

there is no such script on the clients:

[root@CRO1A04DBV0L ~]# ls -lh /usr/openv/netbackup/bin/bpstart_notify.CRO2_Linux                                    ls: /usr/openv/netbackup/bin/bpstart_notify.CRO2_Linux: No such file or directory

[root@CRO1A07DBS0L ~]# ls -l /usr/openv/netbackup/bin/bpstart_notify.CRO2_Linux

ls: /usr/openv/netbackup/bin/bpstart_notify.CRO2_Linux: No such file or directory

24.09.2013 05:40:00 - Info nbjm(pid=8096) starting backup job (jobid=91364) for client CRO1A04DBV0L.mgmt.local, policy CRO2_Linux, schedule Inc-Backup 
24.09.2013 05:40:00 - Info nbjm(pid=8096) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=91364, request id:{587B50AA-0956-4041-A06E-F7E93DE4EDF9}) 
24.09.2013 05:40:00 - requesting resource SYSMP03BKS0W_BD2F
24.09.2013 05:40:00 - requesting resource sysmp03bks0w.mgmt.local.NBU_CLIENT.MAXJOBS.CRO1A04DBV0L.mgmt.local
24.09.2013 05:40:00 - requesting resource sysmp03bks0w.mgmt.local.NBU_POLICY.MAXJOBS.CRO2_Linux
24.09.2013 05:40:00 - granted resource sysmp03bks0w.mgmt.local.NBU_CLIENT.MAXJOBS.CRO1A04DBV0L.mgmt.local
24.09.2013 05:40:00 - granted resource sysmp03bks0w.mgmt.local.NBU_POLICY.MAXJOBS.CRO2_Linux
24.09.2013 05:40:00 - granted resource MediaID=@aaaad;Path=F:\BD2F;MediaServer=sysmp03bks0w.mgmt.local
24.09.2013 05:40:00 - granted resource SYSMP03BKS0W_BD2F
24.09.2013 05:40:00 - estimated 0 Kbytes needed
24.09.2013 05:40:00 - Info nbjm(pid=8096) resumed backup (backupid=CRO1A04DBV0L.mgmt.local_1379975834) job for client CRO1A04DBV0L.mgmt.local, policy CRO2_Linux, schedule Inc-Backup on storage unit SYSMP03BKS0W_BD2F
24.09.2013 05:40:00 - started process bpbrm (10268)
24.09.2013 05:40:01 - connecting
24.09.2013 05:40:03 - connected; connect time: 00:00:02
24.09.2013 05:40:05 - end writing
bpstart_notify failed(73)

Are there any bpstart_notify scripts on that client?

I dont understand from you command output where you have the bpstart_notify.CRO2_Linux from - unless that does exist but you do not have permission to access it?

not on the client.

So you are saying that CRO1A04DBV0L.mgmt.local has no bpstart_notify script at all in its NetBackup bin directory?

Only other thing i can think is that it could be a parent start notify for this client on the Master?

Yes.

bpstart_notify exists on the master.

It is a windows batch file.

I was think or the parent script - but worth looking at that one anyway while you are there

bpstart_notify on master server:

@REM $Id: bpstart_notify.bat,v 1.3 2006/08/01 20:46:43 $
@REM ***************************************************************************
@REM * $VRTScprght: Copyright 1993 - 2012 Symantec Corporation, All Rights Reserved $ *
@REM ***************************************************************************
@REM ecpyrght
@REM
@REM bpstart_notify.bat
@REM
@REM   This script is called by NetBackup when bpbkar is started up on the client
@REM   to do a backup or archive.
@REM
@REM This script receives 6 parameters:
@REM   %1 = CLIENT_NAME
@REM   %2 = POLICY_NAME
@REM   %3 = SCHEDULE_NAME
@REM   %4 = SCHEDULE_TYPE, one of the following: FULL, INCR, CINC, UBAK, UARC
@REM   %5 = STATUS, always 0
@REM   %6 = RESULT_FILE
@REM  
@REM   The script must reside in in the same directory as the rest of the NetBackup
@REM   client binaries (install_path\netbackup\bin\bpstart_notify.bat). 
@REM   It must also be executable by the root user.
@REM   Should exit with 0 upon successful completion
@REM
@REM Naming conventions:
@REM   There are three different versions of names that the scripts can use. 
@REM   The start notify script may use one version and the end notify script may use
@REM   another, or they can both use the same version.
@REM 
@REM   Substitute "policy" with the NetBackup policy being used and "sched" with the
@REM   schedule name.  "bpstart" can be substituted with "bpend".
@REM   bpstart_notify.policy.sched.bat
@REM   bpstart_notify.policy.bat
@REM   bpstart_notify.bat 
@REM 
@REM Result files:
@REM   The result file names will be dependant on the script file names. 
@REM   Example:
@REM   Script name:                         Result file name:
@REM   bpstart_notify.policyA.schedB.bat    BPSTART_RES.policyA.schedB
@REM   bpstart_notify.policyB.bat           BPSTART_RES.policyB
@REM   bpend_notify.bat                     BPEND_RES
@REM     
@REM CAUTION: Writing anything to stdout or stderr will cause backup problems.
@REM          Output should be redirected to the results files.
@REM
@REM --------------------------------------------------------------------
@REM main script starts here
@REM This is a simple script that records what kind of backup will be done along
@REM with other relevent information (Client name, policy name, etc) and
@REM appends the information to the results file
@REM --------------------------------------------------------------------
@if "%4" == "FULL" goto FULL
@if "%4" == "CINC" goto CINC
@if "%4" == "" goto FAIL
@REM print a generic message since backup is neither full, nor cumulative incremental
@echo backup/restore started on %1 using policy %2 with schedule %3 and status %5, bpres = %6 >> bin\BP_RES.txt
@echo 0 >> %6
@GOTO :EOF
@REM exit 0
:FULL
@echo full backup started on %1 using policy %2 with schedule %3 and status %5, bpres = %6 >> bin\BP_RES.txt
@echo 0 >> %6
@GOTO :EOF
@REM exit 0
@:CINC
@echo cumulative incremental backup started on %1 using policy %2 with schedule %3 and status %5, bpres = %6 >> bin\BP_RES.txt
@echo 0 >> %6
GOTO :EOF
@REM exit 0
:FAIL
@REM no schedule type information was sent.  A failure has occured.  Write status 1 to results files.
@echo 1 >> %6
@GOTO :EOF
@REM exit 0