Database down

[kzn]

Hi

Any help or advice appreciated. We have been using Mcafee Total protection for about 4 years now and it has never caused a problem with our mail server ... never a need for exclusions like Group shield this was confirmed when we purchased Total protection.

Today Mcafee decided to quaratine one of the log files and since then our database has been down. I moved the file back but the database wont mount.

The problem is last nights back up did not complete due to this error so that means if I will lose a day and a bits worth of mails. The users do have cached copies so I am busy extracting them to pst files, some people dont have cached mails.

I have run the eseutil program and it has confirmed the database is in a dirty state. I ran the hard repair of Eseutil /cc. It said it successfully repaired the database but it still wont mount. Should I delete the log files? I did make a copy of the MDBDATA folder before trying this.

Back up from tape is an option but would mean loosing some data so at the minute I am wait for most the extractions to pst files.
Any help appreciated.

Thanks you

 

[58sniper]

Not sure I understand why that would happen. Log files are after the fact. Data isn't read into a database from a log file unless the database is doing log replay as the result of either dirty shutdown, or log shipping as part of a DAG.

There has ALWAYS been exclusions required for Exchange. I don't care what AV product you're using. Exclusions have been clearly documented. See

http://technet.microsoft.com/en-us/library/bb332342.aspx

Have you run isinteg after the repair?

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.exchangeblogs.com/

 

[kzn]

Thanks for the reply, no I have not run isinteg yet, should I delete all the files and just leave the edb file and then run isinteg?

Regarding the exclusions, that is exactly what I thought and that is the reason why I contacted Mcafee and spoke to one of there so called professionals who reassured me that was the case with groupshield but was not necessary on the new Total defense product. I am just so p***** with myself because I should have not listened and done it anyway, but cant do anything about that now and need to concentrate on the problem at hand.

Prior to running the command I mentioned earlier I made a copy of the MDBDATA folder

Thanks again

 

[58sniper]

Don't touch the log files. Run isinteg anytime you run a full repair on a database (which I can count on 1 hand the number of times I've done it in 15 years).

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.exchangeblogs.com/