RE: Secondary exchange server and automatic spooling
- From: Jabber Wock <jabberwock99@xxxxxxxxx>
- To: "[ExchangeList]" <exchangelist@xxxxxxxxxxxxx>
- Date: Mon, 26 Sep 2005 11:44:57 -0400
Hi Michael,
You've also got some misunderstandings how OSTs work. If you connect a
> profile to another server, a new OST will be created.
>
Good point ... thanks for the clarification.
> I think you need to take a step back and take a look at your solution
> from a fresh perspective. Examine NeverFail and DoubleTake and MessageOne
> (there are other players in this space, but those are probably the big
> names).
>
Actually I considered those apps. and I do not need them. I am not trying
to maintain an up-to-date live replica of my primary Echange server, on the
backup Exchange server. During normal operation, the backup Exchange server
will be "empty", not receiving or sending anything, nor being quietly
duplicated.
When the primary fails, email will start arriving at the backup mailserver
(because in the DNS it is set up as a secondary MX). However instead of
being a traditional "store and foreward" secondary MX, this backup
mailserver will have live accounts already pre-configured so users will be
able to connect their standby profiles (or switch to their live profile to
this backup) and will see their newly arrived emails, and will be able to
send emails, and use OWA etc. until the main server comes back on line
again. There is no requirement that the backup server keep itself sync'd up
in preparation for the disaster (yes I know that sounds strange but thats
the spec). Hence no need for neverfail etc. Yes the backup server will not
have historical data but apparently that is OK.
But what is needed is the ability to flush all incoming email that has
accumulated in each inbox, to the corresponding mailbox on teh main server,
when the mailserver comes back on line.
JW
------------------------------
>
> *From:* Jabber Wock [mailto:jabberwock99@xxxxxxxxx]
> *Sent:* Monday, September 26, 2005 10:56 AM
> *To:* [ExchangeList]
> *Subject:* [exchangelist] Secondary exchange server and automatic spooling
>
> http://www.MSExchange.org/ <http://www.msexchange.org/>
>
> Hi,
>
> I have set up two exchange servers, one as primary and one as backup. The
> two are far apart across the Internet (many hundreds of miles apart). There
> is no Active Directory connection between them, i.e. they are not in the
> same forest, no "trust relationships" between them etc., and they do not
> have the same AD DOMAIN name and no VPN between them. This is intentional,
> for reasons I won't go into here to avoid clouding the question.
>
> The primary mailserver and backup mailserver are both configured with the
> same user accounts. The intent is that if the primary fails disastrously for
> a prolonged period, users will switch their profiles manually to the backup
> server and will have send and receive and OWA capability (not just storage
> for received emails but no send or OWA as with a secondary MX mailserver).
> Of course, the historical content will not be visible immediately but that
> will be in the OST files so in cached mode, should get sync'd up.
>
> The question is: when the primary server comes back on line, how do we
> ensure that all the email that was received on the secondary server,
> automatically gets spooled to the primary? is there a way of "flushing" or
> "spooling" this data from the backup server to the primary server?
>
> best regards
>
> JW
>
> ------------------------------------------------------ List Archives:
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange
> Newsletters:
> http://www.msexchange.org/pages/newsletter.asp------------------------------------------------------
> Visit
> TechGenix.com for more information about our other sites:
> http://www.techgenix.com------------------------------------------------------
> You are currently
> subscribed to this MSEXchange.org Discussion List as: michael@xxxxxxxxxxxx
> unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Report abuse to
> listadmin@xxxxxxxxxxxxxx
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> ------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> ------------------------------------------------------
> You are currently subscribed to this MSEXchange.org Discussion List as:
> eoml@xxxxxxxxxxxxxxxxx
> To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
>
> ________________________________________________
>
> If this email contains a quotation then unless otherwise stated
> it is valid for 7 days and offered subject to Silversands standard
> Terms and Conditions, a copy of which is available on request.
>
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual to whom it is addressed.
> If you have received this email in error, or if you believe this email
> is unsolicited and wish to be removed from any future mailings, please
> contact our Support Desk immediately on 01202 360360 or email
> helpdesk@xxxxxxxxxxxxxxxxx
>
> Any view or opinions presented are solely those of the author and do
> not necessarily represent those of Silversands.
>
> ________________________________________________
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> ------------------------------------------------------
> Visit TechGenix.com for more information about our other sites:
> http://www.techgenix.com
> ------------------------------------------------------
> You are currently subscribed to this MSEXchange.org Discussion List as:
> jabberwock99@xxxxxxxxx
> To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
>
Other related posts:
