none
How to Remove a bad mailbox server and add new mailbox server to DAG and copy mailboxes over RRS feed

  • Question

  • DAG
    2- cas - VM
    2- mbx- physical blade  (mbx1, mbx2)
    5- mailbox databases
    OS: Win 2008 SP2
    Exchange 2010SP3
    Storage: Tegile Disk jbod  Luns

    We have bad disks on mbx1.  our plan is to get a new blade to replace the bad one named mbx3. we need to do this asap since we are running on 1 server without failover capability

    How can I safely:
    1. Add a new mailbox server to the DAG
    2. Copy\Move the databases from the old (passive) server to the new server
    3. Remove the bad mailbox server from DAG

    Wednesday, February 19, 2014 10:47 PM

Answers

  • You'll want to make sure that the new server is on all the same networks that the server you are removing is on, specifically networks that are DAG networks. Also, you'll want to avoid using Windows Network Load Balancing on the new mailbox server since it will be part of the DAG. Also, just as you did with the current DAG members, ensure that the disk drive letters match the existing disks that hold databases & logs. Other than that, it's as simple as you have stated.

    1.) Once you have the new mbx server built & configured with the mailbox role, you can use:

    Get-DatabaseAvailabilityGroup "Name of DAG" | Add-DatabaseAvailabilityGroupServer "Name of New MBX Server"

    2.) Add the databases to the new DAG member:

    Add-MailboxDatabaseCopy "name of database" -MailboxServer "name of new DAG member" -ActivationPreference "[you decide based on the server replacing mbx1]"

    3.) Once your databases are Mounted and/or Healthy on the new DAG member, you'll want to remove the databases from the "bad" server (make sure they are all passive on the server first):

    Get-MailboxDatabaseCopy "SERVER\Database" | Remove-MailboxDatabaseCopy

    4.) Once all of the databases are removed from the "bad" DAG member, remove him from the DAG:

    Get-DatabaseAvailabilityGroup "Name of DAG" | Remove-DatabaseAvailabilityGroupServer "Name of old MBX Server"

    Before you pull the blade, uninstall Exchange Server gracefully, as this will save you AD & Exchange headaches later on.

    Petri has a pretty good GUI walk-through for some of the above steps here:

    How to Configure Database Availability Group for Exchange Server 2010

     

    Woody Colling, MCITP Exchange 2010
    --The incentive for the experts to answer posts is to get their replies marked as helpful, or as the answer to our questions, help them help us, mark posts accordingly--

    • Marked as answer by leo_430 Monday, February 24, 2014 8:43 PM
    Monday, February 24, 2014 1:50 AM

All replies

  • You'll want to make sure that the new server is on all the same networks that the server you are removing is on, specifically networks that are DAG networks. Also, you'll want to avoid using Windows Network Load Balancing on the new mailbox server since it will be part of the DAG. Also, just as you did with the current DAG members, ensure that the disk drive letters match the existing disks that hold databases & logs. Other than that, it's as simple as you have stated.

    1.) Once you have the new mbx server built & configured with the mailbox role, you can use:

    Get-DatabaseAvailabilityGroup "Name of DAG" | Add-DatabaseAvailabilityGroupServer "Name of New MBX Server"

    2.) Add the databases to the new DAG member:

    Add-MailboxDatabaseCopy "name of database" -MailboxServer "name of new DAG member" -ActivationPreference "[you decide based on the server replacing mbx1]"

    3.) Once your databases are Mounted and/or Healthy on the new DAG member, you'll want to remove the databases from the "bad" server (make sure they are all passive on the server first):

    Get-MailboxDatabaseCopy "SERVER\Database" | Remove-MailboxDatabaseCopy

    4.) Once all of the databases are removed from the "bad" DAG member, remove him from the DAG:

    Get-DatabaseAvailabilityGroup "Name of DAG" | Remove-DatabaseAvailabilityGroupServer "Name of old MBX Server"

    Before you pull the blade, uninstall Exchange Server gracefully, as this will save you AD & Exchange headaches later on.

    Petri has a pretty good GUI walk-through for some of the above steps here:

    How to Configure Database Availability Group for Exchange Server 2010

     

    Woody Colling, MCITP Exchange 2010
    --The incentive for the experts to answer posts is to get their replies marked as helpful, or as the answer to our questions, help them help us, mark posts accordingly--

    • Marked as answer by leo_430 Monday, February 24, 2014 8:43 PM
    Monday, February 24, 2014 1:50 AM
  • Thank you very much for this information!  Install and removal went smoothly.

    Monday, February 24, 2014 8:48 PM