Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Microsoft Dynamics CRM...
Microsoft Dynamics CRM (Archived)

Microsoft Dynamics CRM 2015 - Disaster Recovery

(0) ShareShare
ReportReport
Posted on by Community Member Microsoft Employee

Hi Sirs / Madam,

Good day!

We're currently running a Microsoft Dynamics CRM 2015 and planning to have a new server for its Disaster Recovery.

Just want to ask some help on how and what's the better way to do it? 

1. Clone the existing server & application or Fresh installed CRM Dynamics 2015?

2. What are the configurations or settings that we should check if we will create a new server and restoring CRM application?

3. Is there any link or manual that we can follow to successfully do the activity?

Thanks so much in advance. :)

*This post is locked for comments

  • Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Microsoft Dynamics CRM 2015 - Disaster Recovery

    Hi,

    Regarding your other question, the link below provides you with instructions on how the configure CRM on multiple computers and enable Network Load Balancing. This is less of a CRM configuration/installation issue, and a little more of a windows/IT administration issue. I would get support from your IT team on how to get this installed.

    technet.microsoft.com/.../hh699803.aspx

    Hope this helps.

  • Suggested answer
    Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Microsoft Dynamics CRM 2015 - Disaster Recovery

    Hi,

    A SQL Server failover cluster instance always appears on the network as if it were a single computer. You must use the SQL Server failover cluster instance name to connect to the SQL Server failover cluster, not the machine name of the node it happens to be running on. Doing so ensures that you are always able to connect to the failover cluster instance using the same name, regardless of which node is running SQL Server.

    The name of your failover cluster instance must be unique to your domain. SQL Server does not listen on the IP address of the local servers. Instead, SQL Server listens only on the virtual IP address created during installation of the SQL Server failover cluster instance.

    SQL Server depends on distinct registry keys and service names within the failover cluster to ensure that SQL Server functionality continues after a failover. Therefore, the name you provide for the instance of SQL Server, including the default instance, must be unique across all nodes in the failover cluster. Using unique instance names ensures that instances of SQL Server that are configured to fail over to a single server have distinct registry keys and service names.

    msdn.microsoft.com/.../ms179410(v=sql.105).aspx

    What this means is that once your cluster is set up, you configure CRM Deployment manager to point to the cluster and not to the individual SQL Server instance.

    Hope this helps.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Microsoft Dynamics CRM 2015 - Disaster Recovery

    I am trying to reconfigure the replicated CRM server  for DR purpose and wasnt able to configure the deployment manager due to MMC snapin error.

    May we just also confirm if the following are correct in order to run the crm app on dr server?

    1. point the db path to replicated database

    2. update the hostname on IIS

    3. re import organization on deployment manager

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Microsoft Dynamics CRM 2015 - Disaster Recovery

    Hi Sir Aric,

    Thank you so much for your response and it is a great help for us.

    May i also with your if you had also a link in rebuilding a new CRM application which is MS Dynamics 2015? or maybe a config once we replicate the application on another VM Server? Thanks again, Sir! :))

  • Suggested answer
    Aric Levin Profile Picture
    Aric Levin 30,188 on at
    RE: Microsoft Dynamics CRM 2015 - Disaster Recovery

    Hi,

    Since the CRM Server can be easily rebuilt, I would focus my disaster recovery on the SQL Server.

    Take a look at the following documentation from MS regarding Disaster Recovery in SQL Server.

    docs.microsoft.com/.../sql-server-business-continuity-dr

    Regarding the CRM Server, you should consider using Load Balancing to replicate the server. Take a look at the following article for additional information regarding this:

    us.hitachi-solutions.com/.../disaster-recovery-strategies-for-microsoft-dynamics-crm

    Hope this helps.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,235 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans