having a problem with backups of an Exchange 2007 SP1 public folder database. using BU Exec 2010. odd thing is the logs are getting truncated. it could very weill be a BU Exec problem but during the shadow process, I see the following error: Log Name: Application Source: Storage Group Consistency Check Date: 9/27/2010 11:01:22 PM Event ID: 200 Task Category: Database Header Validation Level: Information Keywords: Classic User: N/A Computer: WAS-E-W-V01 Description: Instance 2: Database headers have been successfully validated. All databases are in a dirty shutdown state. To bring these databases to a clean shutdown state, log generations 107369 (0x0001a369) to 107369 (0x0001a369) will be required. is instance 2 the shadow? also, I tried to run eseutil, does the database have to be unmounted? E:\Exch\Bin>eseutil /mh "f:\exch\mailbox\second storage group\public folder data base.edb" Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Error: Access to source database 'f:\exch\mailbox\second storage group\public fo lder database.edb' failed with Jet error -1032. Operation terminated with error -1032 (JET_errFileAccessDenied, Cannot access fi le, the file is locked or in use) after 20.46 seconds. E:\Exch\Bin> thanks

Your Databse is in dirty shutdown state so backup is getting failed ! for run successfull backup you have to clean shutdown database and then mount it and run backup.Log generations 107369 (0x0001a369) to 107369 (0x0001a369) . You can pick these logs from backup to sommit it into database. Reference for Common Eseutil Errors:: http://technet.microsoft.com/en-us/library/aa996759(EXCHG.80).aspx The Exchange database store may not mount in Exchange Server, and event IDs 9175, 486, 455, 413, and 5 may be logged:: http://support.microsoft.com/kb/896143Anil

which database is dirty, actual or shadow copy? and I dont have any of those other events.

Ohh , Please disregard my above comment ! Anil

so I ran the failed backup again, manually, it ran fine.