EDB file

[amirwhite]

Good afternoon,

Exchange Server 2010 SP2

Situation following, there is a small database of 15 GB. She was unmounted EDB file and treacherous been deleted. There is also a log file from the first day of life base, completely, not damaged (15 GB).

Is it possible to get data from log files back?

I will be grateful even for the tips.

 

[expat_mike]

same text here http://forums.cloudclan.org/topic/1639-edb-file/

so beware https://www.youtube.com/watch?v=anwy2MPT5RE

 

[hybridauth_Google_106566899134309438995]

EDB to PST converter software is the advance way to repair and recover EDB file and convert EDB to PST file from exchange server. It entirely retrieves data from Exchange server and transfer to Outlook PST file format with one shot. EDB to PST converter program works on all Exchange versions and easily recover EDB to PST. It let you to read corrupt Exchange database and save EDB in PST file within second.

Get more information :- http://www.tools4recovery.com/edb-to-pst-converter.html

 

[spiny norman]

<SNIP>

Other processed meat products are available.

 

[xexysus361]

If your exchange database has a usual problem, but if your database is severely corrupted, then apply more powerful methods

http://itknowledgeexchange.techtarget.com/itanswers/trouble-reading-files-error-523-service-transaction-error-in-exchange-2007/
http://forums.msexchange.org/m_1800598776/mpage_1/key_/tm.htm#1800598776

1) Copy all the original database and log files to somewhere safe. Then also copy them into a working directory. Eseutil will modify the files in situ so if it goes wrong you don't want your original files modified.

You need to have a copy of the database files (*.edb and *.stm) plus the transaction logs (Exx*.log where xx is a number relating to the information store). The location of the files is available from exchange system manager, but you really should know where they all are anyway.

I'm going to assume the temp directory for the database files is e:tempdata and they're called exchdb.edb, exchdb.stm. If they reside in the 1st storage group, the transaction logs will be called E00.log (this is the most recent base file) and E00xxxx.log etc (these are the old logs). Lets assume these are copied to e:templogs. You need to replace these with your own paths/filenames of course.

2) Check the database state and expected log files with

eseutil.exe /mh e:tempdataexchdb.edb

The output will show a line State: which will be either clean or dirty shutdown. If it's clean, then you don't need this article

It will also show which logs are required e.g. which hadn't yet been played into the database when the dirty shutdown occured. If you have any missing then you will have lost email. This generally only occurs if you lost a log drive and have replicated copies of the logs you can use.

3) "Recover" the database. This replays missing transaction logs into the database file - run:

eseutil.exe /r E00 /d"e:tempdataexchdb.edb"

You might receive an error that there is an outstanding database attachment. In this case use the /i switch in the command

eseutil.exe /r E00 /d"e:tempdataexchdb.edb" /i

4) recheck the database state with the command in 2). If it still shows dirty shutdown you need to repair the database with:

eseutil /p e:tempdataexchdb.edb

5) Recheck the database once more and it should show clean shutdown. At this point you should defrag the database

eseutil /d e:tempdataexchdb.edb

6) The file is now in a clean state and is ready to be put back into exchange so copy it back to the original location on your exchange server but don't yet mount the file. The last step before mounting the file is to get rid of any remaining errors using isinteg.exe. This tool requires the database to be in the original location on the original exchange server. It needs to be run several times until it no longer reports any errors.

7) Once the database file has no more errors you can now remount it in exchange.

USING HARD RECOVERY
eseutil /r /a e00 /d "Crogram FilesMicrosoftExchange ServerMailboxFirst Storage Group" /s "Crogram FilesMicrosoftExchange ServerMailboxFirst Storage Group"

Then

eseutil /p "Crogram FilesMicrosoftExchange ServerMailboxFirst Storage GroupMailbox Database.edb"

Where "Crogram FilesMicrosoftExchange ServerMailboxFirst Storage Group" and "Mailbox Database.edb" were the names of my database directory and database file respectively.

The first, recovers the database from the existing log files and the second performs a repair on the database for inconsistencies.

 

[spiny norman]

<SNIP>

Thanks for that, really is interseting and sloved my prolbem. Now, do you has a similar solution for websites unabe to make their spam filtering workproperly, or a link to some mod-finder software? Thank you.