08-24-2012 02:00 PM
Hi Folks,
I am doing windows to window alternate restoration but its getting failed with error code 5.Please find the below for error code and attachement for mt media server logs.could you please alayse and let us know the solution..
From the client, collect and send me the bpbkar and bpcd logs again.
From the media server, collect and send me the bpbrm, bptm, and bpcd logs.
My master and media server is solaris 10 with 6.5.5 version.
Thanks,
Susi.S
Solved! Go to Solution.
08-26-2012 05:54 AM
Hi Marianne,
We found issue with NIC card driver version very old and speed also mis matching.We are planing to upgrade driver versiona and i will keep on posted once issue is fixed.
I want to know how you analysing logs? using any tool?
Thanks,
Susi.S
08-24-2012 05:13 PM
Hi All,
Any one help on this???????????????
Thanks,
Susi.S
08-24-2012 07:16 PM
Bpbkar log is for backup. You need tar log on client for restore. Please also give us the restore progress log on the master server.
PS: Urgent matters should be logged with Symantec Support.
We all live in different parts of the world in different timezones..... America, Europe, Africa are all asleep right now... plus it's the weekend...
08-24-2012 08:14 PM
The PIDs and the times in media server log are different to the ones that you posted above in Job Details, but I can see that restore was running, that bptm was reading files and was sending it to the client until network connection was broken on client side.
You need to concentrate troubleshooting efforts on the client - check for anti-virus software that could terminate restore process.
Check tar log to see if any data was actually received and written by the client.
Check Event Viewer logs for errors.
Something outside of NBU broke network connection.
08-24-2012 09:37 PM
Thanks Marianne..What and all i have to check on client side..i am basically for unix side and i want to check windows team to look on it..Could you please explain what and all logs i need to check with them??
I have logged call with symantec 2 days before but its going like a journy............:(
08-24-2012 09:45 PM
Please read through my previous post.
I have listed all I can think of.
08-24-2012 10:25 PM
Thanks marianne..Let me check with windows team for below pont ..
You need to concentrate troubleshooting efforts on the client - check for anti-virus software that could terminate restore process.
Check tar log to see if any data was actually received and written by the client.
Check Event Viewer logs for errors.
08-24-2012 11:39 PM
Most of times i got this kind of error it due to insufficient privileges on target side.
Check if that helps
08-25-2012 12:16 PM
Have you collected tar log from the client side? It's really necessary.
08-25-2012 12:19 PM
please find the tar and bpcd logs..
08-25-2012 12:20 PM
i have attached below my tar logs..
08-25-2012 01:00 PM
No problem in NBU logs on client - successful connection in bpcd; tar log show files being received/restored between 09:37 and 09:53. No errors.
This confirms that "something" outside of NBU has terminated the restore/connection.
Have you checked Event Viewer logs on client yet? I would check all of them for any hints as to what happened around the time of the last entry in tar log (9:53:58).
Check anti-virus logs as well.
08-25-2012 01:13 PM
How many NIC does your clinet have? Run bplocaladdrs -verbose on your client.
08-26-2012 05:54 AM
Hi Marianne,
We found issue with NIC card driver version very old and speed also mis matching.We are planing to upgrade driver versiona and i will keep on posted once issue is fixed.
I want to know how you analysing logs? using any tool?
Thanks,
Susi.S
08-26-2012 10:41 AM
I do not have any tool.
This post explains how I am reading logs: https://www-secure.symantec.com/connect/forums/how-use-logs#comment-6505511
Not sure if Symantec Support staff have tools to read/analyse logs (especially level 5 logs), but I run a mile when someone posts level 5 log....
08-26-2012 11:32 PM
Dear Susindran,
Is this client has backup policy in your nbu system?
Is this server inserted to hosts file?
08-27-2012 10:32 AM
Hi Muhanas,
We find issue.Its will NIC card.
08-27-2012 10:35 AM
Good information marianne...
08-27-2012 11:43 AM
I love level 5 logs .... ;o)
"Not sure if Symantec Support staff have tools to read/analyse logs"
Yes, it is called a BackLine Engineer .... he he he ...
More seriously, yes and no.
The best tools for looking at logs are textpad and unix awk, oh, and I hate to say it but experience.
There are no magic tools, support have an internal only tool that helps when looking through the IRM logs (pem, jm, rb, emm) , but this is really the only script that I know of.
Legacy logs (found in /usr/openv/volmgr/debug and /usr/openv/netbackup/logs ) are fairly easy to read as they are single threaded. Quite conveniently, if you have an error you quite often have a <16> on the line.
Unfortunately easy to read does not mean 'easy to find the problem', just that it is easy to pull out the lines that refer to 'whatever' part of the job, as the lines will all have the same PID.
For support, most of us just get them at verbose 5 ( + general 2 if windows) although sometimes overkill, this ensures we definately have the details we need and avoids having to get the logs again, if we make a mistake and request them too low.
The lines contain a process ID, and as single threaded, if you pull out the lines with the same process id, you often have the details you need. There may be a child process, with a different PID, but quite often the parent process gives the PID of the child.
The best two tools for legacy logs are the unix 'awk' command and /or the program 'textpad' which can be purchasd for about $25.
How good is textpad, well, Symantec have a license to use it. It was once described to me as almost being written to read Netbackup logs.
If you are good with Unix awk, this can be good for pulling bit's out of logs, and other outputs from NBU commands.
You could also do simple things like a small unix script to automatically pull out all the lines for the different PIDs in a legacy log and place in a sepaare files - this could save vast amounts of time, and just makes things less stressful.
VX/ Unified logs are a nightmare because they are multi-threaded, as it happened I wrote some details about these the other day in another post which I have copied here.
Regards,
martin
08-27-2012 12:27 PM
Very very helpful martin..