<div>
can your DR site connect to your ISP with the same account details (during failover) and then hence get the same IP settings?<br />
Simply have two routers at the DR site so when a disaster strikes you can connect witht the preconfigured second router?
</div>


can your DR site connect to your ISP with the same account details (during failover) and then hence get the same IP settings?
Simply have two routers at the DR site so when a disaster strikes you can connect witht the preconfigured second router?

<div>
Unfortunately we have two different ISPs -- our DR site is in a different state....
</div>


Unfortunately we have two different ISPs -- our DR site is in a different state....

<div>
Not sure if that's true yet by personal testing (since it's a live site) but if you've seen it done, that's very promising!
</div>


Not sure if that's true yet by personal testing (since it's a live site) but if you've seen it done, that's very promising!

<div>
<div class="content wysiwyg-content">
I am planning a DR site for our mail servers and am trying to muddle through a question....<br />
<br />
If our front-end server's public address is bound to a domain name -- this information being used to create an SSL certificate - &nbsp;how do you &quot;failover&quot; OWA and Activesync? &nbsp;If I redirect my webmail address to a new IP at the DR site, it will break the SSL cert. &nbsp;The webmail address is also the URL entered into the PDAs connecting via Activesync to the front-end server....<br />
<br />

</div>
</div>


I am planning a DR site for our mail servers and am trying to muddle through a question....

If our front-end server's public address is bound to a domain name -- this information being used to create an SSL certificate -  how do you "failover" OWA and Activesync?  If I redirect my webmail address to a new IP at the DR site, it will break the SSL cert.  The webmail address is also the URL entered into the PDAs connecting via Activesync to the front-end server....



Failover of Public Mail Services - Activesync &amp; OWA - to DR Site

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.

SSL / HTTPS

Disaster Recovery is the planning for and creation of policies and procedures related to the resumption or continuation of an organization's functions following a catastrophic event. The term is most frequently used in relation to failure of networks, but DR preparations also include other business systems and personnel considerations.

Failover of Public Mail Services - Activesync &amp; OWA - to DR Site

Failover of Public Mail Services - Activesync & OWA - to DR Site