Forum Discussion

Venki009's avatar
Venki009
Level 4
11 years ago
Solved

Backup failing with 50

Hi Team,

 

One of my failing with 50 after long writing,it failing after 75% of backup.

Master/Media :Linux 2.6,NBU 7.5

 

Client: Windows 2008,NBU 7.5

 

Thanks in advance

 

 

  • 10/01/2014 06:20:28 - Info bpbrm (pid=24825) start bpbkar on client

    10/01/2014 06:20:28 - connected; connect time: 0:00:00

    10/01/2014 06:20:28 - begin writing

    10/01/2014 06:20:30 - Info bpbkar (pid=5136) Backup started

    10/01/2014 06:20:30 - Info bpbrm (pid=24825) Sending the file list to the client

    10/01/2014 06:20:31 - Info bpbkar (pid=5136) change journal NOT enabled for <D:\>

    client process aborted  (50)

     

    your job failed with in 4 seconds once after staritng the bpbkar in client..

    are you sure its wring 75% of data...? what is the backup selection...?

    does this failure happening everytime when you run the backup or at speciifc time?

    please enable the bpbkar log with verbose 5 in client side and run the backup again... and attach the log to this post

4 Replies

  • 10/01/2014 06:20:28 - Info bpbrm (pid=24825) start bpbkar on client

    10/01/2014 06:20:28 - connected; connect time: 0:00:00

    10/01/2014 06:20:28 - begin writing

    10/01/2014 06:20:30 - Info bpbkar (pid=5136) Backup started

    10/01/2014 06:20:30 - Info bpbrm (pid=24825) Sending the file list to the client

    10/01/2014 06:20:31 - Info bpbkar (pid=5136) change journal NOT enabled for <D:\>

    client process aborted  (50)

     

    your job failed with in 4 seconds once after staritng the bpbkar in client..

    are you sure its wring 75% of data...? what is the backup selection...?

    does this failure happening everytime when you run the backup or at speciifc time?

    please enable the bpbkar log with verbose 5 in client side and run the backup again... and attach the log to this post

  • While the job took a long time, most of that was waiting for the robot to give you a drive. What your looking for here is the fact that the client (bpbkar) dumped out so fast. like Ram said, 4 seconds. 

    I would like to see the bpbkar log for around the same time. "Change journal NOT enabled" is most likley not even related, its more of a INFO message. 

    Also please patch if your at 7 base.

     

  • Speak to sysadmin of this client.

    My guess is that one of these 2 things happened: 

    1) The client rebooted or crashed.

    2) Someone killed bpbkar on the client.