Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange 2003 "Hot Spare"

Status
Not open for further replies.

jsonchan

MIS
Jan 25, 2002
44
0
0
HK
Is it possible to maintain a live hot spare server running at all times for Exchange 2003 recovery (within same org & site?

Thanks
Jasonz
 
We have about 60 users.

Is there any other (low cost) way to do? Actually we're just running standard version
 
Ok, maybe a bit overkill ;)

What is the server you are running? What is the hard disk configuration? If you have RAID-1 hot swappable disks, you could keep a could spare that you could rotate as a spare.

"Assumption is the mother of all f#%kups!
 
HP DL380G4 with 2GB, 4*145GB/U320 RAID-5 running on Win2k3/R2 STD server. And this would be the only server we have in the office providing File/Print/Exchange mail services and A.D controller (all-in-one).
 
There is a DR thread that covers most of this:


The short answer is you can't have a hot spare. Exchange standard does not support failover senarios without 3rd party tools.

It also becomes much, much more difficult if your Exchange machine is your DC because Exchange needs Active Directory so if your second machine was not also all a DC then you couldn't use it if the first machine failed.

Unless you're running SBS you are better off using any second machine to move the DC responsibilities off of the Exchange box.
 
You can't move DC responsibilities off of Exchange. Trust me - you'll PERMANENTLY break Exchange. Use a second box and move Exchange to it. That drive configuration isn't the best for Exchange, either. I'd recommend

2 drives in RAID 1 for OS/Exchange app
2 drives in RAID 1 for Exchange transaction logs
3+ drives in RAID 5 for Exchange databases
3+ drives in RAID 5 for everything else

You could combine the first two together, if you must, but the transaction logs and databases should have their own arrays.

Pat Richard, MCSE MCSA:Messaging CNA
Want to know how email works? Read for yourself -
 
58Sniper,

Thanks for pointing out your can't move the DC off of Exchange, I wasn't thinking when I typed that. Seperate the duties, but by moving Exchange not the DC. My bad.
 
Thanks you guys all the comments above!!

Thought the better way is to move Exchange out of DC controller first.

Secondly XOsoft WANSync for Exchange seems a good solution. When disaster strike, it may immediately be rerouted to Exchange server replicas.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top