I am just about to deploy and would be really keen to follow this thread, I will post my deployment details shortly Gavin -----Original Message----- From: Byron Kendrick [mailto:bkendrick@xxxxxxxxxxxxxxxxx] Sent: 26 April 2005 20:02 To: [ExchangeList] Subject: [exchangelist] Best failover and/or redundency http://www.MSExchange.org/ 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. Thanks. Byron ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: World of Windows Networking: http://www.windowsnetworking.com Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this MSEXchange.org Discussion List as: gavin.jones@xxxxxxxxxxxx To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to listadmin@xxxxxxxxxxxxxx