NetBackup Error Status 157 when trying to resume a suspended job

[wheelscs]

I have an issue where I suspend jobs so they do not run durring production hours and many times when I select to resume these jobs they fail immediately with a red X and and error cone 157 on the child and error code 50 on the parent. When you right click these jobs resume is no longer an option you must restart them.

Child Job

6/14/2013 10:01:24 PM - Info nbjm(pid=6292) starting backup job (jobid=73264) for client WSPC001001ICS02, policy WSPC001001ICS02, schedule Full 
6/14/2013 10:01:24 PM - estimated 238091815 Kbytes needed
6/14/2013 10:01:24 PM - Info nbjm(pid=6292) started backup (backupid=WSPC001001ICS02_1371261684) job for client WSPC001001ICS02, policy WSPC001001ICS02, schedule Full on storage unit D2600B_Weekly
6/14/2013 10:01:24 PM - started process bpbrm (14448)
6/14/2013 10:01:32 PM - Info bpbrm(pid=14448) WSPC001001ICS02 is the host to backup data from    
6/14/2013 10:01:32 PM - Info bpbrm(pid=14448) reading file list from client       
6/14/2013 10:01:34 PM - connecting
6/14/2013 10:01:37 PM - Info bpbrm(pid=14448) starting bpbkar32 on client        
6/14/2013 10:01:37 PM - connected; connect time: 00:00:03
6/14/2013 10:01:47 PM - Info bpbkar32(pid=4332) Backup started          
6/14/2013 10:01:47 PM - Info bptm(pid=11344) start           
6/14/2013 10:01:47 PM - Info bptm(pid=11344) using 262144 data buffer size       
6/14/2013 10:01:47 PM - Info bptm(pid=11344) setting receive network buffer to 252144 bytes     
6/14/2013 10:01:47 PM - Info bptm(pid=11344) using 64 data buffers        
6/14/2013 10:01:49 PM - Info bptm(pid=11344) start backup          
6/14/2013 10:01:49 PM - Info bptm(pid=11344) backup child process is pid 20920.12764      
6/14/2013 10:01:49 PM - Info bptm(pid=20920) start           
6/14/2013 10:01:49 PM - begin writing
6/14/2013 10:02:12 PM - Info bpbkar32(pid=4332) change journal NOT enabled for <F:\>      
6/17/2013 9:11:57 AM - end writing; write time: 2 11:10:08
suspend requested by administrator(157)

Parent Job

6/17/2013 5:47:35 PM - Info nbjm(pid=6292) starting backup job (jobid=73259) for client WSPC001001ICS02, policy WSPC001001ICS02, schedule Full 
6/17/2013 5:47:35 PM - Info nbjm(pid=6292) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=73259, request id:{575C5F39-7285-4DAA-A0DE-E6AE2767A517}) 
6/17/2013 5:47:35 PM - requesting resource D2600B_Weekly
6/17/2013 5:47:35 PM - requesting resource wspc001001nm08.NBU_CLIENT.MAXJOBS.WSPC001001ICS02
6/17/2013 5:47:35 PM - requesting resource wspc001001nm08.NBU_POLICY.MAXJOBS.WSPC001001ICS02
6/17/2013 5:47:35 PM - granted resource wspc001001nm08.NBU_CLIENT.MAXJOBS.WSPC001001ICS02
6/17/2013 5:47:35 PM - granted resource wspc001001nm08.NBU_POLICY.MAXJOBS.WSPC001001ICS02
6/17/2013 5:47:35 PM - granted resource MediaID=@aaaaH;Path=G:\Weekly;MediaServer=WSPC001001NM08
6/17/2013 5:47:35 PM - granted resource D2600B_Weekly
6/17/2013 5:47:36 PM - estimated 238091815 Kbytes needed
6/17/2013 5:47:36 PM - begin Parent Job
6/17/2013 5:47:36 PM - begin Snapshot, Start Notify Script
6/17/2013 5:47:36 PM - Info RUNCMD(pid=13384) started           
6/17/2013 5:47:36 PM - Info RUNCMD(pid=13384) exiting with status: 0        
Status 0
6/17/2013 5:47:36 PM - end Snapshot, Start Notify Script; elapsed time: 00:00:00
6/17/2013 5:47:36 PM - begin Snapshot, Step By Condition
Status 0
6/17/2013 5:47:36 PM - end Snapshot, Step By Condition; elapsed time: 00:00:00
6/17/2013 5:47:36 PM - begin Snapshot, Policy Execution Manager Preprocessed
Status 50
6/17/2013 5:47:36 PM - end Snapshot, Policy Execution Manager Preprocessed; elapsed time: 00:00:00
6/17/2013 5:47:36 PM - begin Snapshot, Stop On Error
Status 0
6/17/2013 5:47:36 PM - end Snapshot, Stop On Error; elapsed time: 00:00:00
6/17/2013 5:47:36 PM - begin Snapshot, End Notify Script
6/17/2013 5:47:37 PM - Info RUNCMD(pid=8732) started           
6/17/2013 5:47:37 PM - Info RUNCMD(pid=8732) exiting with status: 0        
Status 0
6/17/2013 5:47:37 PM - end Snapshot, End Notify Script; elapsed time: 00:00:01
Status 50
6/17/2013 5:47:37 PM - end Parent Job; elapsed time: 00:00:01
client process aborted(50)
6/17/2013 5:47:41 PM - Info bpbrm(pid=10996) Starting delete snapshot processing        
6/17/2013 5:47:41 PM - Info bpfis(pid=0) Snapshot will not be deleted       
6/17/2013 5:47:55 PM - Info bpfis(pid=3408) Backup started          

[ontherocks · Accepted solution]

When you suspend a job, check the time in the Master servers "Clean Up" option "Move backup job from incomplete state to done state" as your job will come to Failed State after this period has elapsed.

[wheelscs]

My "Clean Up" option is set at 12 hours the last jobs to fail were started only 9 hours after they were suspended. My "Move backup job from incomplete state to done state" is set for 3 hours, but it this issue does not happen every time so I'm not sure if either one of these is the issue.

[ontherocks]

I have came accross the same issue, and after changing this parameter value the issue got resolved.

[wheelscs]

I will adjust them both to 18 hours and try wgain for a few days

[huanglao2002]

The parent job and the child job have 3 days gap.

Can you try to improve you backup performance to solve this problem?

[Pawan_Nagra_777]

Hi,

Please share the OS and NBU version 

Regards,

Pawan

[wheelscs]

To answer both. I'm not sure How to make the backup performance any better. I'm backing up from a SAN to a DAS. 

Windows 2008 R2

NetBackup 7.5.0.4

[Vickie]

Hi Wheelscs,

Sometime this could occur, if the media server netbackup services got bounce back (got recycled).

Check if that is the cause of this issue.

Are you getting this error all the time when you suspend a job and try to resume ?

Is it coming for specific server backup or you getting this for number of servers ?

[wheelscs]

this issue does not happen every time on any specifif servers

[Vickie]

If such an issue then, its the only cocern of make the jobs complete after specific time period as mentioned in above post.

You had changed that as you stated in previous update, do you still facing this issue ?