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.
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.
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?
Thank you @ManojNisal
The job failed again at 07:38 this morning, log as follows:
The expiry of the job is set to 3 hours, in case I forget to swap the RDX tape so it could be overwritten. Usually, the tape is changed daily with 5 tapes in rotation for the week.
Unfortunately, the only thing that changed with today's job is that the verification job completed succesfully - which it didn't after the failed backup jobs of the previous days.
I was suspecting this to be a case of backup set expiry happening while backup job was in progress. However, from the available information I don't think that's the case.
As this would require more detailed troubleshooting, I'd suggest opening a case with support.
Thank you for your pointers. I will create a ticket with support.
Currently, I am debating with myself if I should try to create a new BE database over the weekend to see if that fixes the issue, as the error messages point to database problems. This article makes me believe that should be a quick process: https://www.veritas.com/support/en_US/article.100015393
Hi. So far, the issue is still there. I am in touch with Support thru a ticket. It is not their fault that this is still unsolved, they are very helpful. I just don't have the time at the moment to reply in a timely manner.
Basically, the first approaches failed. We are now trying to use an empty database to see if that works - and then would reinstall the original DB. They have advised a couple of other things I should try after that, and will collect some data to further investigate the issue.
I'd recommend to open a ticket yourself. I can update here, I am just slow due to having to deal with the Corona-situation currently.