Re: Recovering Information Store after complete system crash

Tech-Archive recommends: Fix windows errors by optimizing your registry

From my understanding, you would like to retrieve your messages from
the priv1.edb and priv1.stm?

"Copy Exchange database files from the current path location to the
path location for a different logical database, storage group, or
server If you use this method, the logical storage group and
database names do not have to match, but the database filenames must
match those defined in the destination. You may rename database files
as necessary to make them match.
For example, database files named "Priv1.edb" and "Priv1.stm" are
associated with the logical database "Mailbox Store (Server A)" in
storage group "Server-A-SG1" on Server A. You create a Storage Group
called "Server-B-SG1 on Server B, and create a database called "SG1-
MB1" in that storage group. The file paths listed for the SG1-MB1
database are "F:\Databases\SG1-MB1.edb" and "F:\Databases\SG1-
MB1.stm."
You copy Priv1.edb and Priv1.stm from D:\Databases on Server A to F:
\Databases on Server B. You then rename Priv1.edb to SG1-MB1.edb and
rename Priv1.stm to SG1-MB1.edb."


Moving an Exchange Mailbox Database to Another Server or Storage
Group
http://technet.microsoft.com/en-us/library/aa997006.aspx



For third party apps you can purchase,

http://www.ontrackpowercontrols.com/


James Chong (MVP)
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com
On Mar 13, 11:44 am, Greg H <G...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello,

I was handed a Windows SBE 2003 server that had crashed with a lsass.exe
error. I was only able to recover the priv1.edb and the priv1.stm files from
the system. The previous tech didn't have any backups. I have the server
re-built, but I would really like to be able to recover the mailboxes from
the old Server.

I know Circular logging was enabled on the old server from the previous
tech's documents.

Is there a Utility to exctract the messages into a PST or something?

Thanks,


.

Relevant Pages

  • RE: Repairing / modyfing Exchange
    ... I'll setup a new server today to try it. ... Also, because I have messed something up with the First Storage Group, if I ... > Exchange Database to another disk, ...
    (microsoft.public.windows.server.sbs)
  • Re: Database Size, Database Corruption, Message Store & Storage Group
    ... More careful monitoring of the server. ... Each extra storage group also requires more memory at startup, ... Also it is important to know if there was actually database corruption. ... In terms of backups, you should look at "how" you are performing backups. ...
    (microsoft.public.exchange.admin)
  • Create SharePoint Portal failed.
    ... One mentioned ensuring that SQL Server uses a case ... 13:55:40 Service database server is 'USDC-JOHRIV'. ... Update dbo.propertylist set DisplayName = N'Last name' ...
    (microsoft.public.sharepoint.portalserver)
  • Re: Database Size, Database Corruption, Message Store & Storage Group
    ... More careful monitoring of the server. ... > up an entire storage group before creating a new one. ... > Also it is important to know if there was actually database corruption. ... > that 99.9% of all database corruption in Exchange is caused by faulty ...
    (microsoft.public.exchange.admin)
  • Re: ADO Connection Timeout
    ... to the central server, but you are willing to live with periods where it ... i.e. a local database or even a text file. ... to function until the connection can be restored to the server. ...
    (microsoft.public.data.ado)