Exchange 2010 DAG's - 4 Mailbox Servers in 2 Datacenters with per site redundancy

I recently came into a company with an Exchange 2010 sp1 environment where there are two data centers in two different subnets (10.70.62.0 and 10.80.56.0)
Each datacenter has 2 mailbox servers (4 servers total) but their plan was to have only enough storage space to host 1/2 of the databases on each server. So instead of server 1, 2, and 3 being copies of each other, ServerA is a copy of ServerA and ServerB
is a copy of ServerB
Server     -            Databases
Site1mbA - Primary Database copy 1-10
Site1mbB - Primary Database copy 11-20
Site2mbA - Secondary Database copy 1-10
Site2mbB - Secondary Database copy 11-20
Normally if there were enough storage space I would keep a copy on each server and replicate within 1 DAG.
However since not all the databases are on each member server do I need to use 2 DAGS? 1st for Site1mbA & Site2mbA and 2nd for Site1mbB & Site2mbB
I feel I would need the 2 DAG's because with 1 DAG if Site1mbA server went offline the DAG couldn't switch to the Failover Cluster IP for Site2 because there are still active mailboxes in Site1 on Site1mbB.
Does that make any sense or am I over complicating it?
Thanks!

There is no rule that every server in a DAG must have a copy of every Database. You could do this with one DAG, but if the WAN goes down then the DAG will be active in only a single site not both.
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx#FourTwo
As illustrated in the previous example, using a single four-member DAG extended across two datacenters can provide high availability and site resilience for the mailbox services and data. However, if a WAN outage occurs, only the primary datacenter retains
service because it contains the majority of the voters. The datacenter with the minority of voters loses majority, and the DAG members in that datacenter lose quorum and go offline.
To deploy highly available Mailbox servers in a multiple datacenter environment, where each datacenter is actively serving a local user population, we recommend that you deploy multiple DAGs, where each DAG has a majority of voters in a different datacenter,
as illustrated in the following figure.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne 
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Similar Messages

  • Decommissioning Exchange 2010 Casarray (contains 2013 Mailbox Servers?)

    I'm in the process of decommissioning exchange 2010. I went to remove the 2010 casarray and see that my 2013 mailbox servers are a part of the array? Can I still remove the array? Do I leave it?

    Hi,
    Please have a look in to the below mentioned article especially the reply from Off2work
    http://social.technet.microsoft.com/Forums/office/en-US/c10550fa-b735-48ee-ad52-a75f0176e1de/cas-array-in-exchange-2013?forum=exchangesvrdeploy
    As an additional info , as per my knowledge there is no use of cas array in exchange 2013 and at the same time exchange 2013 servers will not make use of it even though if it is an member of an casarray in exchange 2010.
    Please reply me if you have any queries .
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange 2010 dag with only 2 servers

    I have my exchange 2010 running on win server 2012 R2 and I have installed another exchange 2010 server with the same FQDN and I want to configure DAG with only these 2 servers. Can I implement DAG with only 2 servers?Can the mailbox,client access and hub
    transport roles still work with only 2 servers? If Mailbox and Hub transport could work it will be fine for me as CAS switchover can always be done manually.My main concern is securing data. Any article on how to implement that would be highly appreciated.
    Thanks

    Hi,
    Yes, we can create a DAG with 2Servers and Each server can have upto 100 database depends upon Standard or Enterprise.
    Here is a great link that explains about DAG
    Exchange 2010 DAG Installation
    Mark as Answer/Helpful Post if it helps
    Regards.
    Naren Neelam, Messaging Consultant, ITBigBang (P) Ltd Www.ITBigBang.Com | Hire Us for Messaging Consulting

  • Exchange 2010 dag migration to exchange 2013 help

    If I want to use the Same mailbox servers and upgrade them to exchange 2013, what is the recommended way? I have a 4 member exchange 2010 DAG.
    I was thinking (where A,B,C,D are mailbox servers, A,B are in one site and C,D another active directory site):
     A  B  -------------- C D
    Remove A and C from the 2010 DAG, Format and install Exchange 2013 on both, and create a 2013 dag :
    A1 ----------- C1
    B ------------- D
    Then move across all mailboxes from B to A1. Upgrade B and D to exchange 2013 and put them in the DAG
    A1 B1 ----------- C1 D1
    Does this make sense ? I am trying to do this while having as much high availability as possible during the transition. I have no extra servers so I have to use the existing server hardware.
    Anand_N

    Hi,
    When you want to migrate a DAG from Exchange 2010 to Exchange 2013, you should first remove the mailbox server from the DAG in Exchange 2010 and then move mailboxes from database in this mailbox server to Exchange 2013. After all mailboxes have been migrated
    to the Exchange 2013 mailbox server, when the new server is ready, it can become a member of the Exchange 2013 DAG.
    Here is an article about migration DAG from Exchange 2010 to Exchange 2013 for your reference.
    Migrating an Exchange 2010 DAG to Exchange 2013
    http://windowsitpro.com/blog/migrating-exchange-2010-dag-exchange-2013
    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make
    sure that you completely understand the risk before retrieving any suggestions from the above link.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 DAG netowrk replications issues - Causing database copies to be disconnected and resynchronizing.

    My
    environment is as follows.<o:p></o:p>
    We have 3 exchange 2010 servers.<o:p></o:p>
    EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
    EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
    The dag is configured to to communicate to all three.<o:p></o:p>
    The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
    The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
    DREX1 is located in another network. It is in another building connected via vpn. The ip
    for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
    (These are not the actual address, but the concept is similar)<o:p></o:p>
    The dag network configuration is as follows.<o:p></o:p>
    DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
    DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
    and 192.168.100.52<o:p></o:p>
    DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
    160.100.3.51 and 160.100.3.52<o:p></o:p>
    Last Friday, 3/7/14 something happened.<o:p></o:p>
    To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
    full backups of our exchange databases when I reviewed the backup jobs, the
    exchange database backups using dpm2010 failed all weekend long starting at
    11:00pm that Friday.<o:p></o:p>
    The issue that occurred was that the database copies went to a status of Disconnected and
    Resynchronizing, and after about 30 seconds, the status would show
    Resynchronizing.<o:p></o:p>
    All attempts to resolve this with the research methods failed.  Deleting the
    logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
    Creating a new database worked, creating a database copy worked, but seeding the copy
    failed. All with the same pattern, a status of Disconnected and
    Resynchronizing, and after about 30 seconds, and the status would show
    Resynchronizing.<o:p></o:p>
    The database was mounted on EX2, and seeding to EX1
    DREX1 has no issues.<o:p></o:p>
    All the DAG networks were in a good status, all Green and all up.  I could ping from
    EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
    In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
    fix, but after rebooting EX2, it all resolved.  It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
    was all healthy.<o:p></o:p>
    We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
    issue occurred; a status of Disconnected and Resynchronizing, and after about
    30 seconds, the status would show Resynchronizing.<o:p></o:p>
    The database was mounted on EX2 and seeding to EX1 again. I did not notice the
    issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
    Late Monday morning, my boss and I were looking at more articles, but all the same results,
    delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
    I mentioned that it was strange because the networks were all up. What made us try the next
    scenarios was just "luck" I guess. I made a statement about not remembering
    which networks DAG replication took place over.  Again, we have a LAN and
    a BACKUP network.  Bother were listed to use replication, so we decided to
    disable replication over the BACKUP network in the EMC. Immediately, the
    database copies switch to healthy and started seeding.<o:p></o:p>
    Later that evening I enabled replication over the BACKUP network and it failed again with
    a status of Disconnected and Resynchronizing, and after about 30 seconds, the
    status would show Resynchronizing.  I disabled the replication over the
    BACKUP network and the database copy went back to healthy<o:p></o:p>
    The last round of windows updates were pushed to these boxes the Friday before the
    issues began, 2/28/14.  I don't believe the updates to be the issue. <o:p></o:p>
    Can anyone make any suggestions as to where to look?  It worked with the BACKUP
    network enabled to so long that is eluding me as to why the issues would start
    all of a sudden. I am also confident that the switch configuration for the
    BACKUP network has not been changed at all in at least 2-3 months.  I am
    still open to look at the config. Please help if you can.<o:p></o:p>
     <o:p></o:p>
    Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
    the database copies so that I can be alerted when the status changes.  We
    use WhatsUpGold 16.2 to monitor the devices.  <o:p></o:p>
    Thanks for any future assistance.<o:p></o:p>
    Ian
    Ian

    You don't have to enable the Replication on Backup Network.
    You should collapse your DAG network.
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
    http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
    Post the result of Below command:
    Get-DatabaseAvailabilityGroupNetwork 
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 DAG and NIC Teaming | Team broke and now cluster doesn't see the box

    Hello everyone,
    Question for the group. We are running an Exchange 2010 DAG cluster with four boxes with active/passive DB's on each of the four boxes. We run HP boxes for Exchange and the NIC's are teamed. Now mind you, I arrived at this company well after this environment
    was set up so I have inherited everything here.
    What has happened is one of the four boxes had an issue after an otherwise normal reboot. We could no longer ping it. Logged into the ILO and was able to log into the server, only to discover its team NIC was messed up and our only option was to rebuild
    the team NIC. So I rebuilt the team and gave it the original IP/subnet/gateway it had. The server reboots and we can ping it.
    However, when I look in the EMC at Database Management, all the passive copies that were on that DB are showing Failed. Ok, so I suspend the copy and attempt to reseed. No luck. I get the error "The NetworkManager has not yet been initialized"
    and it references my machine which had the bad team NIC. Curious, I go look at my Failover Cluster Manager.
    Looking at the fail over cluster manager, I notice a X on the cluster and I am showing my server which had the bad team NIC being listed as down. I attempted to start the cluster service for the machine, but it did not work.
    Is there something I a missing? What are my exact steps to take to get my cluster configuration working correctly again and see my box? Do I need to remove the box from the DAG, evict it from the cluster, and rejoin it again? If so, can I do this without
    affecting the other three machines so users don't notice any outage?
    Thanks for any help you can give!

    Hi Kyle,
    I am Chetan Savade from Symantec Technical Support Team & sorry to know the problem you faced because of SEP.
    Symantec recommends that the Exchange server's OS always be protected by the latest available release of SEP.  The Exchange server's message flow and Information Store must be protected by a dedicated mail security product, such as Symantec
    Mail Security for Microsoft Exchange. 
    For cluster environment I would recommend to follow this article:
    Installing the Symantec Endpoint Protection client to a Windows cluster server
    http://www.symantec.com/docs/TECH91154
    Installation best practices for Endpoint Protection on Windows servers
    http://www.symantec.com/docs/TECH91154
    Best Regards,
    Chetan

  • Exchange 2010 DAG backup & Transaction logs

    Hi, 
    What is Microsoft recommended best practise for Exchange DAG group backup in an environment where there are Active & multiple (2-3) passive copies of the databases?
    Is it a good practice to backup transaction logs as frequently as possible in addition to daily full backup ? This I belive will allow to restore the DB to the latest possible state
    using last good full backup & transaction logs (Like restoring SQL databases)
    Thanks

    Hi,
    Windows Server Backup can't backup passive copy. If you want to backup both active and passive copies, you need to use DPM or other third party.
    Here is a similar thread for your reference.
    Exchange 2010 DAG Backup Best Practices
    http://social.technet.microsoft.com/Forums/exchange/en-US/269c195f-f7d7-488c-bb2e-98b98c7e8325/exchange-2010-dag-backup-best-practices
    Besides, here is a related blog below which may help you.
    Backup issues and limitations with Exchange 2010 and DAG
    http://blogs.technet.com/b/ehlro/archive/2010/02/13/backup-issues-and-limitations-with-exchange-2010-and-dag.aspx
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010 Conference Room Resource mailbox. Additional text field HTML images

    In the same vein as this question:
    http://social.technet.microsoft.com/Forums/systemcenter/en-US/338b4fff-e8df-41aa-8066-a32a9f76fa92/exchange-2010-conference-room-resource-mailbox-additional-text-field
    Have successfully created Additional text messages that actually work with a surprising amount of HTML in it (Tables, link colours, hyperlinks etc...)
    The one thing we can't seem to crack is the ability to show images, is this possible?
    (have tried the usual suspects of:
    img src="x.jpg"
               also tried making sure the img tag was self closing, no luck
    td background="x.jpg"
    td background (css property)
    but no joy and ran out of ideas, any help out there?
    Many thanks in advance!

    Have you tried the same formatting that is required to add an image in a disclaimer:
    http://technet.microsoft.com/en-us/library/bb124352.aspx#Images

  • Removing mailbox server from Exchange 2010 DAG - Node not fully cleaned up

    Hi,
    We are in the process of decommissioning some old Exchange 2010 servers. I have just attempted to remove one of our mailbox servers and have received a number of errors, related to its removal from the DAG.
    I have already removed the Public Folder replicas and all mailbox database copies. I then tried to evict the server from the DAG and received the following warning:
    I then ran the command that was recommended, from another server and in an administrative command prompt:
    I have looked in this log on both the server I ran the command on, a CAS server, and the mailbox server itself and can see no evidence of this error 2 that is listed here.
    If I run the Powershell command to look at the DAG I cannot see it there any more. I am assuming that this error message might only be an issue if I was planning on re-using this server somewhere else in Exchange or perhaps adding this server to another
    DAG. But I just want to decommission it.
    Can anyone put my mind at rest as to whether this is a genuine concern or not. If not my next step is to uninstall Exchange 2010 from this server and turn it off.

    Hi Belinda,
    I get the following:
    [PS] C:\Windows\system32>Get-DatabaseAvailabilityGroup
    Name             Member Servers                                                         
    Operational Servers
    DAG01            {WSR-EX-01, WSR-EX-101, WSR21}
    It doesn't look like that server is part of the DAG any more as far as I can see. I just can't explain that error message reported from the cluster command. As far as I can see the server is isolated. I already removed its database copies as a pre-requisite
    before removing it from the DAG as per this guide:
    http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_27039933.html
    I found a nice little script that gave reports on your Public Folder configuration and it highlighted that some of our folders were not being replicated properly across our mailbox servers. This helped me in removing these services from the server.
    It is currently doing nothing at this time as far as Exchange Services are concerned.

  • Mailbox Databases - 1500 users Exchange 2010 DAG

    I have the following setup for a 5 server DAG setup and would like to know the recommended setup for high availability for all user databases. I would like the databases copied to several DAG members servers, but am unsure as to how i should stagger the
    database replication. Please see the drive sizes below and send me feedback/recommendations.
    Each of my DAG member servers (mailbox servers) has the following storage space available:
    C:\60GB(O/S), D:\1TB(Mailboxes), E:\1TB(Mailboxes) F:\(logs)
    How many databases should i create to maximize efficiency and give best user performance/experience?
    To how many DAG member servers should i copy the database in order to achieve a reasonable amount of High Availability?
    Again, I have 1500 users and 2TB per server to accommodate mailbox databases.
    Users average 500MB mailbox quotas.
    Can i create the DAG replicas on the second drive (E:\) or should i just use both terabyte volumes exclusively for users mailboxes?

    Hi,
    5 members in a DAG and one database created for every member, I suggest you create three copys for a database like the following figure. Any two servers corruption couldn't interrupt any client connection.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Sean Xiao
    TechNet Community Support

  • Exchange 2010 DAG Failover does not works

    Hi Experts,
    I have a Exchange 2010 setup in  a DAG environment. We have 2 MBX servers in the main site and 1 MBX server in the DR site , all part of one DAG. We have 2 HUB/CAS servers in the main site and 1 HUB/CAS server in the DR site.
    Recently we had to do our BCP test for audit purpose. We had issues in doing failover to the DR site and below is the error faced.
    Please advise urgently on the possible causes and resolution steps for it as we need to do this test again on the coming weekend.
    "EvictDagClusterNode got exception Microsoft.Exchange.Cluster.Replay.AmClusterEvictWithoutCleanupException: An Active Manager operation failed. Error An error
    occurred while attempting a cluster operation. Error: Evict node 'sme-ho-mbx01' returned without the node being fully cleaned up. Please run cluster.exe node <NodeName> /forcecleanup to complete clean up for this node.. ---> System.ComponentModel.Win32Exception:
    The wait operation timed out"
    So, basically one of the MBX server was not evicting from the Cluster due to which failover did not work.
    Would appreciate some urgent thoughts for the possible resolution.
    regards
    abubakar
    Md.Abubakar Noorani IT Systems Engineer Serco Ltd.

    Hi,
    Yes, you can run the Stop-DatabaseAvailabilityGroup without shutting down the Mailbox server. During the process of DAG failover to DR site, the Stop-DatabaseAvailabilityGroup cmdlet should be run against all servers in the primary datacenter. If the Mailbox
    server is unavailable but Active Directory is operating in the primary datacenter, the Stop-DatabaseAvailabilityGroup command with the ConfigurationOnly parameter must be run against all servers in this state in the primary datacenter.
    And please note that the Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of DagOnly. 
    Based on the error message, it seems that you should run the cluster node nodename /forcecleanup cmdlet against the specified node in the main site. Have you tried this to check the result?
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange 2010: Remove high available mailbox database error

    Hello everyone,
    I have a two node DAG exchange 2010 and recently split one mailbox database into two databases. 
    Now when removing the original database I get the following error:
    Please provide specific details.
    The following was done thus far:
    Deleted all softdeleted items
    this is not the default mailbox database
    Suspended the second mail server and removed it from mailbox, leaving now just one mail server attached to the mailbox database.
    Help

    Try to check mailbox import request is there or no by this command. Get-MailboxImportRequest. If you can see any requests listed. Remove it by this command Get-MailboxImportRequest | Remove-MailboxImportRequest.
    Thanks, MAS
    Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Can't move Exchange 2003 mailbox to Exchange 2010 Resource forest (Linked Mailbox)

    Problem Description:
    Can’t move Exchange 2003 mailbox to Exchange 2010 resource forest
    Error message:
    Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials.
    Source Environment Configuration:
    Active Directory
    FQDN: umfolozi.local
    Domain name (pre-Windows 2000): UMFOLOZI
    Domain Function Level: Windows Server 2003
    Domain Controllers:
    Hostname
    OS
    Operation Master
    SRVUMVMDC01.umfolozi.local
    Windows Server 2008 R2 Standard SP1
    Schema Master, Domain Naming, RID, PDC
    SRVUMVMDC01.umfolozi.local
    Windows Server 2008 R2 Standard SP1
    Infrastructure
    Exchange
    Version: Microsoft Exchange 2003 Standard SP2 Build 7638.2
    Server Information:
    Hostname
    OS
    TUSKUMFMAIL.umfolozi.local
    Windows Server 2003 R2 SP2
    DNS Zones
    Zone Name
    Zone Type
    Domain Controllers
    umfolozi.local
    Active Directory-Integrated (Primary)
    SRVUMVMDC01.umfolozi.local
    SRVUMVMDC01.umfolozi.local
    peermont.com
    Secondary
    SRVPGVMDC01.peermont.com
    SRVPGVMDC02.peermont.com
    Trusts
    Domain Name
    Trust Type
    Transitive
    Validated
    peermont.com
    Forest
    Yes
    Yes
    Target Environment Configuration:
    Active Directory
    FQDN: peermont.com
    Domain name (pre-Windows 2000): PG
    Domain Functional Level: Windows Server 2008 R2
    Domain Controllers:
    Hostname
    OS
    Operation Master
    SRVPGVMDC01.peermont.com
    Windows Server 2008 R2 Std SP1
    SRVPGVMDC02.peermont.com
    Windows Server 2008 R2 Std SP1
    Domain naming, RID, PDC, Infrastructure, Schema Master
    Exchange
    Resource Exchange Forest
    Server Information:
    Hostname
    OS
    Role
    Version
    Client Access Array
    SRVPGVMEXCH01.peermont.com
    Windows Server 2012 Std
    HUB, CAS
    Version 14.3 (Build 123.4)
    exchange.peermont.com
    SRVPGVMEXCH02.peermont.com
    Windows Server 2012 Std
    HUB, CAS
    Version 14.3 (Build 123.4)
    exchange.peermont.com
    Hostname
    OS
    Role
    Version
    Database Availibility Group
    SRVPGVMEXCH03.peermont.com
    Windows Server 2012 Std
    MBX
    Version 14.3 (Build 123.4)
    PeermontDAG
    SRVPGVMEXCH04.peermont.com
    Windows Server 2012 Std
    MBX
    Version 14.3 (Build 123.4)
    PeermontDAG
    DNS Zones
    Zone Name
    Zone Type
    Domain Controllers
    peermont.com
    Active Directory-Integrated (Primary)
    SRVPGVMDC01.peermont.com
    SRVPGVMDC02.peermont.com
    umfolozi.local
    Secondary
    SRVUMVMDC01.umfolozi.local
    SRVUMVMDC01.umfolozi.local
    Trusts       
    Domain Name
    Trust Type
    Transitive
    Validated
    umfolozi.local
    Forest
    Yes
    Yes
    Migration Process
    Task
    Description
    Successful/Error
    1
    SYNC AD Domain account from source forest (umfolozi.local) to target forest (peermont.com) using BinaryTree SMART Directory Sync (ADMT can be used as alternative)
    Successful
    2
    Create mailed enabled user
    Successful
    3
    Run Prepare-MoveRepuest with –OverWriteLocalObject
    Command Example:
    .\Prepare-MoveRequest.ps1 -Identity [email protected] -RemoteForestDomainController SRVUMVMDC01.umfolozi.local
    -RemoteForestCredential $RemoteCredentials -UseLocalObject -LocalForestDomainController SRVPGVMDC01.peermont.com -LocalForestCredential $LocalCredentials -OverWriteLocalObject
    Successful
    4
    Submit mailbox request
    Command Example:
    New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeliveryDomain
    "internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Credential "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True
    Error
    All the standard migration task works as expected until the mailbox migration move request is submitted. See move request verbose detail below:
    [PS] C:\Windows\system32>New-MoveRequest -Identity "0fa7d17e-3637-4708-a51b-f14eaae17968" -BadItemLimit "50" -TargetDeli
    veryDomain "internal.peermont.com" -TargetDatabase "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" -RemoteCredential (Get-Crede
    ntial "umfolozi\svcmigration") -RemoteGlobalCatalog "SRVUMVMDC02.umfolozi.local" -RemoteLegacy:$True -Verbose
    VERBOSE: [11:34:27.346 GMT] New-MoveRequest : Active Directory session settings for 'New-MoveRequest' are: View Entire
    Forest: 'False', Default Scope: 'peermont.com', Configuration Domain Controller: 'SRVPGVMDC02.peermont.com', Preferred
    Global Catalog: 'SRVPGVMDC02.peermont.com', Preferred Domain Controllers: '{ SRVPGVMDC02.peermont.com }'
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Runspace context: Executing user: peermont.com/Admin/Users/Admin
    Accounts/Information Technology/SoarSoft/Johann Van Schalkwyk, Executing user organization: , Current organization: ,
    RBAC-enabled: Enabled.
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Beginning processing &
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Instantiating handler with index 0 for cmdlet extension agent "Admin
    Audit Log Agent".
    WARNING: When an item can't be read from the source database or it can't be written to the destination database, it
    will be considered corrupted. By specifying a non-zero BadItemLimit, you are requesting that Exchange not copy such
    items to the destination mailbox. At move completion, these corrupted items won't be available in the destination
    mailbox.
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Searching objects "{c5d6ea95-07b3-4a52-9868-e41e808a76fe}" of type
    "MailboxDatabase" under the root "$null".
    VERBOSE: [11:34:27.362 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
    VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
    Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope(s):
     {}, Exclusive Configuration Scope(s): {} }
    VERBOSE: [11:34:27.393 GMT] New-MoveRequest : Searching objects "0fa7d17e-3637-4708-a51b-f14eaae17968" of type "ADUser"
     under the root "$null".
    VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Previous operation run on domain controller 'SRVPGVMDC02.peermont.com'.
    VERBOSE: [11:34:27.471 GMT] New-MoveRequest : Processing object "$null".
    VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] No RequestJob messages found.
    VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MDB c5d6ea95-07b3-4a52-9868-e41e808a76fe found to belong to Site:
     peermont.com/Configuration/Sites/Peermont
    VERBOSE: [11:34:27.487 GMT] New-MoveRequest : [DEBUG] MRSClient: attempting to connect to 'SRVPGVMEXCH02.peermont.com'
    VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] MRSClient: connected to 'SRVPGVMEXCH02.peermont.com', version
    14.3.178.0 caps:07
    VERBOSE: [11:34:27.627 GMT] New-MoveRequest : [DEBUG] Loading source mailbox info
    VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Failed to reconnect to Active Directory server
    SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that you have used the correct credentials. --> A
    local error occurred.
    VERBOSE: [11:34:28.844 GMT] New-MoveRequest : Admin Audit Log: Entered Handler:OnComplete.
    Failed to reconnect to Active Directory server SRVUMVMDC02.umfolozi.local. Make sure the server is available, and that
    you have used the correct credentials.
        + CategoryInfo          : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
        + FullyQualifiedErrorId : F48FD74B,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
        + PSComputerName        : srvpgvmexch02.peermont.com
    VERBOSE: [11:34:28.859 GMT] New-MoveRequest : Ending processing &
    Troubleshooting Performed
    1. When submitting mailbox move request tried the following credential inputs:
    1.1. DOMAIN\Username
    1.2. FQDN\Username
    1.3. userPrincipalName
    2. Confirmed domain trust between source and target domain is in place and validated.
    3. Confirmed name resolution in source and target domain is functioning as expected.
    4. Confirmed network connectivity between source and target domain controllers as well as source and target exchange servers.
    5. Tried to create new Linked Mailbox to account in source forest, can’t select Global Catologue via the wizard;
    Tried to specify the credentials for the account forest and got the following error when tried to select Global Catalog from wizard:

    The error talk about the credential. Did you check the credential
    Did you tried this command?
    New-MoveRequest -Identity "Distinguished name of User in Target Forest" -RemoteLegacy -TargetDatabase "E2K10 Mailbox Database Name" -RemoteGlobalCatalog "FQDN of Source DC" -RemoteCredential $Remote -TargetDeliveryDomain "Target
    domain name"
    http://blogs.technet.com/b/exchange/archive/2010/08/10/3410619.aspx
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 DAG Replication - too much data crossing the wire

    I’m replicating 3 Exchange databases from our production active Exchange 2010 server across the WAN to another passive Exchange 2010 server at our DR site. 
    The Exchange server at the DR site does not have any active databases, i.e. no users are hitting that server. 
    We are running Update Rollup 8 for Exchange Server 2010 SP1 on both these servers. 
    The two sites are connected via a 10Mb/s MPLS connection and all the databases are in sync and the replication is working fine. 
    I have setup a network sniffer at the primary site and see a sizable amount of data crossing the wire from the production Exchange server to the DR Exchange server. 
    When I query the production Exchange server using the Tracking Log explorer and only choose the EventID ‘RECEIVED’ that should show me the amount of data that has been committed to the database. 
    If I choose a date range that is the same exact range that I have used to capture the raw data with my sniffer the amount of data the sniffer shows crossing the wire is 10 fold compared to what the Tracking Log Explorer shows. 
    If I actually count up the data in the LOG files it is about 20% more than what is crossing the wire but that seems to be because the DAG is compressing the data. 
    If in a one hour timeframe there is 500MB of data crossing the wire to the DR Exchange server the tracking log explorer will show only 50MB. 
    I would like to know why the data crossing the wire far exceeds the amount of data that is truly being sent/received from the primary exchange server. 
    Perhaps I’m simply not getting a true view of the amount of data being committed to the exchange server using the Tracking Log Explorer. 
    Maybe there is a better way to report how much data is being committed to the exchange databases. 
    Any assistance would be appreciated…

    Two things.
    1 - you must update Exchange to SP3 and a recent RU.  Willard has already provided the links, which point back to my blog if you want to see the lifecycle map for Exchange 2010.  SP1 has been out of support since January 2013.  Time to move
    on pllease
    2 - Looking at the tracking log is not sufficient.  I would not expect that to show everything.
    I want to know what traffic you see as excessive.  What ports are you seeing used here?
    My money is on content indexing.  CI will use additional traffic over and above log repl traffic.  Expect CI traffic to be roughly the same again.  You can test this by disabling CI on the database or stopping the services on the DR server. 
    To disable the CI for the database:
    Set-MailboxDatabase DBName -indexEnabled $False
    Or stop the Exchange search services on the DR box to leave production unaffected.
    Again - you need to update Exchange.  You would be better to do that now rather than when something breaks and Microsoft support cannot fully assist you since you are not uptodate.    I'll leave discussion of the security issues resolved
    in recent Exchange RUs aside. 
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 to 2013 migration: Mailbox move requests are journaled.

    Hello,
    I've installed Exchange 2013 into Exchange 2010 infrastructure
    [ single Exchange 2010 server; single AD site; AD = 2003 ],
    Exchange 2010 has 2 databases:
    1. Database with users mailboxes;    Journaling YES: Journal account.
    2. Database with 1 mailbox for Journal user mentioned above:     Journaling NO.
    Exchange 2013 has 1 database:
    1. Database with moved users mailboxes;    Journaling YES: Journal account.
    I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !
    I logged into Journal mailbox by OWA and didn't see any duplicate messages concerned with this mailbox user...
    I'd like:
    * to understand technically what happened,
    * to avoid unnecessary growth of Journal Database.
    I'd like not to switch off journaling for all users during mailbox move.
    best regards Janusz Such

    Hello Winnie,
    your understanding is not correct:
    I move mailboxes from first DATABASE which is journaled;
    second database is dedicated solely for Journal user's mailbox and is not touched now.
    Thank you for PS commands; I'll use them...
    best regards Janusz Such
    Hi Janusz,
    Sorry for my delay. In your original posting, "I saw that when I move mailbox from 2010 to 2013 then Journal Database INCREASES about size of MOVED MAILBOX !"
    My understanding is that when you move mailbox from Exchange 2010 Database 1 to Exchange 2013 database, the journal mailbox in Exchange 2010 Database 2 is incleased. Is it right?
    Generally, the mailbox move would not be journaled unless there is any new email bening sent to the mailbox during the migration. Please run the commands in my original posting to check the statistics about it, and refer to Ed Crowdly's suggestion to use
    Journal rule instead of database journal as a workaround.
    Regards,
    Winnie Liang
    TechNet Community Support

Maybe you are looking for