NBU Backup job stuck on specifc file
Updated: 26 Sep 2010 | 5 comments
Hey All,
I'm running a large backup job today and noticed last time that it took much longer than it normally does. This week it seems to be doing so again, so I'm trying to figure out why this job is so sluggish. I noticed from looking at the detailed information on the activity monitor that it has been on the same file for quite some time. I navigated to the file and its only about 2kb. Could this file be my issue? Or is that not updated as frequently throughout the backup job?
Any ideas of what log files i should look at that might help?
I'm running NBU 6.5.4 on win2k8
Let me know if you need more info or anything, Thanks!
Evan
Discussion Filed Under:
Comments
Check file locking, and
Check file locking, and exclusions.
Our windows guys have this issue all the time, trying not to be a windows hater, but I don't seem to have this issue with unix...
NBU 7.0.1 on Solaris 10
writing to EMC 4206 VTL
duplicating to LTO2 in SL8500
(Soon to be LTO5)
using ACSLS 7.3.1
What kind of file is this..Is
What kind of file is this..Is this App/DB related or system file
This is a .img file
This is a .img file
Systems Integrator
Emmanuel College
Boston, MA
logging
On this particular client enable bpbkar logging by creating bpbkar directory under <install path>\netbackup\logs. With BAR gui on this client enable verbose logging - ie set it to 5.
rerun this job and check the log file created in bpbkar directory.
Quebek is right, bpbkar is
Quebek is right, bpbkar is the correct process to debug for this.
http://seer.entsupport.symantec.com/docs/267292.htm
If locking is occurring...and get the usual explorer error Access Denied if trying to do anything with it. Could try and kill any handles on the file.
Good old sysinternals process explorer allowed file handles to be killed. Remember this from the vsp snapshot days.
http://seer.support.veritas.com/docs/270127.htm
Or the util Unlocker. has a portable version - handy these tools.!
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Would you like to reply?
Login or Register to post your comment.