Dave,

You have to check each and every drive backup log. If a file
is corrupted then you will get a failed status.
I also had my backup selection saying to backup N: drive but
there was no n: drive so the status was always Failed.

Linnea


"Dave" wrote:
>
>I'm getting the following status:
>
>Job completion status: Failed
>
>but I can't see any thing wrong with job. Whats up here? Others are having
>this problem also!!

The following is the list I use to determine the cause of a "FAILED" status. If
you have an editor that suports macros, set one up that you can use scan any
failed job log.

Access Denied
Corrupt File
Unable to Attach
Job was Aborted
Insufficient Memory
The Media Operations was Aborted
Drive Not Responding
Lost Connection

If you have V7.3, you can also scan for the "^" character.


Dave wrote:

> I'm getting the following status:
>
> Job completion status: Failed
>
> but I can't see any thing wrong with job. Whats up here? Others are having
> this problem also!!

Yes, I to am geting that same 'failed' error. I have scoured the books to
no avail. I have posted at various sites again to resolution. Anyone have
any idea about this? I have checked for 'skipped', 'corrupt' and other keywords,
still nothing has solved this. HELP!!!

"Dave" wrote:
>
>I'm getting the following status:
>
>Job completion status: Failed
>
>but I can't see any thing wrong with job. Whats up here? Others are having
>this problem also!!

ok.....post the whole log here then..lets take a look.....always a first for
everything but i have yet to see a log from a failed job that didnt have a
reason.
i am not not being a smart-ass ... just never seen what you describe before.


"Victor Peel" wrote in message
news:392aa4cf@hronntp01....
>
> Yes, I to am geting that same 'failed' error. I have scoured the books to
> no avail. I have posted at various sites again to resolution. Anyone
have
> any idea about this? I have checked for 'skipped', 'corrupt' and other
keywords,
> still nothing has solved this. HELP!!!
>
> "Dave" wrote:
> >
> >I'm getting the following status:
> >
> >Job completion status: Failed
> >
> >but I can't see any thing wrong with job. Whats up here? Others are
having
> >this problem also!!
>

yes! I get the same messages. So far I think BE 8 is WAY to full of bugs to
use on a productional server. I'm completley unimpressed with the product.
Heck, Microsoft products work better!

"Victor Peel" wrote:
>
>Yes, I to am geting that same 'failed' error. I have scoured the books
to
>no avail. I have posted at various sites again to resolution. Anyone have
>any idea about this? I have checked for 'skipped', 'corrupt' and other
keywords,
>still nothing has solved this. HELP!!!
>
>"Dave" wrote:
>>
>>I'm getting the following status:
>>
>>Job completion status: Failed
>>
>>but I can't see any thing wrong with job. Whats up here? Others are having
>>this problem also!!
>

Agents are running on all server ??
(no agents not present, in logfile)


trombone skrev i en
nyhedsmeddelelse:392b65fb@hronntp01....
> ok.....post the whole log here then..lets take a look.....always a first
for
> everything but i have yet to see a log from a failed job that didnt have a
> reason.
> i am not not being a smart-ass ... just never seen what you describe
before.
>
>
> "Victor Peel" wrote in message
> news:392aa4cf@hronntp01....
> >
> > Yes, I to am geting that same 'failed' error. I have scoured the books
to
> > no avail. I have posted at various sites again to resolution. Anyone
> have
> > any idea about this? I have checked for 'skipped', 'corrupt' and other
> keywords,
> > still nothing has solved this. HELP!!!
> >
> > "Dave" wrote:
> > >
> > >I'm getting the following status:
> > >
> > >Job completion status: Failed
> > >
> > >but I can't see any thing wrong with job. Whats up here? Others are
> having
> > >this problem also!!
> >
>
>

I'm on version 7.2 and I just got my first taste of this problem. I see nothing
in the job log that would cause me to get the "failed" message at the end
of my backup.

"Derek Seaman" wrote:
>
>yes! I get the same messages. So far I think BE 8 is WAY to full of bugs
to
>use on a productional server. I'm completley unimpressed with the product.
>Heck, Microsoft products work better!
>
>"Victor Peel" wrote:
>>
>>Yes, I to am geting that same 'failed' error. I have scoured the books
>to
>>no avail. I have posted at various sites again to resolution. Anyone
have
>>any idea about this? I have checked for 'skipped', 'corrupt' and other
>keywords,
>>still nothing has solved this. HELP!!!
>>
>>"Dave" wrote:
>>>
>>>I'm getting the following status:
>>>
>>>Job completion status: Failed
>>>
>>>but I can't see any thing wrong with job. Whats up here? Others are
having
>>>this problem also!!
>>
>

I get an error stating "Drive is not responding. Backup set aborted" and when
I check the log it shows that the amount of data processed actually EXCEEDS
the amount in the backup set!
We backup the same files Incrementally through the week with no error. WHen
I run a Full backup at the end of the week, it fails with the above error,
but at different points. We have v7.2 of BackUp Exec for NT installed. The
only material relating to the above error regards backing up Exchange, an
Oracle database, or the Registry on a Win9.x PC, NONE of which apply to my
situation.
If you find out what causes the error message, I'd sure like to know about
it!


"Michael Thornton" wrote:
>
>I'm on version 7.2 and I just got my first taste of this problem. I see
nothing
>in the job log that would cause me to get the "failed" message at the end
>of my backup.
>
>"Derek Seaman" wrote:
>>
>>yes! I get the same messages. So far I think BE 8 is WAY to full of bugs
>to
>>use on a productional server. I'm completley unimpressed with the product.
>>Heck, Microsoft products work better!
>>
>>"Victor Peel" wrote:
>>>
>>>Yes, I to am geting that same 'failed' error. I have scoured the books
>>to
>>>no avail. I have posted at various sites again to resolution. Anyone
>have
>>>any idea about this? I have checked for 'skipped', 'corrupt' and other
>>keywords,
>>>still nothing has solved this. HELP!!!
>>>
>>>"Dave" wrote:
>>>>
>>>>I'm getting the following status:
>>>>
>>>>Job completion status: Failed
>>>>
>>>>but I can't see any thing wrong with job. Whats up here? Others are
>having
>>>>this problem also!!
>>>
>>
>

"Neil Brown" wrote:
>
>I get an error stating "Drive is not responding. Backup set aborted" and
when
>I check the log it shows that the amount of data processed actually EXCEEDS
>the amount in the backup set!
>We backup the same files Incrementally through the week with no error. WHen
>I run a Full backup at the end of the week, it fails with the above error,
>but at different points. We have v7.2 of BackUp Exec for NT installed.
The
>only material relating to the above error regards backing up Exchange, an
>Oracle database, or the Registry on a Win9.x PC, NONE of which apply to
my
>situation.
>If you find out what causes the error message, I'd sure like to know about
>it!
>
>
>"Michael Thornton" wrote:
>>
>>I'm on version 7.2 and I just got my first taste of this problem. I see
>nothing
>>in the job log that would cause me to get the "failed" message at the end
>>of my backup.
>>
>>"Derek Seaman" wrote:
>>>
>>>yes! I get the same messages. So far I think BE 8 is WAY to full of bugs
>>to
>>>use on a productional server. I'm completley unimpressed with the product.
>>>Heck, Microsoft products work better!
>>>
>>>"Victor Peel" wrote:
>>>>
>>>>Yes, I to am geting that same 'failed' error. I have scoured the books
>>>to
>>>>no avail. I have posted at various sites again to resolution. Anyone
>>have
>>>>any idea about this? I have checked for 'skipped', 'corrupt' and other
>>>keywords,
>>>>still nothing has solved this. HELP!!!
>>>>
>>>>"Dave" wrote:
>>>>>
>>>>>I'm getting the following status:
>>>>>
>>>>>Job completion status: Failed
>>>>>
>>>>>but I can't see any thing wrong with job. Whats up here? Others are
>>having
>>>>>this problem also!!
>>>>
>>>
>>
>
Same problem as the rest of you....has anyone called with a service contract?

Right !

If anyone of you have experienced the backup job ending in a "Failed" status
and some files were reported being corrupted etc. please check this posting:

In Veritas' Knowledge Base select "BackupExec NT/2000"
In Version select "8.0"
In Subject select "All Subjects"
In Search Phrase type "193940"

Make sure you're connected to the US-site as the UK site is not actually
similar. (I'm not kidding ! Honestly )

If you still have problems locating the fix, please feel free to e-mail me
at my above address

Regards

Colin Padget
"I haven't lost my mind - It's backed up somewhere"

"James" wrote:
>
>"Neil Brown" wrote:
>>
>>I get an error stating "Drive is not responding. Backup set aborted" and
>when
>>I check the log it shows that the amount of data processed actually EXCEEDS
>>the amount in the backup set!
>>We backup the same files Incrementally through the week with no error.
WHen
>>I run a Full backup at the end of the week, it fails with the above error,
>>but at different points. We have v7.2 of BackUp Exec for NT installed.
>The
>>only material relating to the above error regards backing up Exchange,
an
>>Oracle database, or the Registry on a Win9.x PC, NONE of which apply to
>my
>>situation.
>>If you find out what causes the error message, I'd sure like to know about
>>it!
>>
>>
>>"Michael Thornton" wrote:
>>>
>>>I'm on version 7.2 and I just got my first taste of this problem. I see
>>nothing
>>>in the job log that would cause me to get the "failed" message at the
end
>>>of my backup.
>>>
>>>"Derek Seaman" wrote:
>>>>
>>>>yes! I get the same messages. So far I think BE 8 is WAY to full of bugs
>>>to
>>>>use on a productional server. I'm completley unimpressed with the product.
>>>>Heck, Microsoft products work better!
>>>>
>>>>"Victor Peel" wrote:
>>>>>
>>>>>Yes, I to am geting that same 'failed' error. I have scoured the books
>>>>to
>>>>>no avail. I have posted at various sites again to resolution. Anyone
>>>have
>>>>>any idea about this? I have checked for 'skipped', 'corrupt' and other
>>>>keywords,
>>>>>still nothing has solved this. HELP!!!
>>>>>
>>>>>"Dave" wrote:
>>>>>>
>>>>>>I'm getting the following status:
>>>>>>
>>>>>>Job completion status: Failed
>>>>>>
>>>>>>but I can't see any thing wrong with job. Whats up here? Others are
>>>having
>>>>>>this problem also!!
>>>>>
>>>>
>>>
>>
>Same problem as the rest of you....has anyone called with a service contract?

"Colin Padget" wrote:
>
>Right !
>
>If anyone of you have experienced the backup job ending in a "Failed" status
>and some files were reported being corrupted etc. please check this posting:
>
>In Veritas' Knowledge Base select "BackupExec NT/2000"
>In Version select "8.0"
>In Subject select "All Subjects"
>In Search Phrase type "193940"
>
>Make sure you're connected to the US-site as the UK site is not actually
>similar. (I'm not kidding ! Honestly )
>
>If you still have problems locating the fix, please feel free to e-mail
me
>at my above address
>
>Regards
>
>Colin Padget
>"I haven't lost my mind - It's backed up somewhere"
>
>"James" wrote:
>>
>>"Neil Brown" wrote:
>>>
>>>I get an error stating "Drive is not responding. Backup set aborted" and
>>when
>>>I check the log it shows that the amount of data processed actually EXCEEDS
>>>the amount in the backup set!
>>>We backup the same files Incrementally through the week with no error.
>WHen
>>>I run a Full backup at the end of the week, it fails with the above error,
>>>but at different points. We have v7.2 of BackUp Exec for NT installed.
>>The
>>>only material relating to the above error regards backing up Exchange,
>an
>>>Oracle database, or the Registry on a Win9.x PC, NONE of which apply to
>>my
>>>situation.
>>>If you find out what causes the error message, I'd sure like to know about
>>>it!
>>>
>>>
>>>"Michael Thornton" wrote:
>>>>
>>>>I'm on version 7.2 and I just got my first taste of this problem. I
see
>>>nothing
>>>>in the job log that would cause me to get the "failed" message at the
>end
>>>>of my backup.
>>>>
>>>>"Derek Seaman" wrote:
>>>>>
>>>>>yes! I get the same messages. So far I think BE 8 is WAY to full of
bugs
>>>>to
>>>>>use on a productional server. I'm completley unimpressed with the product.
>>>>>Heck, Microsoft products work better!
>>>>>
>>>>>"Victor Peel" wrote:
>>>>>>
>>>>>>Yes, I to am geting that same 'failed' error. I have scoured the books
>>>>>to
>>>>>>no avail. I have posted at various sites again to resolution. Anyone
>>>>have
>>>>>>any idea about this? I have checked for 'skipped', 'corrupt' and other
>>>>>keywords,
>>>>>>still nothing has solved this. HELP!!!
>>>>>>
>>>>>>"Dave" wrote:
>>>>>>>
>>>>>>>I'm getting the following status:
>>>>>>>
>>>>>>>Job completion status: Failed
>>>>>>>
>>>>>>>but I can't see any thing wrong with job. Whats up here? Others
are
>>>>having
>>>>>>>this problem also!!
>>>>>>
>>>>>
>>>>
>>>
>>Same problem as the rest of you....has anyone called with a service contract?
>
I am having this same problem!
But here's a twist, I have jobs in the past that have a status of successful
even though I have 3 files in Exchange mailboxes that are corrupt, and cannot
verify.
Does anyone have a clue about that?

"Linnea" wrote:
>
>Dave,
>
>You have to check each and every drive backup log. If a file
>is corrupted then you will get a failed status.
>I also had my backup selection saying to backup N: drive but
>there was no n: drive so the status was always Failed.
>
>Linnea
>
>
>"Dave" wrote:
>>
>>I'm getting the following status:
>>
>>Job completion status: Failed
>>
>>but I can't see any thing wrong with job. Whats up here? Others are having
>>this problem also!!
>
I get the same problem with a number of jobs. The majority of the time it
is because there is/are "corrupt" files being backed up. The following are
words that you can find in your jobs log file that will
cause a job to fail.

Abort
Attach
Corrupt
Denied
Connections
Memory
Terminated
Responding
Error

When these words are found in a job log, it will usually cause the job to
fail. Realize, however, that file names of the above will not cause a job
to fail.

You can search for these words in your job log, by opening the log in any
text editor.