Share via

FIM 2010: How to migrate FIM backend database to new SQL Server

  • Article

Purpose

The purpose of this document is to guide you through the steps to migrate the backend database from one SQL Server to a new SQL Server.  

 

Overview

The Synchronization Manager does not contain any easy way of referencing a new location for the backend SQL Server database.  You will need to uninstall and reinstall the Synchronization Manager in order to reference the new SQL Server.  This document will help cover those steps necessary to accomplish this task. 

Here is an outline of what your migration process should / might look like when migrating the database to a new SQL Server.

  1. Backup Information
  2. Move to new SQL Server
  3. Uninstall / Reinstall of the Synchronization Manager 

 

Backup Information

Any time you execute a major move like moving the backend database to a new SQL Server, you want to ensure that you have all of your data backed up to ensure that if something were to go wrong, that you could get back up and running as soon as possible.

Below you will find the recommended information to backup prior to executing the migration of the backend database to a new SQL Server.

 Backup type  Description

Encryption Key Backup

This is very crucial.  If the MicrosoftIdentityIntegrationServer Database exists in the backend SQL Server database, the installation of the Synchronization Manager will prompt you to see if you want to use an existing database.  If you decide to use the existing database, then you will be required to provide the Encryption Key Bin file.  You already have a copy of the file.  However, it is just a good idea to get a clean backup before the process to migrate the database to a new SQL Server.

 

Server Configuration Backup

Not absolutely necessary.  Simply a good idea to keep a good backup of the server configuration for disaster recovery purposes.

Extensions Folder Backup

Not absolutely necessary.  Simply a good idea to keep a good backup of the server configuration for disaster recovery purposes.

Clear the Run History

Not absolutely necessary.  However, the size of your run history can hinder the performance of your installation.  It is recommended to clear it out, or at-least take it to a minimum required by your company.

You can clear the Run History through the following steps

  1. Open the Synchronization Manager
  2. Select Operations
  3. From the Actions menu, select Clear Runs
  4. Choose the option that best suits your business requirements and click Ok.

Backup SQL Server Database

It is always good to keep a fresh backup of the SQL Server Database.  In this scenario though, we will be using the backup to move it to the new SQL Server.

 

Move to new SQL server

There are many ways to move the backend database to a new SQL Server.  The best option is to back up the SQL Server database, and then restore the database in the new location.

  1. Copy the backup of the SQL Server Database – MicrosoftIdentityIntegrationServer to the new SQL Server
  2. Restore the SQL Server Database 

 

Uninstall/Reinstall of FIM Sync

  1. Control Panel > Programs and Features (Add / Remove Programs if Windows Server 2003)
  2. Locate and Select the Synchronization Manager
    1. MIIS, IIFP, and ILM: Microsoft Identity Integration Server
    2. FIM: Forefront Identity Manager Synchronization Service
  3. Click Uninstall (Change / Remove if Windows Server 2003)
  4. Once the product has been fully removed, then you can execute the installation of the product
  5. Remember to point to the new SQL Server Database when prompted for the SQL Server Database location.
    1. Remember, you will need the Encryption Key. 

 

See also