· Microsoft Identity Integration Server 2003
· Microsoft Identity Integration Feature Pack
· Microsoft Identity Lifecycle Manager 2007 Feature Pack 1
· Microsoft Forefront Identity Manager 2010
a. Backup – Server Configuration
b. Backup – Backend SQL Server Database (Optional – pending the current SQL Server backup/maintenance plan)
b. Backup – Encryption Key
c. Backup – Source Code
d. Backup – Extensions and Data
e. Backup – Backend SQL Server Database
b. Backup – Source Code
c. Backup – Extensions
d. Backup – Backend SQL Server Database (Optional – pending the current SQL Server backup/maintenance plan)
1. Close the Identity Manager Console before beginning this process
a. *NOTE* This is very important, as if you have the Identity Manager Console up and running, or if you have scheduled jobs running when doing this step, you could run into errors, and possibly corrupt data.
2. Open Microsoft SQL Server Management Studio: (NOTE: We will use snapshots from SQL Server 2008 for the purpose of this document.)
a. Microsoft SQL Server 2000: Enterprise Manager
b. Microsoft SQL Server 2005: SQL Server Management Studio
c. Microsoft SQL Server 2008: SQL Server Management Studio
3. Connect to the Microsoft SQL Server housing the MicrosoftIdentityIntegrationServer (FIM2010: FIMSynchronizationService) database.
4. Expand Databases
5. Right click on the MicrosoftIdentityIntegrationServer (FIM2010: FIMSynchronizationService) database
6. Select Tasks > Back Up (*SQL 2000: Select All Tasks and then Back Up Database *)
a. Back Up Type: Full
b. Name: (Recommendation leave the default) MicrosoftIdentityIntegrationServer-Full Database Backup
i. NOTE: The name of this database should be something that you can remember and identify what it is for future reference.
c. Destination: Notice where it is currently backed up at, and change it if you have a specific location to back up the database.
d. Click Ok
7. If you experience problems with the backup process of the SQL Server database, you may need to contact our Microsoft SQL Server team for support.
Complete Database Backup
Restoring Complete database Backups:
SQL 2000 - SQL Server 2000 Backup and Restore
SQL 2005 - Backing Up and Restoring Databases in SQL Server
SQL 2008 - Backing Up and Restoring Databases in SQL Server
Database Maintenance: http://social.technet.microsoft.com/Forums/en-US/identitylifecyclemanager/thread/a109ea2d-a61a-483c-97c8-8a680ce77e2e/
1. Moving the database from a remote SQL Server to be a local SQL Server
2. Moving the database from a local SQL Server to remote SQL Server
3. Moving the database from a remote SQL Server to another remote SQL Server
6. Select Tasks and then Detach
a. Check Drop Connections
b. Check Update Statistics
c. Check Keep Text Full Catalogs
7. Move the MDF and LDF files from the location documented below to the new location
a. [Default Location for MIIS/IIFP/ILM] %programfiles%\Microsoft Identity Integration Server\Data folder
b. [Default Location for FIM] %programfiles%\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA
8. Open Microsoft SQL Server Management Studio: (NOTE: We will use snapshots from SQL Server 2008 for the purpose of this document.)
9. Connect to the Microsoft SQL Server that will host the MicrosoftIdentityIntegrationServer (FIM2010: FIMSynchronizationService) database.
10. Right click on databases and select Attach
11. Click the Add button
12. Point to the location where the MDF and LDF files are located
13. Click the Ok button
14. Click the Ok button and the database should be re-attached
15. If you changed to a new SQL Server, you will need to execute an uninstall and reinstall of the Microsoft Identity Management product that you are utilizing here.
o SourceCode: by default, GALSYNC and LOGGING source code is installed into this folder. You may have custom source code in this folder as well. If you have custom GALSYNC and/or EXTENSION source code in another location, navigate to that location and backup this information.
o Extensions: folder contains all DLL files for default and custom GALSYNC and/or EXTENSION code written.
o MaData: folder contains specific information for each of the Management Agents that you have created. It does not house Management Agent configurations by default.
o Data: by default, this is the location of the SQL Server MDF and LDF files. If you have followed the steps in “Backup the backend SQL Server Database” then you do not need to worry about these files. There may be other files in this folder as well, and you will want to back up this information as well.
This section is designed to assist you in backing up your server configurations. The server configurations consist of backing up all management agent configurations and metaverse configurations. Doing this step, exports all management agent configurations as XML files to a specific location. The process does not allow you to overwrite files, so you will need to have a new location for each back up.
1. Open the Microsoft Identity Synchronization Manager Console (MIIS/IIFP/ILM/FIM)
2. From the File menu select Export Server Configuration.
3. Select the folder to save the data
a. NOTE: It cannot be a folder that you have exported out to before, unless you go in and delete the data there first. Make a new folder if needed.
4. Click OK.
This section is designed to assist you in backing up the encryption key.
1. Click the Start button then All Programs then Microsoft Identity Integration Server.
2. Select Key Management Utility.
3. Select Export Key set and Click the Next button.
4. Enter the MIIS Service Account information.
NOTE: This is the service account used to install the Microsoft Identity Integration Server product.
5. Click the Next button.
6. Select the export location and file name.
7. Click the Next button.
8. Click the Finish button.
9. Click the Close button.
Backup and Restore the FIMService: FIM CM Backup and Restore Guide: ILM 2007 FP1 CLM Backup and Restore:
Carsten Siemens edited Revision 18. Comment: Added tag: en-US, has TOC, has See Also
Ed Price - MSFT edited Revision 9. Comment: TOC and white space issues
Ed Price MSFT edited Revision 7. Comment: Updated title to standards.