Re: Restoring EXCH 5.0 to different hardware / creating blank .edb files

From: Kirill S. Palagin (kpalagin_at_nomail.phxint.please.ru)
Date: 06/24/04


Date: Thu, 24 Jun 2004 16:08:00 +0400

I would suggest fitting the Proliant with 120GB IDE HDD and restoring databases
once again.
For the future, you do not need server-class hardware for lab exercises -
Virtual PC will do just fine.

TheMongKey wrote:

> I'm trying to test an upgrade of Exchange 5.0 (with SP2 + fixes) to 5.5
> (yeah, I know...cutting edge or what). I have restored the mail server to an
> old Proliant 400 (bless ya, ebay!), and managed to work around the hardware
> differences to get it to boot. The NETLOGON, System Attendant and Directory
> services all start with no problems or warnings, and I can run the Exchange
> Admin program as long as I don't try to do anything IS related. The server
> is a BDC so has a copy of the SAM database for permissions, etc.
>
> Here's the thing: I don't have enough disk space to restore the priv.edb so
> I want to just create a blank one to test the upgrade on. I have deleted all
> edb & log files from all MDBDATA directories but if I start the IS from the
> Services applet or with NET START I get the following events in the
> Application event log:
>
> 10 MSExchangeIS ((330) ) Database engine 05.1460.0008 started
> 11502 Initializing the POP3 external interface
> 11500 Initializing the NNTP external interface
> 1000 Attempting to start the Microsoft Exchange Information Store service
> 1087 The information store was restored from an offline backup. Run
> ISINTEG -patch before starting the information store
> 1005 Unable to start the Microsoft Exchange Information Store: Error 1011
> 11505 The POP3 interface has stopped
> 11503 The NNTP interface has stopped
> 11 MSExchangeIS ((330) ) The database engine stopped
>
> When that little lot has finished, I see that a priv.edb (but not a pub.edb)
> has been created, plus edb.chk, edb.log, res1.log and res2.log files.
>
> If I run ISINTEG -patch I get the following message
>
> The private store could not be updated. Reason : ecMDBNotInit
>
> plus the following events in the App log:
>
> 1091 You have restored a private information store only. This server
> contains a private information store and a public information store. Only
> the data in the private information store has been modified.
> 10 MSExchangeIS ((330) ) Database engine 05.1460.0008 started
> 11 MSExchangeIS ((330) ) The database engine stopped
>
> Any ideas how I can get the IS to start? I just want to go through the
> upgrade process a few times before I do it on the production machine,
> because I like having a job.
>
> Regards,
>
> TMK

--
Help fight spam - designate sending servers for your domain.
http://spf.pobox.com


Relevant Pages

  • Re: Restored Exchange, cant replay logs because no Restore.env
    ... No, there is no other server involved, but that article was recommended to ... me as instructions on restoring the information store. ... the instructions claim that there's supposed to be a file ...
    (microsoft.public.exchange.admin)
  • Re: Restored Exchange, cant replay logs because no Restore.env
    ... No, there is no other server involved, but that article was recommended to ... me as instructions on restoring the information store. ... the instructions claim that there's supposed to be a file ...
    (microsoft.public.exchange2000.admin)
  • Restoring EXCH 5.0 to different hardware / creating blank .edb files
    ... The server ... I don't have enough disk space to restore the priv.edb so ... 1087 The information store was restored from an offline backup. ... 1091 You have restored a private information store only. ...
    (microsoft.public.exchange.admin)
  • Re: Restored Exchange, cant replay logs because no Restore.env
    ... That article is not just about restoring, ... the Information Store database to a server that is in a different forest ... than your production server is in". ... > I cannot replay the log files that had been generated since the last backup. ...
    (microsoft.public.exchange.admin)
  • Re: Restored Exchange, cant replay logs because no Restore.env
    ... That article is not just about restoring, ... the Information Store database to a server that is in a different forest ... than your production server is in". ... > I cannot replay the log files that had been generated since the last backup. ...
    (microsoft.public.exchange2000.admin)