11-10-2014 05:27 AM
Hello,
We are running netbackup master on a windows 2008 sp1 r2 server.
In addition, all our backups go to 4 appliances that function as Media servers.
Recently, we encountered long backup times.
Sometimes, backups get stuck, causing other backup jobs not to start running and finnally cause them to abend with a 196 code.
Please advise.
Solved! Go to Solution.
01-12-2015 10:17 PM
The problem was solved only recently. The issue was because too much streams and jobs that backuped to the same appliance. We did balance between all the appliances and the issues was solved.
11-11-2014 01:47 AM
Versions please.
11-11-2014 10:18 PM
Appliance is 5230 and the netbackup on the appliance is 7.6.0.2
11-12-2014 03:40 AM
Thanks, post of these stuck jobs detailed status so we can see wha'ts happening. I've not heard of related bugs on these versions (although 7.6.0.2 isn't the best version to be on......)
11-17-2014 02:36 PM
If it's affecting only Vmware backups, either the job is hanging (not progressing) or becoming much slower than usual, then it is probably this issue:
http://www.symantec.com/docs/TECH223790
One way to verify is checking if you have many bpbkar coredumps in /log/crash of appliance media server.
11-23-2014 10:58 AM
This sounds to me like a fairly large environment with Windows master server probably underpowered and unable to control the environment?
What is master server specs?
Memory?
Physical cpu's?
What kind of performance tuning was done on the master?
11-24-2014 01:53 AM
Yes, this is big environment.
Actually, we still have the problem and symantec send us a support technitian to investigate this problem.
I will updat ehere when we will have any solution.
11-24-2014 02:36 AM
This sounds like performance issues on the Windows master.
Docs you can have a look at while waiting for Support person to come out:
NetBackup 7.6 Best Practices: Optimizing Performance
Updated NetBackup Backup Planning and Performance Tuning Guide for Release 7.5 and Release 7.6
01-12-2015 10:17 PM
The problem was solved only recently. The issue was because too much streams and jobs that backuped to the same appliance. We did balance between all the appliances and the issues was solved.