RE: Best failover and/or redundency

  • From: "Gavin Jones" <gavin.jones@xxxxxxxxxxxx>
  • To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
  • Date: Tue, 26 Apr 2005 20:23:45 +0100

I am just about to deploy and would be really keen to follow this thread, I
will post my deployment details shortly


-----Original Message-----
From: Byron Kendrick [mailto:bkendrick@xxxxxxxxxxxxxxxxx] 
Sent: 26 April 2005 20:02
To: [ExchangeList]
Subject: [exchangelist] Best failover and/or redundency

Just like everyone else our Exchange server has become one of the most
critical applications on or network and we are becoming increasingly
concerned about downtime if something goes wrong.  What I am curious about
is what seems to be the best practice. I would really like to have a
couple of exchange servers in a cluster but I was wondering what other
options there are.  I thought about having a second server sitting in the
closet that I could throw up and get online with "last nights" backup. 
That might be a little cheaper but you would still lose some of the
presidents and VP's mail as well as more down time.  What are some of you
doing that is working for you and what prompted you to this instead of
some other solution.  Money is kinda sorta critical but so is my job.


List Archives:
Exchange Newsletters:
Exchange FAQ:
Other Internet Software Marketing Sites:
World of Windows Networking:
Leading Network Software Directory:
No.1 ISA Server Resource Site:
Windows Security Resource Site:
Network Security Library:
Windows 2000/NT Fax Solutions:
You are currently subscribed to this Discussion List as:
To unsubscribe visit
Report abuse to listadmin@xxxxxxxxxxxxxx

Other related posts: