Re: Veritas Backup Exec - Help please

Tech-Archive recommends: Speed Up your PC by fixing your registry

A better way is to change the current backup job selections via the text
version of the selections.

Depending upon the version of BE, you would either change the service
password for each BE service using the Services MMC, or you would do it from
within BE.

Gregg Hill

"kcdspike" <kcdspike@xxxxxxxxxxx> wrote in message
news:%23TelKkojGHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
I can confirm from experience with this Backup that if directory that
existed when the backup job was created, is then deleted (for any reason)
this error occurs. The only way to "fix it" is to redo the job and not
select the now deleted folder.


"David Smithz" <dave1900@xxxxxxxxxxxxxxxx> wrote in message
news:0Qnjg.85127$wl.29317@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi there,

Having taken over maintenance for a SBS 2003 server I notice it is
running Veritas Backup Exec and has a tape drive built in.

I have continued using the schedule that was in place and do which once a
week makes a full backup. But I notice that the report at the end
actually fails. In fact the top of the report says

Error category : Resource Errors
Error : a000fe09 - The directory is invalid.

Btu looking through the majority of the report for all the important
parts it seems to say complete. But as the overall job has the status
"Failed" and shows up in big red, it makes one think that none of the
backup has been complete.

Is this the case, or can someone confirm, that even a minor error on a
backup job will result in the whole job showing failed, but in fact the
majority of files have actually been backed up.

OK that's problem 1. Problem 2 may even be a bit more complicated. When I
cam to the backup server it was not running properly as it did not have
permissions to start services or something. I got round this by changing
the properties for each of the services associated with Backup Exec and
changing the "Log On" to "Local System Account". Then I would log in as
administrator and start jobs manually.

When the services were set as a specified account for which one could
type in details, even though I typed in the administrator details, the
services still failed to start when running Backup Exec with the log
indicating a permission problem/

Any input here is very welcome, as I while I do think I am creating a
useable daily backup, it would be nice to get it all automated and be
happy it is working exactly as expected.

Thanks







.

Relevant Pages

  • Veritas Backup Exec - Help please
    ... Having taken over maintenance for a SBS 2003 server I notice it is running ... Veritas Backup Exec and has a tape drive built in. ... But I notice that the report at the end actually ...
    (microsoft.public.windows.server.sbs)
  • Re: Veritas Backup Exec - Help please
    ... existed when the backup job was created, is then deleted ... Veritas Backup Exec and has a tape drive built in. ... But I notice that the report at the end actually ... in details, even though I typed in the administrator details, the services ...
    (microsoft.public.windows.server.sbs)
  • RE: Loss of error reporting and Intranet web site
    ... email from the server a couple days ago but there was no data in it, ... Any idea why it might have done this if Exchange has to be on ... DAT tape backup and it still was seeing way too much data in Exchange ... Select Receive a daily performance report in e-mail, ...
    (microsoft.public.windows.server.sbs)
  • RE: Loss of error reporting and Intranet web site
    ... Monitoring and Reporting, Companyweb, Backup problem. ... You said you removed Exchange from the server due to not enough backup ... Exchange mailbox and public store to another location. ... Select Receive a daily performance report in e-mail, ...
    (microsoft.public.windows.server.sbs)
  • RE: NT Backup Started but hasnt finished yet?
    ... If yes, as we know, the 'Collect Server Performance Data' scheduled task ... Performance Report, this report created on 25/05/2006 at 6:00 AM. ... However, the SBS Backup is running and not yet finish before 5:08 AM, so ...
    (microsoft.public.windows.server.sbs)