Video Screencast Help

BE2012 keeps crashing for no reason, huge BEX*.XML Files (45GB)

Created: 03 Oct 2012 • Updated: 03 Oct 2012 | 2 comments
This issue has been solved. See solution.


i have some jobs running for ever and the complete backup chain is not working anymore.

Most of the time, the backup exec engine is not responging anymore, even a restart of the service doesn´t work.
I always need to kill the engine.

In this situation i always found huge BEX*.XML Files in the symantec backup exec subfolder.
the last one had 45GB, 9GB, 5GB ... in size.

With these files in place it´s not possible to restart the services.
After i move these files to a tmp folder, everything looks fine.

I had 2 cases open, but symantec wasn´t able to find the problem at all.

Anyone with more information for this obvius bug?

Comments 2 CommentsJump to latest comment

Jaydeep S's picture

These seem to be the job logs for the jobs that you run. In Backup Exec 2012, Click the Bacup Exec icon on the top left, Click Configuration and Settings -> Backup Exec Settings

1. In the job log tab make sure that the Information to include is set to Summary information only. More the details you set to capture the larger will be the file. You could also change the path where the files get created from here.

2. In the same window in database Maintainance Tab, you can set to auto truncate these files.

As for the service crash is your Backup Exec fully patched cause there was an old known issue about BE services crashing which was fixed in SP1a and following hotfixes.

JuergenB's picture


normal Log Files are 0.5MB in size.

The huge job logs are created if the engine crahes.
The system is fully patched with all available BE 2012 fixes.

The huge file comes from crashed BE service (period).