Nick_Montour
20 years agoLevel 2
Failed Jobs
Is there any way to tell quickly why a job failed? Basically, if a job fails because an open file couldn't be backed up or if it's because the backup server couldn't connect to one of the network drives, there isn't a way to tell quickly what happened without opening the log (which is large and takes a decent amount of time).
Is there any way to tell if a job failure was because of something like an open file or a problem with a single file vs. not being able to connect to a network drive?
I was told by a Vertias Tech Support agent a while back that jobs must be marked failed even if a file couldn't be backed up because it was open, but said there was no way to quickly tell what happened without reading the log file.
Thanks!
Is there any way to tell if a job failure was because of something like an open file or a problem with a single file vs. not being able to connect to a network drive?
I was told by a Vertias Tech Support agent a while back that jobs must be marked failed even if a file couldn't be backed up because it was open, but said there was no way to quickly tell what happened without reading the log file.
Thanks!