My Exchange 2007 store ran out of space and the stores dismounted. This is on a CCR cluster. After expanding the volume I brought the mailbox db up. I backup up the databse with DPM 2007. After the backup the log files aren't deleted. On the target node, which is also the node being backed up, I see these events: Microsoft.Exchange.Cluster.ReplayService (2300) The surrogate backup procedure to MBX has been successfully completed. The Microsoft Exchange Replication Service VSS writer (instance 46a3ea35-c95a-4ac4-981a-2be339853fc8) has successfully completed the backup of storage group 'First Storage Group'. Database log truncation has been requested for this storage group. Log truncation will occur on the active copy after the next log generation is created. Log truncation will occur automatically on the passive copy after that log file is copied. On the active node I see these event: Information Store (2236) The surrogate backup procedure has been successfully completed by MBX. (error, source ESE, Event ID 214) MSExchangeIS (2236) First Storage Group: The backup has stopped with error -521. I doin't see any other events after that relate to the log files. As always I appreciate any suggestions. Thanks, Andy

Should I just enable circular logging and then diable it? Can anyone help with troubleshooting a log file issue?

I dismounted the database and verified that the required log is 0 so I'm moving all the log files (186 gigs) to temporary storage. When the files are moved I plan on mounting the store and doing a full backup with dpm and hopefully everything will work correctly. Is this a good or bad idea?

after backup completed have you been able to mount the database ? if you are able to then next log will be generated and logs will be purged if you do what you said in previous post.. you may need to reseed as log generation will changeDhruv

Hi, Does the issue happen to other storage groups, or other exchange servers after the backup? At this stage, please run “VSSAdmin List Writers”, and verify if the status is stable and no error. Also, please update to latest service pack on the exchange server. If the issue persists, I suggest you refer to the thread to troubleshoot the issue. Regards, NovakPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I dismounted the database, ran eseutil /mh "database name" on the database and verified the the log required value was "0", meaning all transactions were committed to the database. I then moved the log files to another volume. I didn't delete them in case of some unlikely failure. I also could have zipped them and deleted the log files. In this case it was faster to move them and I had SAN space to create a temporary volume to hold the log files. Server 2008 had a hard time even displaying the folder that contained the log files so I used the command move E000*.log in a command window started as administrator. Once the log files were moved I mounted the database and run a backup with dpm. Things seem to be running normally now, thanks for the help.

I take this back, it looks like the log files are still not being deleted after I run an express full backup from dpm. The output from “VSSAdmin List Writers" looks like this for each writer on both ccr nodes: Writer name: 'Cluster Database' Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e} Writer Instance Id: {d72a8b17-c1b0-4d5e-9c0c-2c7bce645984} State: [1] Stable Last error: No error I still get this error on the CCR master application log: MSExchangeIS (2236) First Storage Group: The backup has stopped with error -521. I should add that in DPM the protection status is listed as OK. The replication status is healthy for each storage group.

Do One thing ! Just run NTbackup (streaming) for one database and see log should e purged. Then try to take VSS backup thru DPM and test it.Anil

After searching around on that error -521 I found this article which says that VSS backups work from the backup perspective but throw that error and the log files aren't truncated. http://support.microsoft.com/kb/2297394/ So it looks like I didn't notice this after I updated to sp3. I installed rollup 1 for sp3 and the error was gone but the logs still weren't turncated due to the logs I removed. I restored the log files I removed (I had just moved them to a temporary volume (NEVER DELETE LOG FILES!) and ran a backup from dpm and the logs were truncated normally. -1 to MS for bad SP! Thanks for the help.

Nice to see Andrew you fix your issue, Now i remember that Exchange 2007 SP3 has a bug for not supporting VSS backup from passive node in CCR. To temp fix this issue microsoft released one interim update till they launch RU1 of SP3. Its looking now they have corrected this in RU1 of SP3. :)Anil