Forum Discussion

snawaz3's avatar
snawaz3
Level 6
12 years ago

BAR shuts down

NBU 7.5.0.6

master/media win 2008 r2

client win2003

backup of microsoft exchange information store started failing with error 13 'an exixting connection was forcibly closed by the remote host'. If I go to the client and start BAR. It comes up fine and shows the last backup of a couple of days ago. If I try and do a manual backup the BAR shuts down. Any clues what is happenening?

7.5
Backup and Recovery
NetBackup
Windows Server (2003-2008)
  • snawaz3's avatar
    snawaz3
    11 years ago

    semantec is still researching this issue. But google finally came through. there is a bug fix for cluster nodes when upgrading to 7.5.0.6. After installing the fix the BAR works and the backup works

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

    thanks for all the help.my bad probably forget to mention the cluster

  • revarooo's avatar
    revarooo
    Level 6
    12 years ago

    Have you tried disabling any anti-virus on the system? If so, does it work then?

  • Nate_D1's avatar
    Nate_D1
    Level 6
    12 years ago

    The BAR console closes? Or the job shuts down (stops)? Are you trying to initiate the backup from the exchange server? Has anything changed in the environment recently? Any new hardware (routers/firewalls) in the network between the 2 servers?

    I know it sounds lame, but half the time when I have some funky random error a reboot or failover will resolve the issue. If thats possible in your environment you could just test that out quickly.

  • Will_Restore's avatar
    Will_Restore
    Level 6
    12 years ago

    Never good when the BAR shuts down early. wink  Check Windows Event Viewer for any clues.

     

    I agree with Nate, a reboot may be in order. 

  • snawaz3's avatar
    snawaz3
    Level 6
    12 years ago

    Yes I tried that but no difference. This happens intermittendly. It will run for a day or two an dthen will not run for a couple of days.

  • snawaz3's avatar
    snawaz3
    Level 6
    12 years ago

    rebooting did fix it once before but that is not an option i can regularly apply.

     

    @NATE.D....I am backing up from the master. But sometimes when backups fail I go to the client and start BAR. This gives me and indication that the clint is working. I have had errors because the client nbu was not working and after restarting the services the backup was good.

  • Nate_D1's avatar
    Nate_D1
    Level 6
    12 years ago

    It sounds like you may need to turn up the bpbrm logging, attempt a job, let it fail and see what it spits out. Error 13 can be pretty vague, with lots of possible places it could be broken.  Do the backups always fail with 13 or do they return any others? Are you trying to do a GRT backup? Does a reboot always fix the issue and then it comes back?

  • Will_Restore's avatar
    Will_Restore
    Level 6
    11 years ago

    no status 13 in the attached log, no fatal errors at all

    Nate suggested posting bpbrm log