Re: Full Exchange System Restore

Tech-Archive recommends: Fix windows errors by optimizing your registry



Honestly, it's been a while since using backup exec 10.1, so I'm not sure of
the requirements for Symantec (Veritas). It's always difference when using
third-party tools and probably best to check with the manufacture. From a
general Microsoft Recovery Procedure, this is the recommended practice. If
you are putting 100% faith on the current backup solution, I'd recommended
testing the recovery processes.

You can always reference the Exchange DR Guide to build a trustworthy
recovery process for all scenarios (RSG, DialTone, etc.). RSG's are great to
validate restoring from tape if you cannot perform a full test system
restore.

http://download.microsoft.com/download/e/c/f/ecf905be-a696-49f1-b9cc-28aeca316eec/DROpsGuide.doc

--
Chris Calderon
"mc123" <mc123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3FF13A67-45D4-47AC-95C6-6258158BD448@xxxxxxxxxxxxxxxx
So this is even after a full system restore has been done which includes
all
Exchange binaries with SP1?

Thanks.

"Chris Calderon" wrote:

In order to recover Exchange, you do need to run the /disasterrecovery
switch for both installation and SP1. The first instance pulls Exchange
configuration from Active Directory and installs the binaries onto the
recovered server. The SP1 installation with the /disasterrecovery switch
updates the binaries in the same matter. Hope this helps.

--
Chris Calderon
"mc123" <mc123@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7E4ABE61-1DB9-48B1-B61B-80FA14056A51@xxxxxxxxxxxxxxxx
I wanted to confirm some steps with a full restore of Exchange 2003
I run Exchange Server 2003 SP1, on a host running Windows Server 2003
SP0.
I use backup exec 10.1 and run full system backups and database
backups.
I
read that after a full system restore, one should run the exchange
setup
with
the /disasterrecovery switch for the exchange install and each exchange
service pack.
My question is since the full system backup will bring the system back
to
a
Exchange SP1 level, do I need to run the exchange setup with the
/disasterrecovery switch both for the initial setup as well as the SP1?
or
do
I just need to run the SP1 setup with the /disasterrecovery switch?
It seems a little odd that I should bring the Exchange SP1 install
(after
the full system restore) back to non service pack install, and SP1
again,
but
maybe it has to be this way to ensure proper restore?

Appreciate feedback.

thanks.





.



Relevant Pages

  • Re: Outbound Messages sitting in Queue
    ... >I have Server 03 sp1 installed. ... the NIC that is on the server will not allow me to change ... install and use the Intellegent Mail Filter ... >> That doesn't sound like an Exchange problem. ...
    (microsoft.public.exchange.admin)
  • SP1 finished successfully... or did it?
    ... This question spawns from my thread "c1041724 when mounting exchange store... ... Copeland last time I tried to install SP1, ... but during the SBS SP1 install the setup halts and it asks if I want to open ...
    (microsoft.public.windows.server.sbs)
  • Re: Concerns about applying SP1 to SBS 2003
    ... Introduction to Windows Small Business Server 2003 for Enterprise IT Pros ... they had never applied any updates to the server, much less SP1. ... reluctant to run Exchange on a server that is doing a bunch of other ... People were itching to install SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Concerns about applying SP1 to SBS 2003
    ... they brought in a consultant who formatted and deployed SBS ... couldn't manage or troubleshoot Exchange if that was necessary. ... applied any updates to the server, much less SP1. ... People were itching to install SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Concerns about applying SP1 to SBS 2003
    ... Introduction to Windows Small Business Server 2003 for Enterprise IT Pros ... reluctant to run Exchange on a server that is doing a bunch of other ... People were itching to install ... SP1, but we kept telling them to please wait, because if they installed ...
    (microsoft.public.windows.server.sbs)