Re: Rebuild Exchange Server 2003 advice required

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Once the rebuild has been done and the backups are up and running
again, the next time I need to do this it'll be easy. I appreciate it
may not be as easy as pulling one disk out and putting another in and
getting the radi to sort itself out, but we are still a fairly small
company and don't really need raid. Having said that, if we had raid
this time, it would be sorted by now! :)

Oliver Moazzezi wrote:
I also note you mention 'disk' instead of 'disks'

I also note you stated 'If I simply install the new drive, install the
OS<snip>'

Are you just using a single disk?

You need to implement RAID...


Oliver



"Andy David - MVP" <adavid@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5o8ck2hff0icku92meulbo2c3ji3v9ef5t@xxxxxxxxxx
On 30 Oct 2006 08:03:45 -0800, "Karl Rhodes"
<googlegroups@xxxxxxxxxxxxxxxx> wrote:

Thanks Andy.

I followed that link you posted and within these pages found this link

http://www.microsoft.com/technet/prodtechnol/exchange/Guides/DROpsGuide/06eaa5e7-0cfc-43d9-928a-acabbfaeb51f.mspx?mfr=true

Which describes the process that I should follow. It does say to
restore the system state as part of this process. Fortunately I can get
the system state and the mail store backups.

I have used the disasterrecovery switch successfully and have never
needed to restore the system state since I was restoring to a new
server, but I understand why that link states that.



A note to anyone else reading this:

NTBACKUP on the Windows Server 2003/Exchange Server 2003 server WILL
backup both the server state and the mail store. There is no reason why
you shouldn't have these backups to hand as with only 5 minutes
configuration and no additional outlay, you can setup scheduled events
to backup this data, either to an existing tape drive or alternate
server hard disk.


Andy David - MVP wrote:
On 30 Oct 2006 06:54:09 -0800, "Karl Rhodes"
<googlegroups@xxxxxxxxxxxxxxxx> wrote:

Hi Andy,

So if I follow this process, all should be well?

Hopefully!

1.Make a note of the Server name and IP.
2.Backup mail stores on Exchange server
3.Install new drive
4.Install Windows Server 2003 (Make sure server has the same name and
ip address as before)
5.Patch fully from MS.
6.Install Exchange 2003 using /disasterrecovery
7.Patch fully from MS
8.Restore from taken backups

What are the ramifications of installing with disasterrecovery on a
fresh install?


That is what the disasterrecovery switch is for.





Andy David - MVP wrote:
On 30 Oct 2006 04:43:23 -0800, "Karl Rhodes"
<googlegroups@xxxxxxxxxxxxxxxx> wrote:

Hi All,

If you've read my posts for the last few days, you'll notice that
our
Exchange server is far from being happy. Dell have delivered a new
hard
drive today and this evening I intend to install this new hard drive
and completely rebuild the server.

I will be installing Windows Server 2003 Ent and Exchange Server
2003
Ent and this server will be part of our domain, as it is at the
moment.

I have read some posts where they mention backing up the system
state,
but have no idea what this is. The only backups I have is an
NTBackup
of the Exchange mail stores.

I wouldnt worry too much about system state if this is a member
server
and your DCs are still up and active.


If I simply install the new drive, install the OS, join the domain,
install exchange and try to restore, I guess that will fail, but as
I've never done this before, I have no idea about what I need to do
to
do this quickly (ie after work for a few hours this evening) and in
one
hit, only having NTBackup by my side.

ANY suggestions are appreciated.


Sounds like you will need to reinstall using the disasterrecovery
switch which assumes that you are rebuilding the exch server and the
object still exists in AD and in ESM as it was before the crash.


You should take a look at:
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/disrecopgde.mspx

If you are not comfortable doing this, I would call PSS. Really.

.

Relevant Pages

  • Re: Shaky server
    ... I may try & get the owner to cough up & purchase a new server but doubt ... want a fully functional SBS server before upgrading, ... So the backup device is broke, this confirms why backups have been ... I have tried to run the BPA but it will not install ...
    (microsoft.public.windows.server.sbs)
  • Re: Backup of AD & but not full system state
    ... I will have at minimum two backups of the data ... the components of the system state I would NOT use them, ... Small Business server and is RAID 5 ready. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Shaky server
    ... I may try & get the owner to cough up & purchase a new server but doubt ... This is SBS Premium but no ISA but is behind hardware firewall that is ... So the backup device is broke, this confirms why backups have been ... I have tried to run the BPA but it will not install ...
    (microsoft.public.windows.server.sbs)
  • Re: Rebuild Exchange Server 2003 advice required
    ... I also note you mention 'disk' instead of 'disks' ... I also note you stated 'If I simply install the new drive, ... restore the system state as part of this process. ... NTBACKUP on the Windows Server 2003/Exchange Server 2003 server WILL ...
    (microsoft.public.exchange.admin)
  • Re: Shaky server
    ... Now I assume the backups & other wizards are failing is due to not having ... any service packs installed so I am planning on installing SBS Service Pack ... server after this. ... Does anyone have any pointers for a successful install or pitfalls that I ...
    (microsoft.public.windows.server.sbs)