none
Migrating MIM between environments RRS feed

  • Question

  • Hi,

    We have a MIM Sync & Portal deployed and working in Production.

    We are deploying a new DEV & TEST environment, and would like to backup and restore the Production MIM into these new environments.

    Is this sufficient?

    • Backup FIMService and FIMSyncService databases in Prod
    • Deploy MIM base in DEV & TEST environments (same version of MIM as Prod)
    • Restore FIMService and FIMSyncService databases in DEV & TEST environments
    • Copy any custom PowerShell add-ins/modules, scripts
    • Copy contents of C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions across to DEV & TEST

    Anything else?

    Thank you.


    • Edited by Shim Kwan Thursday, October 18, 2018 10:13 PM
    Thursday, October 18, 2018 10:13 PM

Answers

  • Hi,

    In this case your plan could work, but i think you should restore the database before installing the MIM base and directly use the Prod Databases. durring th installation wizzard you will get the information to use the existing database. in addition you will get an warning that you need to install the patch version 4.x.yyy.z because the used database is already patched. In addition to use the existing database of the synchronization engine you need to export the sync encyption key. so the plan will be look like this:

    • Backup FIMService and FIMSyncService databases in Prod
    • Backup the FIMSyncEncryptionKey in Prod
    • Restore FIMService and FIMSyncService databases in DEV & TEST environments
    • Deploy MIM base in DEV & TEST environments (using the existing Databases)
    • Patch the MIM base to the same version as in Prod
    • Copy any custom PowerShell add-ins/modules, scripts
    • Copy contents of C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions across to DEV & TEST
    • If you have any Portal Customizations you also need to transport these files.

    I guess this should work.

    KR

    • Marked as answer by Shim Kwan Tuesday, October 23, 2018 8:23 PM
    Tuesday, October 23, 2018 5:00 AM

All replies

  • Hi,

    This sounds like a plan, but there are several stones on the way to success.

    Main Question: Is the DEV & TEST Environment in the same domain as the PROD?
    Based on this Answer the Migration Plan can be defined. Because the one of the Problems will be the SID change of all required Accounts.

    Additional Question: Would you like to clone the PROD with including the data or only creating an DEV & TEST with the same configuration as the PROD?

    With this Informations we could define the migration plan.

    KR

    Saturday, October 20, 2018 8:42 AM
  • Thanks Mario.

    The AD & HR environments will be cloned from Production too.

    So we'd like to bring in MIM config and data across to DEV & TEST.

    Once everything has been migrated, we'll sync up the identities between the different connected systems.

    Tuesday, October 23, 2018 3:06 AM
  • Hi,

    In this case your plan could work, but i think you should restore the database before installing the MIM base and directly use the Prod Databases. durring th installation wizzard you will get the information to use the existing database. in addition you will get an warning that you need to install the patch version 4.x.yyy.z because the used database is already patched. In addition to use the existing database of the synchronization engine you need to export the sync encyption key. so the plan will be look like this:

    • Backup FIMService and FIMSyncService databases in Prod
    • Backup the FIMSyncEncryptionKey in Prod
    • Restore FIMService and FIMSyncService databases in DEV & TEST environments
    • Deploy MIM base in DEV & TEST environments (using the existing Databases)
    • Patch the MIM base to the same version as in Prod
    • Copy any custom PowerShell add-ins/modules, scripts
    • Copy contents of C:\Program Files\Microsoft Forefront Identity Manager\2010\Synchronization Service\Extensions across to DEV & TEST
    • If you have any Portal Customizations you also need to transport these files.

    I guess this should work.

    KR

    • Marked as answer by Shim Kwan Tuesday, October 23, 2018 8:23 PM
    Tuesday, October 23, 2018 5:00 AM
  • thank you for all your help Mario, will let you know how it goes :)
    Tuesday, October 23, 2018 8:23 PM