Definitely very enlightening read. I've checked homemta attribute for the affected users and Rob as you had suggested they do reflect the actual value where the mb's live.
Steve, curious now how this would affect the MassExportmb ps1 you wrote if multiple DAG partners are involved. I'll ping you on your blog. Thanks On Tue, Nov 22, 2011 at 4:02 PM, Michael B. Smith <[email protected]>wrote: > I’m pretty sure a failover doesn’t update at all. I think a switchover > fires up an AD thread to start the update but times out after some number > of seconds to avoid causing a replication storm or times out when network > utilization hits a certain percentage; regardless it gets throttled. Ross > talked about this SOMEWHERE, but I can’t seem to lay my hands on the > presentation. It may not have been public.**** > > ** ** > > Regards,**** > > ** ** > > Michael B. Smith**** > > Consultant and Exchange MVP**** > > http://TheEssentialExchange.com**** > > ** ** > > *From:* Steve Goodman [mailto:[email protected]] > *Sent:* Tuesday, November 22, 2011 3:55 PM > > *To:* MS-Exchange Admin Issues > *Subject:* RE: Split DAG**** > > ** ** > > I agree, I’m not sure that Rajith’s article itself is correct as I’ve seen > it get updated most of the time, but I’ve definitely had people mention it > to me before, and seen it a few times myself on DAG switchovers (on > seemingly random mailboxes).**** > > ** ** > > Steve**** > > ** ** > > *From:* Campbell, Rob [mailto:[email protected]] > *Sent:* 22 November 2011 20:38 > *To:* MS-Exchange Admin Issues > *Subject:* RE: Split DAG**** > > ** ** > > Interesting.**** > > ** ** > > The article says:**** > > ** ** > > “Though Exchange 2010 doesn’t use the attributes homeMTA and > msExchHomeServerName, it populates both based on the server where the > database was active at the time of mailbox creation.”**** > > ** ** > > I recently had to rebuild all of my mailbox servers, and created them with > new names. The current setting on my HomeMTA reflects the new naming > convention, even though the mailbox was created before that server existed. > **** > > ** ** > > When I checked AD yesterday, the correct server was showing in the homeMTA > property. Today, the databases are active on another server in the DAG, > but the AD property on my mailbox is unchanged.**** > > ** ** > > It appears that Exchange may update that property in response to moving a > mailbox, but not in response to a DAG failover.**** > > ** ** > > ** ** > > ** ** > > *From:* Steve Goodman [mailto:[email protected]] > *Sent:* Tuesday, November 22, 2011 2:12 PM > *To:* MS-Exchange Admin Issues > *Subject:* RE: Split DAG**** > > ** ** > > I’ve seen this before – It was causing a script I wrote to tally up > mailbox counts per-database incorrectly. I was informed it is known about, > though.**** > > ** ** > > Since then I’ve seen it mentioned elsewhere, such as > http://www.howexchangeworks.com/2011/10/msexchhomeservername-and-homemta-are.html > **** > > ** ** > > Steve**** > > *Steve Goodman* | Technical Architect* > *Nuneaton, UK* > **www.stevieg.org*** > > ** ** > > *From:* Campbell, Rob [mailto:[email protected]] > *Sent:* 22 November 2011 00:24 > *To:* MS-Exchange Admin Issues > *Subject:* RE: Split DAG**** > > ** ** > > For any given mailbox, the homeMTA property of the user object in AD > should point to where the active copy is.**** > > ** ** > > For the users in question, is that set the same on all of your DCs?**** > > ** ** > > In Exchange 2007 you used to have to update this property manually if you > failed over to a replicated server. In 2010, I believe the CAS servers are > supposed to take care of this automatically. **** > > ** ** > > ** ** > > ** ** > > *From:* David Liu [mailto:[email protected]] > *Sent:* Monday, November 21, 2011 5:19 PM > *To:* MS-Exchange Admin Issues > *Subject:* Re: Split DAG**** > > ** ** > > Hi Rob, if you mean DC's as dactacentres, in running the same commad yes I > get the same results on mailboxes/CAS servers. **** > > ** ** > > I don't even know how this is possible if db is mounted on one server and > yet there can be mailboxes living on the passive/non-active node. **** > > On Mon, Nov 21, 2011 at 6:04 PM, Campbell, Rob < > [email protected]> wrote:**** > > Do you get the same results on all the DCs?**** > > **** > > *From:* David Liu [mailto:[email protected]] > *Sent:* Monday, November 21, 2011 4:49 PM > *To:* MS-Exchange Admin Issues > *Subject:* Split DAG**** > > **** > > hi, **** > > has anyone seen this before? **** > > **** > > Exchange 2010 SP1 RU5. **** > > 5 member DAG, 2 mb server in the primary datacenter (nyc1xmb001), 2 in DR > site (stm1xmb001) and one last one in Primary DC blocked from activation > for backup. **** > > **** > > I ran the following to gauge which users are on a particular mailbox > database, **** > > **** > > [PS] D:\Install\PowerShellScripts>get-mailboxdatabase NYC1XMB001_L_to_M | > get-mailbox**** > > **** > > Name Alias ServerName > ProhibitSendQuota**** > > ---- ----- ---------- > -----------------**** > > Minze, p pminze nyc1xmb001 463.9 MB > (486,400,000 bytes)**** > > Monica, t tmonica nyc1xmb001 unlimited**** > > Locklear, A alocklear stm1xmb001 unlimited**** > > Lipsky, E elipsky stm1xmb001 unlimited**** > > **** > > All users on nyc1xmb001_l_to_m should be hosted in the stm1xmb001 server > and yet both the GUI/commandline suggest that some mailboxes are living on > one in Primary DC and some on secondary Datacenter. **** > > **** > > How is this possible? **** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > ****************************************************************************************************** > > Note: **** > > The information contained in this message may be privileged and confidential > and **** > > protected from disclosure. If the reader of this message is not the intended > **** > > recipient, or an employee or agent responsible for delivering this message to > **** > > the intended recipient, you are hereby notified that any dissemination, **** > > distribution or copying of this communication is strictly prohibited. If you > **** > > have received this communication in error, please notify us immediately by > **** > > replying to the message and deleting it from your computer. **** > > ****************************************************************************************************** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > ** ** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > ****************************************************************************************************** > > Note: **** > > The information contained in this message may be privileged and confidential > and **** > > protected from disclosure. If the reader of this message is not the intended > **** > > recipient, or an employee or agent responsible for delivering this message to > **** > > the intended recipient, you are hereby notified that any dissemination, **** > > distribution or copying of this communication is strictly prohibited. If you > **** > > have received this communication in error, please notify us immediately by > **** > > replying to the message and deleting it from your computer. **** > > ****************************************************************************************************** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > ****************************************************************************************************** > > Note: **** > > The information contained in this message may be privileged and confidential > and **** > > protected from disclosure. If the reader of this message is not the intended > **** > > recipient, or an employee or agent responsible for delivering this message to > **** > > the intended recipient, you are hereby notified that any dissemination, **** > > distribution or copying of this communication is strictly prohibited. If you > **** > > have received this communication in error, please notify us immediately by > **** > > replying to the message and deleting it from your computer. **** > > ****************************************************************************************************** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist**** > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe exchangelist > --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe exchangelist
