Restoring NT and Exchange 5.5

[wjeayre]

I am trying to restore NT and Exchange 5.5....First have installed NT 4.0, Proxy 2.0 and Exchange 5.5 (just as it was installed before the crash using the same site and organization) then installed sp4, then reinstalled Backup Exec (so that I can restore from the last full backup) after several days of frustration...figured out how to read the inventory and catalog information on the cartridge...<br>
<br>
The NT portion of the restore went well...it put all the files, icons, users etc. back as they were. Problem exists in restoring Exchange...even though I used Backup execs feature for backing up all of Exchange. <br>
<br>
Does anyone have the step by step instructions for restoring NT and Exchange...any input would be appreciated.

 

[Zelandakh]

How far do you get with the BE restore of Exchange? Do you get recipients restored?

 

[wjeayre]

Affter restoring the Exchange, I get an error that the server can't be found, the PDC can't be found and none of the services will start.

 

[Zelandakh]

exchange server or NT Server? Best bet is to do a partial restore and only restore the exchange data and mailboxes to a pre existing server. Its probably cos you are restoring the old servername to the new server...

 

[SRG]

Here is some basic exchange restore info. I would need to know more about your environment to help further. <br>
<br>
<br>
Restoring Exchange Databases<br>
Typically, restoration fits one of two scenarios: restoring all databases if the whole disk partition is destroyed, or restoring one database due to some less-disastrous hardware corruption. <br>
If the PRIV.EDB file is the only one damaged on an Exchange server, for example, you can restore it in two basic steps:<br>
· Put everything on tape back on the disk.<br>
· Call Exchange to initiate recovery procedures.<br>
<br>
This second step is triggered automatically by most backup and restore products. However, before you initiate the recovery it’s best to carefully check that everything is where you expect it on disk. Restoring the wrong data in a recovery can cause irksome problems, so a quick sanity check is worthwhile.<br>
Immediately after the restore portion of the recovery operation, these files should be on disk:<br>
· PRIV.EDB, restored from tape<br>
· PRIV.PAT, restored from tape<br>
· EDB.CHK, the checkpoint file, unaffected by the restore operation<br>
· EDBNNNNN.LOG files restored from tape<br>
· Sequence of log files right up to the current EDB.LOG, unaffected by the restore<br>
<br>
When the store service starts it initializes the database software, which checks the status of the data on disk. The “restore in progress” flag tells the database software that the database has been restored from tape. <br>
The database software uses information recorded in the RestorInProgress key to determine the “minimum” range of log files that need to be replayed to make the restored database consistent. These log files, together with data in the .PAT files, is played into the database files first. If an unbroken sequence of log files exists on disk then replay will continue, potentially right up to the “current” log file EDB.LOG. If this process is successful then the database will have been returned to its state at the point of the outage. At this point a “normal” start-up of the store service will resume.<br>
Note This procedure varies depending on which parts of the Exchange server have been damaged and which files are restored. <br>