Forum Discussion

HansMeiser's avatar
HansMeiser
Level 3
6 years ago

BE 20.6 Jobs fail - could not write to database

Hello Vox Community!

For a couple of days, BE 20.6 Backups fail. The given error code is 0xe0000f09 - an error occured writing to the BE Database. The error message links to a KB Item V-79-57344-3849 - which cannot be found.

Googling for these messages, it seems the error is related to incremental Jobs which somehow overlap the Full Backup, at least to my understanding. But we only run full backups every night, no incrementals at all.

Are there any other issues that may cause the error? How to troubleshoot? The job is one we use for years, and the databases have not changed recently. What changed lately was a small BE update to be applied to both the BE Server and the remote servers thru the live update function.

20
Backup Exec
Windows Server 2012 R2

9 Replies

Sort By
  • ManojNisal's avatar
    ManojNisal
    Level 3
    6 years ago

    Hi HansMeiser,

    Whenever a job fails, a couple of debug log files are generated in the "<product install>\Logs" directory on the Backup Exec server.

    Can you check the failures/errors printed in the debug log (towards the end) generated for bengine and paste those errors here?

     

    • HansMeiser's avatar
      HansMeiser
      Level 3
      6 years ago

      Hi ManojNisal

      Thank you for your reply. I am not exactly sure which parts you need, there is a good amount of logs from today. There are 6 files named SERVERNAME_bengine_AlwaysOnLog_DATE.log for a total of 15 MB, and maybe another 20 logfiles which have changed today.

      I am going to restart the server and have another go at the backup tonight. If this doesn't help, I will dive into the logs to see what I can find.

      • ManojNisal's avatar
        ManojNisal
        Level 3
        6 years ago

        Hi HansMeiser,

        Whenever a job fails it will generate a file with name like SERVERNAME_bengine_AlwaysOnLog_DATE.log along with few other files. So you can match the timing of any backup job failure (with error could not write to database) with the timestamp of bengine log file.

        By the way, you mentioned you run full backups everyday. By any chance, is the expiry of these backup sets set to 24 hours?