deleted latest log file while delting extra logs manually

[Mike]

Need to replace an E0***.log that the system was using to
keep place, that was accidently erased when removing older
logs manually, system cannot go online at present.

Exchange 2000 latest service packs

[Mark Arnold [MVP]]

The log files are numbered and checkpointed so you can't
just get a log file and name it to the one that you think
is missing. Can't you undelete it or use Emergency
Undelete etc if you can't restore from backup?

>.
>

[Mike]

Emergency undelete???

Please Explain.

>.
>

[Richard Chen[MSFT]]

Hi Mike,

Mark means some tools that can read the deleted files from the disk like
the Norton Unerase. However, if the disk sectors contain the log file were
overwritten with other files, they cannot be recovered by all means.

Thanks & Regards,

Richard Chen,
Microsoft Online Support Professional

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Mike G]

From where this thread is leading (dead end), and all the
research I've done, I will assume you are telling me there
is no way of recovering the curretn production dbase
without having this log file? The information stored
within this dbase, that has lost this essential log file
(E*000), is our companies users exchange accounts for the
last 1 year plus, we really need to get the data out of
the dbase, even if I set up a new existance of exchange.
I am trying to find the best options for time/data loss in
a prooductive environment, this server has now been down
for 3 days.

>.
>

[Richard Chen[MSFT]]

Hi Mike,

Recovering the log files is the best option. If you cannot do this, we will
try to repair the database, but this will surely discard some messages from
the store to make it consistent and thereby lead to data loss to some
extent.

You may take the following steps as the action plan:

1. Backup the whole MDBData folder
2. Remove all the files except EDB and STM files.
3. Use command ESEUTIL.EXE /p "databasename.edb" to repair the database.

ESEUTIL.EXE is prevent in exchsrvr\bin folder. please include full path and
file name of the edb file in the command line. Please make sure the EDB
file is listed in the parameter, isstead of the STM file.

4. Use command ESEUTIL /d "databasename.edb" to defragment the database.

5. Try to mount the database in Exchange System Manager.

You may perform step 3 and step 4 for all the databases that cannot be
mounted in Exchange System Manager. It only requires run once on each
database.

6. Dismount the database.

7. Run Isinteg -s <servername> -fix -test alltests

Isinteg.exe is also provided in exchsrvr\bin folder. You need to repeat
this command against each database until you see "error amount" and
"warning amount" don't decrease. You need to run this command against all
the databases.

8. Mount the databases in Exchange System Manager and perform a full system
backup.

[Mike]

Yes. This is the fix. Thank you.

>.
>

[Richard Chen[MSFT]]

You are welcome, Mike. I am glad we can be of help.