Clicky

The full text of the error is:
e0000f09 - An error occurred when writing to the Backup Exec database. A synthetic backup of this resource will not include the data backed up by this operation until the next full or incremental backup of this resource.
For additional information regarding this error refer to link V-79-57344-3849

Things I've already tried:
  • Checked that I have plenty of free space on the disk holding my catalogs.

  • Renaming the catalogs folder, and restarting the backup exec services.

  • Running a database repair with BEUtil.exe

  • Fully reindexing and recataloging ALL tapes.


I'm just not sure what else to try. Any help is greatly appreciated!

asked 12/07/2011 05:02

zacharyalexstern's gravatar image

zacharyalexstern ♦♦


11 Answers:
It could be a permissions/security issue.  Make sure the user ID you are using for Backup Exec has full Admin rights to the folder and subfolders where Backup Exec is installed.
link

answered

Patmac951's gravatar image

Patmac951

Patmac951, I've already made sure of that. No luck, unfortunately.
link

answered 2011-12-07 at 13:10:08

zacharyalexstern's gravatar image

zacharyalexstern

How long has BE been installed on this computer?  Is it a new installation or did you upgrade the BE version recently?
link

answered 2011-12-07 at 13:31:44

Patmac951's gravatar image

Patmac951

Also when you renamed the Catalogs folder I am assuming you created a new folder with the proper name?  Another to check would be to make sure your Default Domain group policy on your domain server does not have any Disk quotas in place for the BE user that runs the backup.
link

answered 2011-12-07 at 13:58:17

Patmac951's gravatar image

Patmac951

It was migrated from an older BE Media server a few months ago. It's been working fine (mostly), since then.

I'm sure I've installed hotfixes in the past few weeks, but nothing extremely recently.
link

answered 2011-12-07 at 14:03:31

zacharyalexstern's gravatar image

zacharyalexstern

Yes, I created the new folder with the correct name and made sure it properly inherited permissions.

There are definitely no disk quotas. Any policy changes would have been made by me, and I also created the backup exec user.
link

answered 2011-12-07 at 14:03:35

zacharyalexstern's gravatar image

zacharyalexstern

This is a head scratcher.  Does this happen with every backup job?  For testing purposes if you create a completely new backup job does it still give you the error?
link

answered 2011-12-07 at 14:05:03

Patmac951's gravatar image

Patmac951

It doesn't happen with our "Full Exchange Backup" or normal "Full Backup" job. The former backs up exchange, as it says, and the latter backs up our file shares.

It's happening with our exchange Incremental and Differential backups and our normal Incremental and Differential backups.

I have recreated the Incremental Exchange backup job, and it still happens with that, so it seems to be limited to non-full backups.

I agree, it is a head scratcher. Been trying to fix this for days now.
link

answered 2011-12-07 at 14:24:30

zacharyalexstern's gravatar image

zacharyalexstern

I should also add that during the jobs that fail, we also see "An error occured writing to the on-disk catalogs."
link

answered 2011-12-08 at 12:14:27

zacharyalexstern's gravatar image

zacharyalexstern

I've resolved the issue.
Some of the backup exec agents were running as the backup exec user, when they should run as local system. Also, the backup exec user was missing certain rights.
link

answered 2011-12-08 at 12:36:18

zacharyalexstern's gravatar image

zacharyalexstern

It fixed the problem.

link

answered 2011-12-13 at 10:52:00

zacharyalexstern's gravatar image

zacharyalexstern

Your answer
[hide preview]

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Tags:

×33
×19
×2
×2
×1
×11
×2
×3

Asked: 12/07/2011 05:02

Seen: 1328 times

Last updated: 12/17/2011 05:20