locked
SCOM 2007 R2 Database migration to 2012 R2 RRS feed

  • Question

  • Hi Experts,

    Greetings.

    We are planning to do a side by side migration from existing SCOM 2007 R2 to SCOM 2012 R2.

    Are there any well documented links for the same ?

    The major concern for us is using the all the data stored in the current databases(which is on 2008 R2 SQL) for SCOM 2012 as well.

    Best Regards,

    Prajul Nambiar

    Monday, January 5, 2015 11:47 AM

Answers

  • Hi,

    For side by side migration, we will add a new Operations Manager Management Group, and let agents be multihomed and then imported all the management packs, notifications, account and so on are added to the
    management group. Eventually the old management group can be removed.

    Please check links below for more information:

    Do I need a specific Cumulative Update Release (UR) in order to upgrade to SCOM 2012 or 2012 SP1 or 2012 R2?

    http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx

    http://www.systemcentercentral.com/scom-2012-rc-side-by-side-migration-phase-1-preparations/

    http://marthijnvanrheenen.wordpress.com/2012/03/05/scom-2012-side-by-side-installation-with-scom-2007-r2/

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Proposed as answer by Yan Li_ Wednesday, January 14, 2015 1:45 AM
    • Marked as answer by Yan Li_ Monday, January 19, 2015 7:04 AM
    Thursday, January 8, 2015 9:10 AM
    • High-level steps:
      • New hierarchy: Design the new environment with pre-requisites.
      • Deploy the new OpsMgr 2012 R2 environment.
      • Migrate Management Packs (Microsoft, third party and custom)
      • Migrate notifications
      • Migrate (recreate) user roles
      • Migrate cross-platform monitoring (if required)
      • Migrate integration with third party enterprise
      • Custom reports, schedules, etc.
      • Upgrade agents to OpsMgr 2012 R2 (dual-homing)
      • Decommission OpsMgr 2007 R2 agents
      • Retire the old OpsMgr 2007 R2 environment
    • Reasons for side-by-side migration
      • Minimizes impact in Production environment.
      • Phases the migration.
      • Minimizes down time of monitoring.
      • Coexistence period and staged migration.
      • Most overrides have been created will be able to be migrated to new environment.
      • Current OperationsManager database (2007) has configuration or performance deficiencies and we want to start with a clean environment applying learned lessons with the old environment.
      • Current OperationsManager database is too large to do an in-place upgrade. Take in account that we need 50% of free space of the database before an in-place upgrade.
      • SCOM 2007 R2 Management Group is configured with non-supported configurations such as old Operating System versions, old SQL Server versions, 32 bits, etc. In this scenario, upgrading in-place is more work than starting over with a new using side-by-side (multi-homed) migration.
      • Company wants to deploy System Center suite in a private cloud scenario.
      • More time to validate and test new infrastructure and 2012 R2 Management Group.
    • Limitations
      • Lab environment
      • New OpsMgr 2012 R2 environment
      • Manage both environments (production and the new one)
      • Management Packs (specially third party and custom MPs)
    • Migration Workflow
      • Upgrade OM2007 to (at least) OM2007 R2 CU6
      • Deploy OpsMgr2012 R2 environment
      • Review Custom Configuration in OM2007 (regkeys, directories, scheduled tasks… if required)
      • Management Packs (sequentially, one at a time)
        • Including process to clean up management packs and customizations (overrides)
      • Notifications
      • Run as accounts and run as profiles
      • User roles
      • Custom Reports
      • Subcriptions
      • Decommission OM2007
    • Recommended post-upgrade services
      • RAP as a service for OM2012


    Thanks, S K Agrawal

    • Marked as answer by Yan Li_ Monday, January 19, 2015 7:04 AM
    Wednesday, January 14, 2015 5:16 AM

All replies

  • Hi Parjul,

    find below links 

    http://scug.be/christopher/2012/10/23/upgrade-guide-from-scom-2007-to-scom-2012/

    http://jeroennotebaertsblog.blogspot.com/2012/01/upgrading-scom-2007-r2-to-scom-2012.html

    about Migrate using same SQL Server, Just make sure that use different Instance For Databases & Reporting.


    Regards, Ibrahim Hamdy

    Monday, January 5, 2015 12:20 PM
  • Hi,

    For side by side migration, we will add a new Operations Manager Management Group, and let agents be multihomed and then imported all the management packs, notifications, account and so on are added to the
    management group. Eventually the old management group can be removed.

    Please check links below for more information:

    Do I need a specific Cumulative Update Release (UR) in order to upgrade to SCOM 2012 or 2012 SP1 or 2012 R2?

    http://blogs.technet.com/b/kevinholman/archive/2014/01/20/do-i-need-a-specific-cumulative-update-release-ur-in-order-to-upgrade-to-scom-2012-or-2012-sp1-or-2012-r2.aspx

    http://www.systemcentercentral.com/scom-2012-rc-side-by-side-migration-phase-1-preparations/

    http://marthijnvanrheenen.wordpress.com/2012/03/05/scom-2012-side-by-side-installation-with-scom-2007-r2/

    Regards,

    Yan Li


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    • Proposed as answer by Yan Li_ Wednesday, January 14, 2015 1:45 AM
    • Marked as answer by Yan Li_ Monday, January 19, 2015 7:04 AM
    Thursday, January 8, 2015 9:10 AM
    • High-level steps:
      • New hierarchy: Design the new environment with pre-requisites.
      • Deploy the new OpsMgr 2012 R2 environment.
      • Migrate Management Packs (Microsoft, third party and custom)
      • Migrate notifications
      • Migrate (recreate) user roles
      • Migrate cross-platform monitoring (if required)
      • Migrate integration with third party enterprise
      • Custom reports, schedules, etc.
      • Upgrade agents to OpsMgr 2012 R2 (dual-homing)
      • Decommission OpsMgr 2007 R2 agents
      • Retire the old OpsMgr 2007 R2 environment
    • Reasons for side-by-side migration
      • Minimizes impact in Production environment.
      • Phases the migration.
      • Minimizes down time of monitoring.
      • Coexistence period and staged migration.
      • Most overrides have been created will be able to be migrated to new environment.
      • Current OperationsManager database (2007) has configuration or performance deficiencies and we want to start with a clean environment applying learned lessons with the old environment.
      • Current OperationsManager database is too large to do an in-place upgrade. Take in account that we need 50% of free space of the database before an in-place upgrade.
      • SCOM 2007 R2 Management Group is configured with non-supported configurations such as old Operating System versions, old SQL Server versions, 32 bits, etc. In this scenario, upgrading in-place is more work than starting over with a new using side-by-side (multi-homed) migration.
      • Company wants to deploy System Center suite in a private cloud scenario.
      • More time to validate and test new infrastructure and 2012 R2 Management Group.
    • Limitations
      • Lab environment
      • New OpsMgr 2012 R2 environment
      • Manage both environments (production and the new one)
      • Management Packs (specially third party and custom MPs)
    • Migration Workflow
      • Upgrade OM2007 to (at least) OM2007 R2 CU6
      • Deploy OpsMgr2012 R2 environment
      • Review Custom Configuration in OM2007 (regkeys, directories, scheduled tasks… if required)
      • Management Packs (sequentially, one at a time)
        • Including process to clean up management packs and customizations (overrides)
      • Notifications
      • Run as accounts and run as profiles
      • User roles
      • Custom Reports
      • Subcriptions
      • Decommission OM2007
    • Recommended post-upgrade services
      • RAP as a service for OM2012


    Thanks, S K Agrawal

    • Marked as answer by Yan Li_ Monday, January 19, 2015 7:04 AM
    Wednesday, January 14, 2015 5:16 AM