RE: Exchange 5.5 died....

  • From: Naboth Semwayo <naboths@xxxxxxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 24 Feb 2004 08:13:13 +0200

+What you can do is copy your private and public stores (*.edb) to another
location, Install your MX with the same organization name and site name,
retsore all the mailboxes (maybe from a CSV. Stop ypur informatuion store
service and overwrite the new edb files. From command prompt in your
exch\bi9n folder run ISINTEG - patch. I have done this thousands of times
and is guarantyeed to work as long as you put in the same site name and org

-----Original Message-----
From: Greg [mailto:ghermida@xxxxxxxxxxxxxxx]
Sent: Saturday, 21 February, 2004 9:53 PM
To: [ExchangeList]
Subject: [exchangelist] Exchange 5.5 died....

Yesterday, our firewall was breached, the a trojan virus was placed on an
internal server, and basically ground the network to a halt.  In the  18
hour day and night long process, our win2k OS hosting the exchange app
took a header.  It's a single site, single 5.5, on a win2k server in a NT4
domain.  C:\ contained the programs, d:\ contained the public info store,
& e:\contained the private store.  When I rebuild the OS and reinstall
exchange, when I specify the where I want the DB's to end up (in the same
locale), will it find the existing public and private db's and overwrite
them?? Or will it find them, see that they exist, and take that into
account.  I have backups so I think I'm covered, I can always apply the
weekend full backup and apply the weekday incrementals, but I was hoping
to recover the damn thing a little quicker.

List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:

Other related posts: