RESTORING EXCHANGE SERVER !!!!!!

[Van Assche Computing]

We are setting up an SBS Server with EXCHANGE 5.5 on it
this is on a complete new server (new hardware...)
we have givin the server the same name and created the same domain name,
so the clients don't have to be reconfigured

we tried to restore with arcserve and NT-BACKUP (also tried to copy the
PRIV.edb and PUB.edb)
but never got the exhange server up and running

does anyone know what's the best way to get the exchange data on the new
server.

[Jim Tagart]

Howdy, I'm in the midst of figuring out how to make a recovery server
for my Exchange server, PDC unfortunatly and the only NT server for
about 70 users.

Check this out.

Notes on Recovery from Offline Backup (From Microsoft TechNet 11/1999)

After running an offline information store restore, but before starting
the information store service, run the isinteg -patch command.
During startup, Exchange validates a globally unique identifier (GUID)
in the information store with an entry stored in the Windows NT
Registry and the Exchange directory. The information store service
cannot be started if the GUIDs do not match in each of the three
places. Mismatches can occur if the information store has been restored
from an offline backup.
If a copy of the information store (Pub.edb and Priv.edb) is restored
from an offline backup and isinteg -patch has not been run, it fails
and a -1011 error is generated when the service is restarted. The -1011
error produces an entry in the Windows NT Event Viewer Application Log
with source ID 2048. The error message reads as follows: “The
information store was restored from an offline backup. Run isinteg -
patch before restarting the information store.”
This error occurs because the GUIDs used by the information store that
was restored are old and matching GUIDs might already exist. The GUID
for this restored information store must be replaced to ensure that it
is unique.
An error message, DS_E_COMMUNICATIONS_PROBLEM, will also appear.
When run with the Patch option, ISINTEG resets the entries for the
GUIDs in the database, directory, and registry. It also patches
information used during replication to prevent incorrect backfilling.
After it has been patched, the information store service can be started
again.

----------------------

Exchange his very dependant on the SID. I have seen mention of using
the ISINTEG from online backups also.

Good Luck,
Jim

In article <MPG.12acc0825...@news.skynet.be>,

Sent via Deja.com http://www.deja.com/
Before you buy.

[Kirill S. Palagin]

f

Van Assche Computing wrote:

> We are setting up an SBS Server with EXCHANGE 5.5 on it
> this is on a complete new server (new hardware...)
> we have givin the server the same name and created the same domain name,
> so the clients don't have to be reconfigured
>
> we tried to restore with arcserve and NT-BACKUP (also tried to copy the
> PRIV.edb and PUB.edb)
> but never got the exhange server up and running
>
> does anyone know what's the best way to get the exchange data on the new
> server.

--
Intel is trying to spoil AMD by pressuring motherboard makers.
Say YES to AMD at
http://www.petitionpetition.com/cgi-bin/cgi12.cgi?petition_id=34
Demand investigation from FTC
http://www.usdoj.gov/atr/contact/newcase.htm
If you have any information on this send it here
newca...@usdoj.gov
Thanks.

Kirill S. Palagin

[Ed Crowley]

You need to obtain, read and understand the Microsoft Exchange Disaster
Recovery whitepaper available from TechNet or the Microsoft web site.
--
Ed Crowley MCSE+Internet MVP
Senior Consultant
NCR Corporation

Van Assche Computing <jsch...@vanassche.com> wrote in message
news:MPG.12acc0825...@news.skynet.be...

[dd1...@my-deja.com]

There is a wealth of information about disaster planning, prevention
and recovery in the MS Knowledge Base.

I do both an Online and Offline backup with NTBackup and have found
value in Q237767.

This ones gonna take some reading and researching on your part. More
than can be covered in the newsgroups. I think that after you get
further down the road with your problem, you will find that the
disaster planning will become a key element of your future
implementation and operation of MS Exchange. Especially if your
Exchanger services are critical to company operation as they are at my
organization.

David Dennen, MCSE

In article <MPG.12acc0825...@news.skynet.be>,

Van Assche Computing <jsch...@vanassche.com> wrote:
> We are setting up an SBS Server with EXCHANGE 5.5 on it
> this is on a complete new server (new hardware...)
> we have givin the server the same name and created the same domain
name,
> so the clients don't have to be reconfigured
>
> we tried to restore with arcserve and NT-BACKUP (also tried to copy
the
> PRIV.edb and PUB.edb)
> but never got the exhange server up and running
>
> does anyone know what's the best way to get the exchange data on the
new
> server.
>