I have Exchange 2007 running on 2003 R2 x64. My problem is that the public folder transaction logs are not being deleted after a full backup. As a background, LCR was enabled on this Storage group but in a suspended mode. After reading several posts and threads about LCR and the transaction logs i disabled LCR and ran a full backup, logs still remain. Circular logging is not enabled. The other 3 mailbox storage groups successfully delete the logs after the full backups. I dont get an event916 in the event log for the Public folder SG, but i do get a backup successful event. We run differential backups daily and once a week on the weekends we run the full backups.Does someone have some insight on this issue, or some steps i can try to resolve this issue. Thanks in advancefor all the help.

ensure that there is no replication still enabled on the storage group using get-storagegroupcopystatus

All Storage groups are showing disabled after running that powershell command.

Hi, The replication feature in LCR guarantees that logs that have not been replicated are not deleted. So for this issue, please check if the copied log file has been moved to the storage group copys log path and replay the copied log into the copy of the database. How to Verify a Local Continuous Replication Copy http://technet.microsoft.com/en-us/library/bb124416.aspx How to View Local Continuous Replication Configuration Settings http://technet.microsoft.com/en-us/library/aa997697.aspx Regards,Xiu

Xiu,I have disabled LCR, preivously the Storage group had LCR enabled but it was in the suspend state. There are logs in the LCR location, do i need to copy those to the Storage groups log location, then when a full backup is run it will purge correctly?

Hi,1. I'd like to know if you have any replics on Public Folder.2. Where do you make backup,on source or target?3. What is the backup tool?4. How many DCs in your environment?Please ensure that the DC replication has been in the health state.Besides,since LCR and public folder replication are two very different forms of replication built into Exchange. Due to interoperability limitations between continuous replication and public folder replication,if more than one Mailbox server in the Exchange organization has a public folder database, public folder replication is enabled and public folder databases should not be hosted in a storage group that is enabled for LCR.Planning for Local Continuous Replicationhttp://technet.microsoft.com/en-us/library/bb124704.aspxRegards,Xiu

Xiu,1. There are no replica's on the public folder from what i can tell2. Backup is run from the target machine for the backup.3. We are using NTbackup as the backup tool.4. We have 5 DC's in our Enviroment. 3 located in different sites than the Exchange Server, the other 2 are local to the Exchange ServerWe dont want LCR, and we do not need any replication. We are just trying to get full backups to clear out the logs as expected with NTbackup for exchange.Thanks for your help in this matter,Stephen

it's possible these logs aren't even needed anymore and are "stranded". I've seen several instances in the past where logs get left behind (for whatever reason). Unfortunately the only way to see if they're needed is to do an eseutil -mh and check the logs needed, but you have todismount thedatabase for that (in which case it should commit any logs it needs to anyway and you should get back a 0-0). NOTE: If you have multiple stores in that storage group then you'd have to do this on all stores, not just the pf store, since logs are per storage group and not database. Only then could you be sure that you can manually remove those logs.

This is a wild guess, but try to dismount the public folder database and then remount it.Jim McBee - Blog - http://mostlyexchange.blogspot.com

I have manually deleted all unnecessary logs about a month back, did a full backup, and checked the event log to see the last commited log file. NTbackup does not even log a 916 event for that storage group to say that it deleted logs exxxxxxxxxxxx-exxxxxxxxxxx. I have not simply unmounted and remounted the DB, i will try that after hours this evening, while i am at it i will run the eseutil -mh. This morning i read some MS documentation that states to delete all the LCR info manually after disabling it, which i have also done, and ran a full backup, same results, i have about 3GB of log files for the public folder SG. This is the only DB in the SG also.

I know it has been a while, but still facing this problem. I have dismounted the store and run the checks. Remounted the store, performed full backups. Still have logs dating back to june in the log folder. Now up to 11GB of logs, while there is no space issue yet, in the future there will be. Any other things i can try.