Forum Discussion
Have a look at the processes that are involved in this backup:
bpbrm
bpbkar32
So, the logs that you need to check first are bpbrm and bpbkar.
- skrp5 years agoLevel 4
Hi Marianne,
Thanks for the update. I'm unable to open the file as it is too big. Can you suggest some editors please.
- Marianne5 years agoLevel 6
Try TextPad.
Hopefully your logging level is not set to 5?
I only enable this logging level if requested by Veritas Support.
Level 3 is normally fine for 99% of troubleshooting.
- Lowell_Palecek5 years agoLevel 6
My 7.5.x way-back machine isn't working so well this morning. In current terminology, a VMware policy has a backup host or a restore host. I think it used to be called a proxy host. At any rate, that's where bpbkar32 executes.
Q1: In your case, does bpbkar32 execute on the same master/media server where bpbrm executes?
Q2: Do you see anything significant in the Windows application event log? Did bpbkar32 or another NetBackup process crash?
For Windows client processes such as bpfis, bpbkar32, and tar32, the important logging level is the one you configure under Windows client host properties. It should be set to 2, which is the max.
Q3: If bpbkar32 didn't crash, what errors do you find in its log? If bpbkar32 did crash, what are the last 20 log lines before the crash? Please post such a summary here.
Q4: Are your Windows and VMware versions (VCenter, Esx server, VDDK) compatible with NetBackup 7.5.0.7?
- skrp5 years agoLevel 4
Here are the logs(bpbrm and bpbkar) as an attachment. Below are the backups that are failing with this error.
KOSLOAPP001
KWSLOWBE005L
KWSLOWBE053
KWSLOWBE002
KWSLOWBE004L
Please help me with this as I'm unable to resolve issue with KOSLOAPP001 and couldn't secure a backup for this client since one month.
- Marianne5 years agoLevel 6
The log file is way too big to download on my (slow) home network.
You say that you have uploaded (bpbrm and bpbkar), but there is only one large file?
What you need to look for in the logs are the PID's seen in Activity Monitor.
e.g. bpbrm log file for 15 July, look for PID 11572 in square brackets [ ] .
bpbkar on 15 July, look for all PID entries [15264].So, if you want to troubleshoot failures that happened on 15 July, there is no use looking at a log dated 13 July (071320.log).
Related Content
- 13 years ago
- 12 years ago
- 7 years ago
- 15 years ago
- 11 years ago