Hi I wondered if someone could help me with this annoying issue. I had an issue with one of our clients' HP servers where one of the logical partitions suffered a multiple failure and they lost their Exchange databases, after replacing the disks and recovering the Exchange data using Windows Server Backup restoration process everything appeared fine except I couldn't mount the second storage group which contained the public folders, so I ran an eseutil /p to repair the store which worked, I then mounted the store and everything was fine.
The issue that I have now is that when the Windows Imaging Backup runs of a night time one of the Exchange log files E01.log gets flagged up as being in an inconsistent state, yesterday I dismounted the store again and ran lots more tests on it and everything was fine and I was happy that the store was in a clean state. I now want to know what I can do with this log file so it does not get flagged as being dirty. I have tried renaming it but when I mount the store it will not mount. Is there anything I can do to prevent the backup failing with an inconsistency just because this log file appears damaged?