none
How to split multi-role server?

    Întrebare

  • Hello,

     I have 2 Exchange servers, both hosting the CAS, HT, and MB roles. Both servers are members of a DAG for database failover. All outlook clients are currently connected to Server1.

    Current Setup :-

    MX1 - CAS, HT and MB
    MX2 - CAS, HT and MB

    with DAG group

    I want to configure client Access Array by using virtualization so that the server can failover automatically.

    New setup :-

    VM1 - CAS, HT
    VM2 - CAS, HT
    MX1 - MB1
    MX2 - MB2

    How can I do it? Is there are guide to do it?

    Please help. Thanks!


    12 martie 2012 10:59

Răspunsuri

    1. No particular guide, install the 2 new servers (CAS), you may want to create an CAS Array if you haven't done so already, then configure any settings that you need, (OWA/OA/Autodiscover/Load Cert etc...)
    2. Then remove the CAS role off the existing server by running setup or going to control panel & changing the Exchange install.

    Sukh

    12 martie 2012 11:35
  • In addition to the comment from Sukh. You may need to modify the receive connectors on the HUB also if you will install them on a another server. This since the config for a receive connector is stored per server. Also don't forget to modify your send connector on organization level so it accepts messages from the new HUB.

    Regards,

    Johan


    Exchange-blog: www.johanveldhuis.nl

    12 martie 2012 12:58
  • Try the link that Frank posted yesterday to Henrik's most excellent site

    http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html 

    And you will need to look at load balancing.....

    While Windows NLB is supported, the product team's current recommendation is to use a hardware based load balancer (this can also be an appliance running as a VM) as it is service aware, supports multiple persistence options and can give you some additional reporting detail. 

    It also reduces some of the complexity  of doing Windows NLB on a VM.  You don't mention what hypervisor you are using, but ensure that you follow all the requirements for the platform in question if you do decide to do Windows NLB. 

    List of LBs that have gone through the validation programme:

    http://technet.microsoft.com/en-us/exchange/gg176682 


    Cheers, Rhoderick

    12 martie 2012 13:13
  • A little addition, just make sure that you size the VM's well even if they are VM's

    Size them as there were physical machines

    Around the LB, follow the link Rhoderick posted for supported load balancers and follow the deployment guide from the vendors and you will be fine, verify it so it works the way you want it to regarding affinity/sticky/timeout and so on

    Check the hardware section for sizing

    http://technet.microsoft.com/en-us/library/aa996719.aspx

    http://technet.microsoft.com/en-us/library/dd346700.aspx



    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

    12 martie 2012 21:35

Toate mesajele

    1. No particular guide, install the 2 new servers (CAS), you may want to create an CAS Array if you haven't done so already, then configure any settings that you need, (OWA/OA/Autodiscover/Load Cert etc...)
    2. Then remove the CAS role off the existing server by running setup or going to control panel & changing the Exchange install.

    Sukh

    12 martie 2012 11:35
  • In addition to the comment from Sukh. You may need to modify the receive connectors on the HUB also if you will install them on a another server. This since the config for a receive connector is stored per server. Also don't forget to modify your send connector on organization level so it accepts messages from the new HUB.

    Regards,

    Johan


    Exchange-blog: www.johanveldhuis.nl

    12 martie 2012 12:58
  • Try the link that Frank posted yesterday to Henrik's most excellent site

    http://www.msexchange.org/articles_tutorials/exchange-server-2010/management-administration/planning-deploying-testing-exchange-2010-site-resilient-solution-sized-medium-organization-part1.html 

    And you will need to look at load balancing.....

    While Windows NLB is supported, the product team's current recommendation is to use a hardware based load balancer (this can also be an appliance running as a VM) as it is service aware, supports multiple persistence options and can give you some additional reporting detail. 

    It also reduces some of the complexity  of doing Windows NLB on a VM.  You don't mention what hypervisor you are using, but ensure that you follow all the requirements for the platform in question if you do decide to do Windows NLB. 

    List of LBs that have gone through the validation programme:

    http://technet.microsoft.com/en-us/exchange/gg176682 


    Cheers, Rhoderick

    12 martie 2012 13:13
  • A little addition, just make sure that you size the VM's well even if they are VM's

    Size them as there were physical machines

    Around the LB, follow the link Rhoderick posted for supported load balancers and follow the deployment guide from the vendors and you will be fine, verify it so it works the way you want it to regarding affinity/sticky/timeout and so on

    Check the hardware section for sizing

    http://technet.microsoft.com/en-us/library/aa996719.aspx

    http://technet.microsoft.com/en-us/library/dd346700.aspx



    Jonas Andersson | Microsoft Community Contributor Award 2011 | MCITP: EMA 2007/2010 | Blog: http://www.testlabs.se/blog | Follow me on twitter: jonand82

    12 martie 2012 21:35