Restoring Microsoft Identity Integration Server 2003

If a server running Microsoft Identity Integration Server 2003, SQL Server 2000, or Windows Server 2003, Enterprise Edition stops responding and becomes inoperable, you can restore your metadirectory to the state of your most recent backup. It is strongly recommended that you test your restore procedure before an emergency occurs.

To restore your metadirectory, you need some or all of the following:

• Windows Server 2003, Enterprise Edition installation CD with a valid Product Identification Number.
• SQL Server 2000 installation CD with a valid Product Identification Number.
• Microsoft Identity Integration Server 2003 installation CD with a valid Product Identification Number.
• A backup copy of your Windows Server 2003, Enterprise Edition local Security Accounts Manager (SAM) database.
• A backup copy of the MicrosoftIdentityIntegrationServer database, which is stored in SQL Server 2000.
• A backup copy of your MIIS 2003 encryption keys.
• A backup copy of the source files for your rules extensions.
• A backup copy of any MIIS 2003 log files or file-based management agent import and export files that are located in InstallationDirectory\Madata.

To restore the metadirectory

1. If needed, install a fresh copy of Windows Server 2003, Enterprise Edition.
2. • The server must be installed in the same role as the previous installation, either as a stand-alone server or as a member of an Active Directory domain. If the server is a stand-alone server, use the Windows Server 2003, Enterprise Edition Backup tool to restore the local SAM database.
   • The server can have the same name or a different name as the previous installation.
3. If needed, install SQL Server 2000 with the same options as the previous installation.
4. Install MIIS 2003 on your server with the same options as the previous installation. If you are prompted during Setup, insert a floppy disk that contains your MIIS 2003 encryption key.
5. In SQL Server 2000, restore the MicrosoftIdentityIntegrationServer database.
6. In Windows Server 2003, Enterprise Edition, use Backup to restore any MIIS 2003 log files or file-based management agent import and export files located in InstallationDirectory\Madata.
7. If password synchronization was previously enabled, there may be password changes remaining in the queue. You should clear the queue before enabling password synchronization again on the restored server. For more information about clearing the password queue, see Microsoft Identity Integration Server 2003 Developer Reference.
8. After performing the above steps, run a Full Synchronization to bring your metaverse up to date.

Notes

• For more information about restoring the MicrosoftIdentityIntegrationServer database, see the Microsoft Identity Integration Server 2003 Technical Library on the Microsoft Web site(http://www.microsoft.com/) or SQL Server 2000 Books Online.
• For more information about Windows Server 2003, Enterprise Edition Backup, see Help and Support Center in Windows Server 2003, Enterprise Edition.