SQL Server failure recovery with Dynamics 365 Customer Engagement (on-premises)
If the computer that is running SQL Server fails, you must restore the databases from backup, and then reassociate them with the Dynamics 365 Customer Engagement (on-premises) deployment.
Install Microsoft Windows Server and make sure that the computer is in the same domain as the Dynamics 365 Server or Dynamics 365 Server roles. In addition, you should use the same database name and disk structure. If you change either of these, you must take additional steps to correctly restore the SQL Server databases.
Install SQL Server. For supported versions, see SQL Server editions.
If you have a valid backup of the master database, restore that backup. For more information, see MSDN: Back Up and Restore of System Databases in SQL Server Books Online.
Restore the msdb database. For more information, see MSDN: Back Up and Restore of System Databases in SQL Server Books Online.
Restore the MSCRM_CONFIG and OrganizationName_MSCRM databases. For more information about how to restore SQL Server databases, see MSDN: Back Up and Restore of SQL Server Databases.
If SQL Server Reporting Services and the Microsoft Dynamics 365 Reporting Extensions are also installed on the instance of SQL Server, restore the ReportServer and ReportServertempDB databases. For more information about how to restore databases, see MSDN: Backup and Restore of SQL Server Databases.
If you restored the MSCRM_CONFIG database, you must run Microsoft Dynamics 365 Server Setup and use the Connect to existing databases option on the Specify Deployment Options page. If you didn’t restore the MSCRM_CONFIG database and the database is functioning correctly, you can reconnect the organization database to the system. To do this, run the
Disable-CrmOrganizationandEdit-CrmOrganizationWindows PowerShell commands. More information:Administer the deployment using Windows PowerShell. Alternatively, in Deployment Manager right-click the organization and select Disable, right-click the organization again, select Edit Organization, and then change the SQL Server value in the wizard. For more information about how to edit an organization, see Edit an organizations attributes..
This scenario is a worst-case situation, that is, a total failure of the computer that is running SQL Server. In other circumstances, such as the failure of a disk, you may only have to restore a single database to recover the environment.