Does anyone know what this means? I think it is haivng trouble reading the logs from the Local Copies folder of one of the mail stores/databases. Do I need a "Local Copies" folder on top of the regular database folders? Microsoft.Exchange.Cluster.ReplayService (4572) Recovery E02: Unable to read page 966174 of database D:\Program Files\Microsoft\Exchange Server\Mailbox\LocalCopies\Third Storage Group\Sales Database.edb. Error -1018.

What version of Exchange? Are you using LCR? Or did you run LCR at one time? Anyway, -1018 errors are almost always caused by faulty or crummy storage subsystem hardware.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

I always forget the essentials here. I am using Exchange 2007. I am using LCR on my storage groups (that's the only way to mount them right??). When you say storage subsystem hardware, you mean say like a RAID controller, etc...? When a failing HDD fall under that category as well?

Mount what? LCR keeps a second copy of your database on the same server based on log shipping (storage group copy), offering some protection against corruption. If you're not familiar with what you have and what the benefits are, you really ought to read up on the subject. Storage subsystem hardware definitely includes both of those, yes.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Well, for some reason, maybe I am mistaken but I had to enable LCR in order to create and mount my database(s). Do I not need this? And yea, I am quite novice with Exchange. I've always been into PC repair, not server administration. Much less Exchange. Learning as I go along here. As for the subsys HW, I just replaced the RAID controller (which was my main problem to begin with). Since I was given, had to install a refurb card, could it be anything else other than the HDD. Or could the RAID card still not be functionally 100%?

LCR is not required to mount a database. LCR is a database redundancy feature that I don't believe was widely adopted largely because it doesn't scale. In fact, the feature was dropped from Exchange 2010. Like I said, -1018 errors are almost always caused by faulty or crummy storage subsystem hardware.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."