I have Exchange 2003 with 4 mailbox store I have some thing wrong with my Hard disk so my EDB files and STM files are not working " I can't attached them and can't repaire them with eseutil " My Buckup was in the same Hard disk with EDB so it's corrupted too but fortunately I have a copy off edp and stm files in another Hard so now I have 4 EDB Files with their STM files (old one) and I have all Log Files uptodate from the time of this files are copied until now, so how can I Migrate the data between the edb file and Log files to make the edb files uptodate Note my edb file are in dirty status

When the EDB file is in a dirty state, the eseutil /mh databasepath.edb will tell you what log files are needed. When you have those log files in the proper place, you can run eseutil /R to replay the log files into the database to put it into a clean state.MVP | MCSE:M | MCITP: Enterprise Messaging Administrator | MCTS: OCS + Voice Specialization | http://www.shudnow.net

Thanx bro So can I use eseutil /r after I use eseutil /p I use eseutil /p and my EDB files are know in clean status so only I need to replay Log files on the EDB files

No, you can't. The database is essentially a new database. After running eseutil /p, you want to run eseutil /d to do an offline defragmentation and then run Isinteg –fix –test alltests. You then remove all the existing log files and checkpoint file and a new log stream including a checkpoint file will be created.MVP | MCSE:M | MCITP: Enterprise Messaging Administrator | MCTS: OCS + Voice Specialization | http://www.shudnow.net

A few things here; If you attempted a /P against the EDBs on the same server where the problem occurred it will definitely fail because besides the obvious reasons that the disk may be bad, it could also be the motherboard, memory or disk controller thats causing the problem and a /P would cause a serious stress on all of those systems. If you have the original EDB, STM and Log files that were in place before running a /p you can try to get the data by first moving the files to a new system and then use a third party tool like Lucid8's DigiScope http://www.lucid8.com/product/digiscope.asp to extract the data So short story get the files off the original Exchange server ASAP. Unless you know what the exact failure was caused by I would try to avoid running the new databases on that same server or you may face the same issue again. Also your backups may be good as well, i.e. if you restored them to the same server and tried accessing them it could just be that you are on a bad system so try restoring the files to a completely alternate system and you may have a better chance of recovering the data