Change Job Status from "Failed" to something else

[George_Schroede]

I think there is a registry entry to accomplish this. Does anyone know what it is?

[Ameet_Thakkar]

Please refer to the following technote which mentions various reasons which may cause the job to fail.
Title:- How to determine why a Backup Exec for Windows NT and Windows 2000 job failed http://seer.support.veritas.com/docs/191165.htm
And,
Title:- How to find out why a VERITAS Backup Exec (tm) 9.x http://seer.support.veritas.com/docs/267107.htm

To isolate such issue, try splitting the backup job( for example C:, D: for local and remote backup ) and observe which backup selection is causing this issue.

[George_Schroede]

Ameet,

I know why the job is faiing. I just want the notification to read "Completed with Exceptions" rather than "Failed" The customer gets nervous when he sees the failed notification.

GS

[Thomas_J__Hawle]

I second that. The "Failed" status is simply not correct where, for example, the job cannot find a laptop that is off-net and on the road somewhere. We need better terminology to describe what is really happening.

[Vidyaj__Patneka]

Hi,

The Failed jobs cannot be displayed as "completed with exceptions" or something different.The notifications send are directly related to the job status and hence cannot be modified.

However you can prevent Backup Exec from failing a backup operation when encountering corrupt files (excluding the Exchange files).You may refer the following technote,

http://seer.support.veritas.com/docs/193940.htm

Hope this helps.

[Rohit_Sonawale]

We hope this information helps, if you have any other questions please respond to the post and we will be more than happy to assist you further.

[Sascha_D]

Is it possible to have a job NOT fail if a file cannot be backed up due to access denied? I've run into issues where the permissions on certain files are not allowing the file to get backed up and then the whole job is failed. Which doesnt make sense to me.