cancel
Showing results for 
Search instead for 
Did you mean: 

ERR - bpbkar exiting because backup is aborting

NBFREAK
Level 4

Hi Folks,

We are unable to run backups for the Mater server, where all client backups such as exchange servers backups are running fine. Master server backups are going to hung mode with the below error log and unabvle to suspend or cancel the job.. we cant recycle the netbackup services for killing these jobs all the time... please help me in giving resilution for this issue.


11/19/2009 7:51:47 AM - Error bptm(pid=5580) Media Manager volume pool DAILY has no more unassigned media in robotic device TLD(0)
11/19/2009 7:51:48 AM - Error bpbrm(pid=4776) from client <Server XXXXXX> : ERR - bpbkar exiting because backup is aborting

Your help is highly appreciated.


Thanks all
1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Level 6
Partner    VIP    Accredited Certified
Your master server is probably taking serious strain and is possibly running out of resources when bpbkar kicks in to backup itself. Have you tried to monitor cpu and memory on the master while the backup is running?
This TechNote explains why false status code 96 can be seen (problem was still present in 5.1):
seer.support.veritas.com/docs/237534.htm

Also check KeepAliveTime on the master:

Extract from  NetBackup Release Notes – Additional Operational Notes (TechNote 278130):
While at first it may appear that there is a problem with the NetBackup master server,
this delay is actually a result of a certain TCP/IP configuration parameter that is set to
7,200,000 (two hours, in milliseconds) by default. VERITAS recommends that you set
this parameter to 15 minutes (900,000 milliseconds) or the next lowest, configurable
value that is greater than 15 minutes. (This parameter is called KeepAliveTime on
Microsoft Windows and tcp_keepalive_interval on Solaris systems. You can check the
man page on your system to identify what this parameter is called. You can find more
information about the KeepAliveTime and other associated TCP/IP configuration
parameters on Microsoft Windows in the following Microsoft Knowledge Base
articles: Q140325 and Q120642 )

View solution in original post

4 REPLIES 4

Marianne
Level 6
Partner    VIP    Accredited Certified
Your NBU version? Master server O/S?

NBFREAK
Level 4

Netbackup 5.1 MP4 , Master server with Windows 2000

Anonymous
Not applicable
Increase debug logging to level 5 and look inside bpbkar logs on the client for starters.

Does robot TLD0 have unassigned media from the DAILY pool in its inventory.? If not you need to either put new tapes in or early expire the backup images on some DAILY media.

Marianne
Level 6
Partner    VIP    Accredited Certified
Your master server is probably taking serious strain and is possibly running out of resources when bpbkar kicks in to backup itself. Have you tried to monitor cpu and memory on the master while the backup is running?
This TechNote explains why false status code 96 can be seen (problem was still present in 5.1):
seer.support.veritas.com/docs/237534.htm

Also check KeepAliveTime on the master:

Extract from  NetBackup Release Notes – Additional Operational Notes (TechNote 278130):
While at first it may appear that there is a problem with the NetBackup master server,
this delay is actually a result of a certain TCP/IP configuration parameter that is set to
7,200,000 (two hours, in milliseconds) by default. VERITAS recommends that you set
this parameter to 15 minutes (900,000 milliseconds) or the next lowest, configurable
value that is greater than 15 minutes. (This parameter is called KeepAliveTime on
Microsoft Windows and tcp_keepalive_interval on Solaris systems. You can check the
man page on your system to identify what this parameter is called. You can find more
information about the KeepAliveTime and other associated TCP/IP configuration
parameters on Microsoft Windows in the following Microsoft Knowledge Base
articles: Q140325 and Q120642 )