Backing up Forefront Identity Manager 2010 R2

Regular backup procedures are essential for protecting your data from accidental loss. Critical data for Microsoft® Forefront Identity Manager (FIM) 2010 R2 is stored on the server running FIM that hosts FIM and on the server running SQL Server 2008 hosts the FIM Synchronization Service database. These might be installed on the same server. It is strongly recommended that you test your backup and restore procedures before an emergency occurs.

To back up FIM

1. Back up the FIM encryption key. For more information, see Back up the Forefront Identity Manager 2010 R2 Encryption Key.

   Warning

   All passwords related to FIM data are accessed by using the encryption keys. Although you can restore an FIM installation without the current encryption keys, or with no encryption keys, you might lose the following data:

   • All passwords that are used by management agents to authenticate to connected data sources. These can be reentered manually.

   • All passwords for user objects that were in the process of being provisioned. You can view a list of these user objects by searching the connector space with a scope of Pending Export/Add. You can then disconnect and reprovision these user objects or continue to export them and set the passwords manually.

2. In SQL Server, back up the FIM Synchronization Service database.

3. In Windows Server® 2008 operating system, use Backup to back up any log files or file-based management agent import and export files that are located in InstallationDirectory\Madata.

4. If the server is a stand-alone server, use Windows Server® 2008 operating system Backup to back up the local Security Accounts Manager (SAM) database.

• Windows Server® 2008 operating system installation CD with a valid Product Identification Number.

• SQL Server installation CD with a valid Product Identification Number.

• FIM installation CD with a valid Product Identification Number.

• A backup copy of your Windows Server® 2008 operating system local Security Accounts Manager (SAM) database.

• A backup copy of the FIM Synchronization Service database, which is stored in SQL Server.

• A backup copy of your FIM encryption keys.

• A backup copy of the source files for your rules extensions.

• A backup copy of any FIM log files or file-based management agent import and export files that are located in InstallationDirectory\Madata.