Hi S@m, J.H. is right, the codes you listed aren't necessarily tied to a specific error or cause. It is often a general state. If you double click on the job / error code in the Activity Monitor it will bring up the log file for that job. Normally at the top is a summary that will list the errors and where they are. They will be in red and that is actually a link to where they are in the main body of the log. Looking at the whole line of an error will give you a good description of what happened and where to start.
I started my current job about 6 months ago and have been learning on the fly as managing the Avamar was handed to me very early as one of my main responsibilites. Something I learned very quickly is sometimes good documentation is easy to find and other times not at all from EMC! So there have things I've been able to find myself. Other things this forum has been a good resource and sometimes I have just had to call support.
J_H_
2 Intern
•
498 Posts
0
November 13th, 2014 08:00
1) go to activity monitor, right click failed job, choose view log, your reasons are listed there.
2) reading why it failed see if you can fix the error or look up the error in EMC support
__14
23 Posts
0
November 13th, 2014 10:00
Thanks J.P.
I am agree with the monitor log from the activity , but my concern what does the error code signifies , like network connection broken .
I did not find any relevent KB article in EMC Support ( might be i am searching in a wrong way ) .
It will be appreciated , if you could refer some of the KB article .
J_H_
2 Intern
•
498 Posts
0
November 13th, 2014 10:00
what did the error in the log file tell you, you need to look up the error in the log file not the failure code
GNeal11
1 Rookie
•
21 Posts
0
November 13th, 2014 11:00
Hi S@m, J.H. is right, the codes you listed aren't necessarily tied to a specific error or cause. It is often a general state. If you double click on the job / error code in the Activity Monitor it will bring up the log file for that job. Normally at the top is a summary that will list the errors and where they are. They will be in red and that is actually a link to where they are in the main body of the log. Looking at the whole line of an error will give you a good description of what happened and where to start.
I started my current job about 6 months ago and have been learning on the fly as managing the Avamar was handed to me very early as one of my main responsibilites. Something I learned very quickly is sometimes good documentation is easy to find and other times not at all from EMC! So there have things I've been able to find myself. Other things this forum has been a good resource and sometimes I have just had to call support.