First "isinteg -patch"
second, buy the Intelligent Disaster Recovery Option for Backup Exec.
Make IDR Bootable Disks, CD or Tape, pop them in recovery server (unplug
network connection) click a few buttons and you're set. It'll save you a
lot of time, hair pulling-out and will have your server EXACTLY the way it
was pre-disaster.
> Hello,
>
> I decided to do a DR test today but unfortunately could not get the IS
> service to start after the restore. Below are my steps in the exact order:
> Current Exchange server running 5.5 with sp4 on a windows 2k server
>
> 1.Setup a separate Lan and promoted a bdc that I took off from our existing
> network to a pdc.
> 2.Ran setup of Exchange 5.0. Did not join existing domain.
> 3.Gave the server the same name as the orginal exchange server, the same
> site and organization names as the existing exchange server. (Understanding
> that the site and organization names are case-sensitive)
> 4.Created a new site.
> 5.Selected the same service account as the original exchange server
> 6.Did a directory Import from the most current directory.csv file
> 7.Upgraded recovery server to Exchange 5.5 then SP 4. (same as original
> server)
> 8.Ran MS Exchange performance optimizer
> 9.Deleted and re-added the computer name on the pdc to create a new sid.
> (After readding computer I was forced to remove the recovery server from the
> domain and then re-add it to the domain)
> 10.Installed MS Outlook on recovery server.
> 11.Performed the restore using the last full backup tape (Used Veritas
> Backup Exec ver 8.6). Restored only the Information Store not the Directory
> since that was already imported in step 6. (Note: I normally do a brick
> level backup so the tape consisted of the Directory store, Info store, and
> part of the individual mailboxes. The second tape contained the remainder
> of the mailboxes) The info store was approximately 33gb.
> 12.Restored both Priv and Pub data by selecting them on the Exchange tab in
> Veritas backup exec ver 8.6.
> 13. Once the restore was completed the Diretory, MTA, System Attendent all
> started but the Info store would not start. Also I could not do an isinteg
> -patch because it could not find the IS database.
> 14. I manually tried to start the IS service but received the error:
> Windows could not start the MS IS service on the local computer and to check
> the Event viewer for more info. The Event Viewer said: MS IS service
> terminated with server specific error 4294966266.
> 15. Im going to check the knowledge base regarding this error but im
> curious if any has ever come across this? Did I not do a step right?
> Should I have not imported the Directory store in step 6? Im a little
> stumped as to what I did wrong causing the IS not to start.
> Anyone have any ideas???
>
> Thanks,
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
