Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

i have my 2 policies

Created: 23 Oct 2012 • Updated: 25 Oct 2012 | 5 comments
This issue has been solved. See solution.

I have my 2 polcies backup  failed with error 50 .Client name :unix235

Other Policies which have same client as unix235 completed.(we have miltiple data bases on one client)

May i know the reason for this?

Comments 5 CommentsJump to latest comment

Nicolai's picture

Status 50 is a client process aborted.

See a Symantec General procedure in resolving status 50 : http://www.symantec.com/docs/HOWTO34936

I don't think the policy is related to status 50. 

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Arun K's picture

Only 2 policies failed.But all completed successfully.I have searched the document also.

Marianne's picture

Arun - PLEASE give us something to work with.

Copy ALL the text in the Job Details and post here.

There are different reasons for status 50 - Troubleshooter button in Activity Monitor will help you understand why the error is seen and where to start with Troubleshooting. 

Read through the TN in Nicolai's post - take time to follow all of the advice.
Find out if Client was rebooted while backup was running.

Depending on what exactly is in Job Details, this could also be a possibility: 
http://www.symantec.com/docs/TECH146990 
http://www.symantec.com/docs/TECH163191

 

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Possible's picture

Arun,

Why you are so therotical..please post the logs to work with.

Look for bpbkar and why the job terminted.

Thanks.

mansoor.sheik's picture

Hi,

Please refer to below Link.This Link contains a doc file which explain the error 50 workaround in detailed manner.

http://www.symantec.com/docs/TECH42465