Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Synthetic backup error

Created: 27 Sep 2013 | 1 comment

For two nights in a row I've had a differential backup of a Hyper-V 2012 server fail. Both nights have reported lack of space which I understand and which is not the reason for my posting.

The second night produced an error which I've not seen before and I don't know what to do with.

Job ended: Thursday, September 26, 2013 at 10:18:45 PM
Completed status: Failed
Final error: 0xe0000f09 - 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.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-3849

The link takes me to a page which contains a linkable message which takes me to

This gives me the following:


This issue occurs when the Synthetic Baseline Full or Synthetic Incremental runs at the same time the Synthetic Full backup job. The Synthetic backup is not superceding the Incremental backup.



Edit the Synthetic Full Backup to run at a different time to supercede the Synthetic Incremental.

But I don't understand what a Synthetic backup is. I've checked the schedules and the server is set for backups as follows. System State every Sunday night, Full every Friday night, Differential all other nights.

Can anyone explain to me what this error and explanation are talking about and what to do about it?


Operating Systems:

Comments 1 CommentJump to latest comment

pkh's picture

1) Edit your job and check under ADBO whether the " Collect additional information for synthetic backup and for true image restore " option is enabled.  If so, disable it.

2) Check the amount of free space on the disk hosting the catalogs, usually the C: drive.  If there are insufficient space, free up some space.

3) use a command prompt and run  “C:\Program Files\Symantec\Backup Exec”  and\catrebuildindex -r”

4) Lastly,

a) stop all BE services

b) rename the Catalog directory under the BE installation directory to Catalog.old

c) create a new Catalog directory

d) start all BE services and re-run your job.

If successful, your old catalog is corrupted.  You would need to catalog your media again so that they are present in the new Catalog directory.