30 to 45 seconds to see the failure and a few seconds to do an automated failover.
Derek A Johnson Sr. Systems Administrator National Association of Realtors 430 N. Michigan Ave. Chicago, IL 60611 Email: <mailto:djohn...@realtors.org> djohn...@realtors.org<mailto:djohn...@realtors.org> Cell: 262.496.9201 Desk: 312.329.8618 http://www.realtors.org Sent from my iPhone. Please excuse what auto correct can't catch or has auto not corrected. On Apr 6, 2011, at 17:38, "Sobey, Richard A" <r.so...@imperial.ac.uk<mailto:r.so...@imperial.ac.uk>> wrote: I can’t answer your cross site/continent question, but a database in a DAG is designed to failover when a database becomes unavailable for any reason, whether the hardware has failed, database access issue, or someone simple rebooted a server by accident :) Mail delivery continues as normal, Outlook users experience a brief period of disconnected state whilst it fails over and the CAS switches the client to the new database. Richard From: bounce-9312473-8066...@lyris.sunbelt-software.com<mailto:bounce-9312473-8066...@lyris.sunbelt-software.com> [mailto:bounce-9312473-8066...@lyris.sunbelt-software.com] On Behalf Of Kevan Dickinson Sent: 06 April 2011 23:09 To: MS-Exchange Admin Issues Subject: Questions about DAG's (Database Availability Groups) in exchange 2010 All. This is our Current setup. Exchange 2010 servers in the UK and the US both in the same Exchange organization. At the moment we are running a Windows 2003 Domain structure. The UK domain is a child domain of the US Domain. I was wondering if someone could answer a question for me about DAG’s in Exchange 2010. It is something I would like to understand in case we would like to implement it. My understanding of a DAG is that it is a replication of the Mailbox database attached to an Exchange 2010 server to another site / server in case the main database becomes corrupt. However what happens If the actual server that the mailbox database is attached to becomes unavailable will the users who have mailboxes on the unavailable server be automatically diverted to another server where the replicated database is? Or would you need to attach the replicated database to another server manually in order for users to become attached to their email again? What would happen in a situation like ours if say we replicated our Database to our office in the US and our server became unavailable. Would the office in the US need to manually mount our database on their server and then all our external and internal users need to change their outlook settings to look for client.USCompany.org<http://client.USCompany.org>? Instead of client.ukcompany.com<http://client.ukcompany.com> If so presumably there mail would then get routed via there anti virus / spam filtering software? I am trying to work out what is the best way to get better exchange redundancy in the event of either the An US Exchange 2010 server or ours being becoming unavailable? Presumably everything would be much easier if we had one Exchange Gateway, or does this not matter really? At the moment email in the UK enters via our Mail gateway / anti virus and anti spam system and email in the US enters via there gateway. You help and comments would be appreciated. Regards Kevan ******************************************************************************** ***Disclaimer*** The contents of this Email may be privileged and are confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Should you wish to use Email as a mode of communication, NSF-CMi Ltd and its subsidiaries are unable to guarantee the security of Email content outside of our own computer systems. This footnote also confirms that this Email message has been checked by MailMarshal for the presence of computer viruses. Whilst we run anti-virus software, you are solely responsible for ensuring that any Email or attachment you receive is virus free. We disclaim any liability for any damage you suffer as a consequence of receiving any virus. NSF-CMi Ltd Registered in England No: 1899857 Registered Office : Hill House, 1 Little New Street, London, EC4A 3TR. ********************************************************************************** --- To manage subscriptions click here: <http://lyris.sunbelt-software.com/read/my_forums/> http://lyris.sunbelt-software.com/read/my_forums/ or send an email to <mailto:listmana...@lyris.sunbeltsoftware.com> listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: <http://lyris.sunbelt-software.com/read/my_forums/> http://lyris.sunbelt-software.com/read/my_forums/ or send an email to <mailto:listmana...@lyris.sunbeltsoftware.com> listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
