JET_errDatabaseDirtyShutdown after Exchange 2010 GRT backup

I have exactly the same issue, did you get a resolution?

Yesterday I installed Rollup 12 again and the Exchange backup was successful yesterday, I will check the job tomorrow and the day after to make sure.

Stil having issues, sometimes it shows successful, on other days it says failed with the same message, so reinstalling RU12 was not a solution.
I updated SBS Edition to Capacity Edition Lite, hoping that installation would replace/update certain files that is causing the issue, but that didn't help either.
The backup itself is successful, because a GRT restore is always successful, but the error is bothering me.

If running any AV, exclude it from scanning BE processes.

Sounds similar to - https://www.veritas.com/support/en_US/article.TECH224170

This may require a formal support case to be logged for us to investigate.

We have a customer receiving the same intermittent error on what appears to be the same software.

Backup Exec 15 FP3

Microsoft Exchange 2010 SP3 UR12

Microsoft Windows SBS 2011 (2008 R2)

The error last occurred during the overnight backup, I have checked all VSS Writers just now and they are all stable/no last error.

Sounds like I'll need to log a case with Technical Support, but would be very glad to hear if anyone else gets a resolution!

We're getting the same error as well over the past few weeks with a client.  Seems above is exactly what happened here too.  Any update in the past two weeks on this?  Did anyone open a case?  What was the solution?

Also seeing this on one (of many) SBS 2011 servers we manage - this backs up to a NAS, although we got (slightly less of) the failures if backing up to a local disk.

As part of our support case open for the last few weeks- we have been told the issue is likely with our Exchange Databases being corrupt. ESUTIL checks show they are not.

Very latest BEWS V15 FP3 - Clean install, not upgraded.

Circular logging is enabled as per default and very few transaction logs exist- Exchange is not heavily used at all on this server, we can find no general health issues. No VSS issues.

Disabled AV on the server for a few jobs, no change- approx 1 in 5 jobs randomly "fails", but no real consistency.

Debug logs indicate that the actual failure is at the point of the "AttachDatabase" command and this is being attached from the NAS drive/Backup Exec TEMP folder that contains the backup file. After this we then see an "OPEN DATABASE FAILED" event logged which again relates to the NAS and Backup Exec TEMP folder location.

Glad to see we are not alone here.

We have this too; same versions of BackupExec as above on an SBS 2008 server. Just as random but becoming more frequent. Did anyone discover a solution or mitigation?

Following on from my previous post, we have now had a support case open for 3 months- no conclusion on the matter to date. Just random failures and can we collect more logs.I am currently trying to get a SGMon log of a successful and a failed backup so the logs can be compared, this is easier said than done.

As a side note- I (stupidly) upgraded another SBS 2011 server from BEWS 2014 to 15 FP4 on friday. Never had a GRT dirty shutdown error before. Guess what- from the fist backup after the upgrade, it's now finising jobs with the  same failed error. 

Hi,

@Slave2BEWS. Any update from Support-Team ? I see the same error on a BE15 installaton, also on SBS2011.

Regrads Timo

PS: What will you do if your BE support will expire, because Veritas do not sell anymore support for BE 15 SBS licence.