|
|
|
date: Tue, 30 Oct 2007 13:54:01 -0700,
group: microsoft.public.exchange.design
back
Re: Exchange 2003 Failover
Stretched clusters, 3rd party solutions like Neverfail, DoubleTake, et al.
Or of course you can consider looking at Exchange 2007. It will do what you
want out of the box. Actually, it'll be best out of the SP1 box when it's
released.
--
Neil Hobson
Exchange MVP
http://www.msexchange.org/Neil_Hobson/
http://www.msexchangeblog.com
"Brian Z" wrote in message
news:D8DFC0CF-F8F0-4937-AD6C-3FE9AF7E2188@microsoft.com...
> Hello,
>
> We have an Exchange 2003 SP2 server here on Windows 2003. Just a normal
> office setup with 50 users.
>
> The manager have been asking "what if" something happened to our site. How
> could we still function and do business.
>
> What I need to do is set up a 2nd Exchange server, in another state at a
> co-lo. This is also no problem.
>
> The issue is how can (in the even of a distaster) have the data on my
> primary, as well as the secondary? Is there an easier way then backing it
> all
> up to disk, then restoring it on the other server? I know about move
> mailboxes, but what if the first Exchange Server is totally gone?
>
> I read a few "High Availabilty Papers", but I don't see many people using
> those procedures.
>
> In this scenero, what are my options? My current idea would be to restore
> across the WAN, then change DNS to point at the other mail server.
>
> Thanks for your time.
>
> Brian
date: Wed, 31 Oct 2007 08:37:01 -0000
author: Neil Hobson [MVP]
Re: Exchange 2003 Failover
OK, what would I need to do this on 2 sites for Exchange 2007? How many
servers, do I also need to set up clustering? Do you have any whitepaper on
setting this up?
"Neil Hobson [MVP]" wrote:
> Stretched clusters, 3rd party solutions like Neverfail, DoubleTake, et al.
>
> Or of course you can consider looking at Exchange 2007. It will do what you
> want out of the box. Actually, it'll be best out of the SP1 box when it's
> released.
>
> --
> Neil Hobson
> Exchange MVP
> http://www.msexchange.org/Neil_Hobson/
> http://www.msexchangeblog.com
>
>
> "Brian Z" wrote in message
> news:D8DFC0CF-F8F0-4937-AD6C-3FE9AF7E2188@microsoft.com...
> > Hello,
> >
> > We have an Exchange 2003 SP2 server here on Windows 2003. Just a normal
> > office setup with 50 users.
> >
> > The manager have been asking "what if" something happened to our site. How
> > could we still function and do business.
> >
> > What I need to do is set up a 2nd Exchange server, in another state at a
> > co-lo. This is also no problem.
> >
> > The issue is how can (in the even of a distaster) have the data on my
> > primary, as well as the secondary? Is there an easier way then backing it
> > all
> > up to disk, then restoring it on the other server? I know about move
> > mailboxes, but what if the first Exchange Server is totally gone?
> >
> > I read a few "High Availabilty Papers", but I don't see many people using
> > those procedures.
> >
> > In this scenero, what are my options? My current idea would be to restore
> > across the WAN, then change DNS to point at the other mail server.
> >
> > Thanks for your time.
> >
> > Brian
>
>
>
date: Wed, 31 Oct 2007 05:44:02 -0700
author: Brian Z
Re: Exchange 2003 Failover
On Oct 30, 4:54 pm, Brian Z wrote:
> Hello,
>
> We have an Exchange 2003 SP2 server here on Windows 2003. Just a normal
> office setup with 50 users.
>
> The manager have been asking "what if" something happened to our site. How
> could we still function and do business.
>
> What I need to do is set up a 2nd Exchange server, in another state at a
> co-lo. This is also no problem.
>
> The issue is how can (in the even of a distaster) have the data on my
> primary, as well as the secondary? Is there an easier way then backing it all
> up to disk, then restoring it on the other server? I know about move
> mailboxes, but what if the first Exchange Server is totally gone?
>
> I read a few "High Availabilty Papers", but I don't see many people using
> those procedures.
>
> In this scenero, what are my options? My current idea would be to restore
> across the WAN, then change DNS to point at the other mail server.
>
> Thanks for your time.
>
> Brian
Here is an independant review of some of the 3rd party DR options that
are available for Exchange 2003, including LifeKeeper for Exchange
from my company, SteelEye Technology.
http://www.infoworld.com/article/06/10/02/40TCfailover_1.html
David A. Bermingham, MCSE, MCSA:Messaging
Director of Product Management
http://www.steeleye.com
date: Thu, 01 Nov 2007 20:17:11 -0700
author: daveberm
RE: Exchange 2003 Failover
If failure is not an option for your Exchange 2003 server then what we are
talking about is "Fault Tolorent" systems. For this, you should consider
Marathon Technologies (http://www.marathontechnologies.com)
If failure is acceptable with a quick recoverability then what we are
talking about is "High Availability" systems. For this, you should consider
moving your system to Exchange 2007 and take advantage of the CCR feature and
the SCR feature (due to be released with SP1).
Regards,
Leonard Lee
"Brian Z" wrote:
> Hello,
>
> We have an Exchange 2003 SP2 server here on Windows 2003. Just a normal
> office setup with 50 users.
>
> The manager have been asking "what if" something happened to our site. How
> could we still function and do business.
>
> What I need to do is set up a 2nd Exchange server, in another state at a
> co-lo. This is also no problem.
>
> The issue is how can (in the even of a distaster) have the data on my
> primary, as well as the secondary? Is there an easier way then backing it all
> up to disk, then restoring it on the other server? I know about move
> mailboxes, but what if the first Exchange Server is totally gone?
>
> I read a few "High Availabilty Papers", but I don't see many people using
> those procedures.
>
> In this scenero, what are my options? My current idea would be to restore
> across the WAN, then change DNS to point at the other mail server.
>
> Thanks for your time.
>
> Brian
date: Fri, 2 Nov 2007 06:25:03 -0700
author: Leonard Lee
|
|
