In our Exchange 2007 environment we have 2 active CCR nodes, there is a log file located at c:\data\SG$4ogs named E0B000B9C44..... OR IS THERE!!!! it says the culprit is 1,024 k... so ok, it's a meg, so when I click properties it says it's 0 bytes ....weird. So I try to open it in notepad since its a log file because thats what mommy's and daddy's say we should do in addition to brushing our teeth and saying our prayers ..."Cannot find the blah blah blah.log file. Do you want to create a new file?" OK, I'll play. So I type in a few characters of text and save it. Delete said file and voila.... it's gone... until tomorrow morning when it rises from the grave like the undead (Romero would be proud). Now we're going to try to take it offline and see if that will make a difference, but in case it doesn't, does anyone have any stakes, silver bullets, garlic, wolfsbane, talismans or whatnot that could blow this bugger all the way to silicon heaven?Unified Communications Engineer

Is the log on both nodes? There can only be one active node at a time, so Im not sure which one has this log.

Just on one node. Not available on the other. Lets call them... Patty and Selma. The log file is on Patty, but not Selma. Unified Communications Engineer

Just on one node. Not available on the other. Lets call them... Patty and Selma. The log file is on Patty, but not Selma. Unified Communications Engineer It could be the backup program is somehow holding on to it. I assume you dont have flat-file anti virus scanning any Exchange dirs or processes. Is this the passive or active node?

Patty is the Passive node, Selma is the active one. The short of it – backups are failing, and unable to truncate the logs for a storage group due to a single log file on 1 of 2 nodes in an Exchange 2007 cluster which is either corrupt on the file system, disk, or information store?? Level. We are using Data Protection Manager 2010 to protect all Storage groups in the cluster, and the VSS operations are failing for this single storage group because they see the Log file, but when it requests it, it cannot be found. Manual manipulation of the log file shows it in Windows Explorer, access to the file responds that the file cannot be found – would you like to create it? The file can be created, modified, and then deleted. At which point, the same file is displayed in the windows file system. Open, cannot be found, create, modify, save, delete, Refresh and the file is back. Eseutil /ml -- fails because the log file cannot be found. And when manipulating the file, creating and adding random text into it, eseutil is able to recognize the file on the disk, but cannot read it since it is not an actual exchange log. A key note to DPM – it does not have this issue with the same storage group on the other node, and all other storage groups are being successfully truncated and backed up. DPM is pointing out that the system (exchange host OS) cannot find the file specified. Unified Communications Engineer