Re: More than one Exchange Server in a domain...
From: Dave Kearney [MSFT] (dkearney_at_online.microsoft.com)
Date: 12/02/04
- Next message: Dave Kearney [MSFT]: "Re: setup questions - Non Delivery reports"
- Previous message: Alan Sun [MSFT]: "Re: Migration wizard permissions error"
- In reply to: Greg Williams: "Re: More than one Exchange Server in a domain..."
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 1 Dec 2004 23:32:47 -0800
Any way you cut it it's going to be relatively expensive. To use clustering
you're going to need the Enterprise/Advanced versions of both Windows and
Exchange along with a shared storage solution. You can always setup a new
server and move your mailboxes and public folders over but the old one does
not then automatically become a hot standby system. To do this you're
either going to need clustering as I recommended or a third party solution
such as the one recommeded by Hank.
-- -Dave This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm. "Greg Williams" <Greg Williams@discussions.microsoft.com> wrote in message news:1E00D3BD-B492-4CC4-838D-5F13D55CBB6B@microsoft.com... >I think you two are talking about something that goes down the road I am > being asked to travel? > > My boss wants to put a 2nd exchanger server 2000 in place, start it up, > and > have the old one, that is now out of warranty, as the backup. I will be > using a new server with W2000 Server. Costs will always be the first > question. But is there a way to set up a new server, import the mail, and > have it start up using the old one as a backup to the new server on the > same > domain? > > "Hank Arnold" wrote: > >> Another alternative is a High Availability solution like DoubleTake or >> LifeKeeper. You set up a "failover" server that is in "standby" mode. It >> has >> all the software installed with the services off. Usually, there is a >> "data" >> drive that has all the databases and log files on it that is mirrored >> from >> the active to the standby system. We use LifeKeeper and that how it is >> set >> up. When the main server goes off line, the software detects that this >> has >> happened and proceeds to start the services on the other server and >> change >> machine names/IP addresses/ etc.. It reduces our down time to less than >> 10 >> minutes. >> >> The bad news is that it is *EXPENSIVE* and not trivial to set up or >> maintain. >> >> -- >> Regards, >> Hank Arnold >> >> "felix" <felix(NO-SPAM)@eastop.com> wrote in message >> news:eU7bR$21EHA.208@TK2MSFTNGP12.phx.gbl... >> > Thanks for your reply. >> > >> > Now my boss is now concerning about minimizing the downtime of it. >> > Therefore he came up with an idea that we can have 2 Exchange Servers >> > so >> > that when one is down, another one will be up automatically without any >> > manual user configuration. Now clustering seems like it can provide >> > this. >> > >> > However, since our server is now running WIN2K Small Business Edition, >> > will we be able to use Clustering service? Because it seems to me that >> > this only supports in Enterprise or Datacenter edition only. >> > >> > >> > "Dave Kearney [MSFT]" <dkearney@online.microsoft.com> wrote in message >> > news:eRJaPU21EHA.1524@TK2MSFTNGP09.phx.gbl... >> >> Essentially you're talking about setting up an Exchange cluster. This >> >> solution requires a shared storage device that is accessible from both >> >> servers. Typically, this is an expensive SAN type fiber-channel >> >> configuration but can also be a Windows Storage Server based NAS >> >> solution >> >> if the server's load will be relatively light. >> >> >> >> I recommend reading the Exchange Server 2003 High Availability Guide. >> >> In >> >> particular, Chapter 5: Planning for Exchange Clustering may be of >> >> particular interest: >> >> http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3HighAvGuide/f68057dd-ccda-47f0-be5e-4090d39456b8.mspx >> >> >> >> -- >> >> -Dave >> >> >> >> This posting is provided "AS IS" with no warranties, and confers no >> >> rights. Use of included script samples are subject to the terms >> >> specified >> >> at http://www.microsoft.com/info/cpyright.htm. >> >> >> >> >> >> >> >> "felix" <felix(NO-SPAM)@eastop.com> wrote in message >> >> news:u7$bSO11EHA.824@TK2MSFTNGP11.phx.gbl... >> >>> My boss wants it to be setup so that when one Exchange server is >> >>> dead, >> >>> another one will be serving automatically. Now I'm thinking if I can >> >>> install >> >>> and configure 2 Exchange Servers in the office domain. Will that be >> >>> possible? How can this be done? Because the computer names can't be >> >>> the >> >>> same, how should I configure them? >> >>> >> >>> Please give me some advices and hints on it. Thank you very very >> >>> much. >> >>> >> >>> >> >> >> >> >> > >> > >> >> >>
- Next message: Dave Kearney [MSFT]: "Re: setup questions - Non Delivery reports"
- Previous message: Alan Sun [MSFT]: "Re: Migration wizard permissions error"
- In reply to: Greg Williams: "Re: More than one Exchange Server in a domain..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
