locked
Planning CRM 2011 high availability RRS feed

  • Question

  • Hi all.

    I'm planning a crm 2011 high availability installation.

    I would to implement:

    • 2 node NLB cluster to host a CRM full server installation
    • 2 node SQL active/passive cluster to host CRM databases

    I've read the implementation guide but i'm still unsure on some points:

    • Is better to implement a Windows 2008 R2 software NLB configuration or hardware NLB?
    • How to implement EmailRouter high availability?
    • Ho to implement Reporting high availability? Since reporting services is cluster aware, i think i need to implement NLB for reporting services too, but i need 2 dedicated node or can i use the same nodes where the crm roles are installed?

    Thanks in advance. 

     

     

    Tuesday, October 11, 2011 8:47 AM

Answers

  • One thing to be aware of here.

    If you install SQL reporting services on a separate server, that server will have to be licensed as if it is running a full version of SQL on it. Quite expensive.

    For the above requirements, I would do the following:

    • 2 Node NLB cluster to host CRM full server implementation
    • 2 Node SQL Active/Passive Cluster to host CRM databases, CRM email router in Active/Passive configuration, Reporting Services Databases plus Reporting Services and reporting extension.

    This would bypass the need to license the Front End CRM servers with a SQL license each.

    When it comes to accessing the Reporting services installation on the SQL server, you can access it via the SQL server virtual name http://sqlclustername/reports  . This will provide the failover to the second node in case of failure.

     

     
    • Marked as answer by Thesalex Friday, October 28, 2011 8:18 AM
    Monday, October 24, 2011 4:45 PM
  • No actually now I come to think about this a bit more, I am not sure. But the reporting services databases can be installed on an SQL cluster. Reporting Services can be installed on an NLB cluster as per this article: http://msdn.microsoft.com/en-us/library/bb630407.aspx

     

    • Marked as answer by Thesalex Thursday, October 13, 2011 1:11 PM
    Thursday, October 13, 2011 12:23 PM
    Moderator
  • Ok, for our deployments we use the same front end servers than the CRM ones for reporting services
    My blog : http://mscrmtools.blogspot.com

    All my tools for Dynamics CRM 4.0 on my dedicated site: MSCRMTools Repository

    • Marked as answer by Thesalex Thursday, October 13, 2011 1:11 PM
    Thursday, October 13, 2011 12:24 PM
    Moderator

All replies

  • You can install the E-mail Router in a cluster.

    You can install reporting services in the same cluster as your SQL cluster or a separate cluster.

    Wednesday, October 12, 2011 4:35 PM
    Moderator
  • Thank you for the support.

    If i install email router service in the same cluster of SQL, may cause some issue? 

     

     

    Thursday, October 13, 2011 8:29 AM
  • Feridun,

    Are you sure about installing reporting services on a active/passive SQL cluster?


    My blog : http://mscrmtools.blogspot.com

    All my tools for Dynamics CRM 4.0 on my dedicated site: MSCRMTools Repository

    Thursday, October 13, 2011 12:01 PM
    Moderator
  • Based on this article: http://msdn.microsoft.com/en-us/library/bb630402.aspx

    install reporting services on a SQL active/passive cluster is supported, but only in one node (i think the active node),  but in this case if a failover occurs, the reporting service is unavailable.

    For reporting services redundancy, a NLB configuration is required. http://msdn.microsoft.com/en-us/library/bb630407.aspx (2 more SQL Entrerprise license)

    But in this case, if I have a 2 node NLB cluster for reporting services, the CRM reporting extension must be installed on each node? I think yes.

    And... if I dont' have an high load on reports and only "high availabilty" requirements, can I install reporting services on the same 2 node NLB cluster where CRM server is installed? I think yes.

    Thanks

     

    Thursday, October 13, 2011 12:21 PM
  • No actually now I come to think about this a bit more, I am not sure. But the reporting services databases can be installed on an SQL cluster. Reporting Services can be installed on an NLB cluster as per this article: http://msdn.microsoft.com/en-us/library/bb630407.aspx

     

    • Marked as answer by Thesalex Thursday, October 13, 2011 1:11 PM
    Thursday, October 13, 2011 12:23 PM
    Moderator
  • Ok, for our deployments we use the same front end servers than the CRM ones for reporting services
    My blog : http://mscrmtools.blogspot.com

    All my tools for Dynamics CRM 4.0 on my dedicated site: MSCRMTools Repository

    • Marked as answer by Thesalex Thursday, October 13, 2011 1:11 PM
    Thursday, October 13, 2011 12:24 PM
    Moderator
  • Ok, thanks you guys for the support.

    Just to recap:

    I small installation with not heavy load but with "high availability" requirements:

    • 2 node NLB cluster to host a CRM full server installation + Reporting Services + Reporting Extension
    • 2 node SQL active/passive cluster to host CRM databases, Report Databases + CRM Email Router

    Tell me if I am on the wrong way.

    Thanks again.

    Thursday, October 13, 2011 1:11 PM
  • Looks good to me.

     

    Thursday, October 13, 2011 4:05 PM
    Moderator
  • One thing to be aware of here.

    If you install SQL reporting services on a separate server, that server will have to be licensed as if it is running a full version of SQL on it. Quite expensive.

    For the above requirements, I would do the following:

    • 2 Node NLB cluster to host CRM full server implementation
    • 2 Node SQL Active/Passive Cluster to host CRM databases, CRM email router in Active/Passive configuration, Reporting Services Databases plus Reporting Services and reporting extension.

    This would bypass the need to license the Front End CRM servers with a SQL license each.

    When it comes to accessing the Reporting services installation on the SQL server, you can access it via the SQL server virtual name http://sqlclustername/reports  . This will provide the failover to the second node in case of failure.

     

     
    • Marked as answer by Thesalex Friday, October 28, 2011 8:18 AM
    Monday, October 24, 2011 4:45 PM
  • Thank you wildstyle.

     

    I think your suggested configuration is the best.

     

     

     

     

     

     

    Friday, October 28, 2011 8:23 AM