Exchange Recovery

[AndrewS]

Hows this for a problem...
I have a friend that is running SBS2k3, it died and no back ups. I have
managed to get the *.edb, *.stm and log files from the old drives but thats
it. How do I mount them on to the new server?

[Kevin Weilbacher [SBS-MVP]]

Sounds like a commercial could be made from this:

Friends don't let friends drive servers without backup!

Does this help?
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q155216

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"

"AndrewS" <And...@discussions.microsoft.com> wrote in message
news:8973FA55-626E-4721...@microsoft.com...

[Lanwench [MVP - Exchange]]

In news:8973FA55-626E-4721...@microsoft.com,
AndrewS <And...@discussions.microsoft.com> typed:

If you don't have a good backup (tsk tsk) and can't mount the stores in your
rebuilt environment, you might see
http://www.quest.com/recovery%5Fmanager%5Ffor%5Fexchange/ - it's an
invaluable tool for an Exchange admin.

[Steve Foster [SBS MVP]]

AndrewS wrote:

You don't.

If the original AD is not available, I don't think there's any way to
directly use the stores.

You probably need something like Recovery Manager for Exchange from
www.quest.com (formerly Aelita).

--
Steve Foster [SBS MVP]
---------------------------------------
MVPs do not work for Microsoft. Please reply only to the newsgroups.

[Anna Clark]

Hi Andrew:

Any chance that the client worksations were keeping .ost files, and that
they have not left the old domain yet?

In that case you might be able to open Outlook on the .ost files, export to
.pst and import back to the new domain.

Anna Clark

"AndrewS" <And...@discussions.microsoft.com> wrote in message
news:8973FA55-626E-4721...@microsoft.com...

[Deepak Shenoy]

Hi Andrew,

You are only as good as your last fully good and validated backup. What you
will need to do first is back up what you do have. Go to the folder that
contains your database files - delete those. Restore the database that you
have from the old drives. If your log files are toast then you will have to
copy the old log files from the previous old drive to the current log log
file folder. Ideally, you want to use as much of the old log files as
possible. If your current log files are ok make sure that you also have a
copy of the checkpoint file available. This will tell Exchange what's the
last committed log file it can use for restoration purposes. If you restore
from your old drive you can sometimes merge the log files together - but if
you do this you will need to delete the old checkpoint file.

I would look at the whitepaper on the Microsoft.com site on Exchange
Disaster Recovery. It will provide you with the necessary background as well
as information about how to use ESEUTIL to verify the integrity of the
various Exchange files.

Does this help?

"Anna Clark" wrote:

> Hi Andrew:
>
> Any chance that the client worksations were keeping .ost files, and that
> they have not left the old domain yet?
>
> In that case you might be able to open Outlook on the .ost files, export to

> ..pst and import back to the new domain.

[Anna Clark]

Hi Deepak:

The user seems to be saying that they have rebuilt the SBS from scratch, in
which case the SID will be different and the store will probably not mount.
In some cases, if the did everything exactly the same they may get it to
mount, but unless one has tested this on a backup server in the closet it is
fraught with errors.

I would be more likely to get the production server up, but before joining
the workstations to the new domain, verify if there are no ost's. Then
after getting the users back in operation, try restoring the exchange data
bases files from the old drives to a test unit. Once running on the test
SBS, they can use xmerge or export to recover the individual mailboxes.

Anna

"Deepak Shenoy" <Deepak...@discussions.microsoft.com> wrote in message
news:0F344E76-0F1B-4868...@microsoft.com...

[AndrewS]

This is so true....I had been looking at the box for the first 3-4 weeks just
to make sure that everything was working OK, but then left him to it. Turns
out that for the past 6-8 weeks he has had an anoying beep coming from the
server. Looks like it was telling him that he had a failed drive in hte raid
5 set.I may have to take his server off him!
It just gets worse. The files that I have from the old drives are not what
you would cll "In Good Condition" ESEUTIL /p , ISINTEG just don want to know
about it. Quest can see the files and folders but only fragments of mail.
Will have a look for the .OST on the local cilents, see if I can do anything
from them.

Thanks for your help but it may be a lost cause

[bibo...@gmail.com]

Exchange Server errors, accidental deletion of important files may lead to Exchange Database file corruption. In order to recover EDB files, one needs to use Lepide Exchange manager that is user friendly, professional and easy to use software. This software makes EDB to PST conversion accurate and quick. In case of corrupt EDB files, users need to launch LEM software, point to the corrupt EDB file, extract user mailbox, convert EDB to PST and save to the desired location.
For more information - http://www.exchangedatabaserecovery.co.uk