Hey,Ive files from our old exchange 2003 server (edb,stm, logs...chk) and i want to add them to my new exchange 2003 server...What do i need to do to make its happen...?Thank you.

Hi MagiclogTo recover an Exchange database, please ensure the new Storage Group and Stores have same name as backup1.Dismount the new databases both mail store and public store2.You can copy these files to corresponding roots or certain roots:For example,C:\Program Files\Exchsrvr\mdbdata\prib1.edbC:\Program Files\Exchsrvr\mdbdata\prib1.stmC:\Program Files\Exchsrvr\mdbdata\pub1.edbC:\Program Files\Exchsrvr\mdbdata\pub1.stm3.Change the Properties on New database to can be overwritten by a restore4.Mount the new databaseMore Info,http://support.microsoft.com/kb/555603/en-usThanks,Any updates?Bobo

After i mounted the database i got an error, which said that the database is corrupted... any idea?

HiPlease follow this steps in link,http://support.microsoft.com/kb/823016

I still get the error that the database is corrupted...

Well if Exchange DB are corrupted you are NOT in a good situation:Exchange includes two very sophisticated utilities that came to my rescue: Eseutil and Isinteg.Here is how to repair an Exchange database that won't start:1. Make a copy of the database files before you repair them. (cause you never know)If you're not sure where your database files are, or what they are called, you can find out in Exchange System Manager by accessing the database properties. The Database page lists the paths and names.2. Verify that you have sufficient disk space to do the repair. As a general rule of thumb, you should have the equivalent of 20% of the database size. If you don't have that much free space on the drive where the database files are, you can use command line switches to redirect the temporary files created during repair to a different drive.3. Run Eseutil in /P (repair) mode.The easiest way to do this is to have both database files (.EDB and .STM) in the same directory (which they usually are). If they're in different places, you're going to have to point to the files on the command line.Eseutil is located in the \exchsrvr\bin directoryExample:eseutil /p c:\exchsrvr\mdbdata\db1.edb /sd:\exchsrvr\mdbdata\db1.stm /te:\temp.edbThis command line will repair DB1.EDB located on C: along with its matching .STM file located on D: and will put the temporary file on the E: drive.If your streaming database file (.STM) is not matched to the database file (.EDB) or it has a problem that is blocking repair, you can add the /i switch to the repair command line. The /i option ignores the signature mismatch error in the check phase. The database and streaming file will receive new signatures in the repair phase.Repair can take a while--hours. When it finishes, it will leave you with a very detailed log file of what it did called .integ.raw.Not quit finished yet, there are two more steps to complete.4. Run Eseutil in /D (defragment) mode.Repair may leave index and space allocation problems in the database. Along with compacting the physical size of the file, defragmentation rebuilds the indexes and space trees.To defragment the database, you need space equivalent to 110% the size of the database.As with repair, you can redirect the temporary file to a different drive if necessary, but this will take considerably longer.5. Run Isinteg in -fix -test alltests mode.Note: when you run Eseutil, you can move database files to temporary locations to make repairs. But to run Isinteg, you must put the database back in the location from which it is normally mounted.At the end of an Isinteg fix run, you will probably see hundreds of warnings. This is normal as Isinteg was originally created as an internal test utility. Just make sure that at the end of a successful Isinteg run, you have zero errors reported. If there is even one error, you should run Isinteg again.If a few runs of Isinteg do not decrease the error count down to zero, then you should not rely on this database in production. You should move mailboxes from it.Some say you should expect to spend an hour per gigabyte of data to get through the whole repair process.6. It is now safe to go home and get a heart attack :) JKFreddy @ Advanced Agile Technology LLC www.advancedagile.com

after i ran the deframent mode , from 5giga its became 4mega... whats going on ?? and when i tried to mount database i got a new error... " An internal processing error has occurred. Try restarting the Exchange System Manager or the Microsoft Exchange Information Store service, or both. ID no: C1041724 Exchange System Manager " and i read about this problem and they said i need to free some space, but ive more then 40giga available. any idea? thx.