locked
Side-by-side migration SCOM 2012R2 to SCOM 1801 RRS feed

  • Question

  • Hi,

    We currently have scom 2012r2 and we are planning to migrate to version 1801 the current environment is as below:

    3 Servers

    1.Management Server installed on 2008 R2 OS.

    2.Reporting Service installed on 2012R2

    3.ACS server.

    so what's the best practice to start the migration and how to retain the old data warehouse database with new server 

    Thanks,


    IT Helpdesk

    Tuesday, May 14, 2019 11:12 PM

Answers

  • Hi,

    A side by side migration is basically setting up a new SCOM env from scratch and then adding your custom settings from the old env. 

    Since this is a new env, it's useless even if we have a copy of the data warehouse. If we'd like to keep the data warehouse data, we may consider the in-place upgrading.

    The general side by side migration procedure is like below:

    1, prepare the sheet the collect all the information of the current environment (agents, MPs, integration etc)
    2, after the sizing, prepare the new environment. (DB/Reporting, MS, ACS)
    3, import the fresh (sealed) MPs from the catalog
    4, install the agents from OM1801 console according to requirements (application wise or as needed)
    5, export the custom (unsealed) MPs (contains overrides, groups, etc.) from OM12R2 and import into OM1801
    6, import/export the DA's (if there is any)
    7, checking the third party compatibility with OM1801 and if yes then import it with overrides or import the new one from vendor and recreate the overrides by watching the OM12R2
    8, after verifying everything is working fine, uninstall the agents from OM12R2 console.
    9, uninstallation of OM12R2 and decommission of servers and DB's

    The general in-place upgrade procedure is like below:
    1, backup the servers
    2, Pre-Upgrade Tasks, such as database preparation, remove agents, disable notification subscriptions, stop the services, etc.
    3, upgrade the servers from the installation media
    4, upgrade the agents

    In addition, SCOM2019 is released, with new features, such as enhanced criteria builder with regular expression when creating subscriptions, improvement in agent initiated maintenance mode, new Linux OS support, and so on. It is recommended to migrate/upgrade to SCOM2019.

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, May 15, 2019 2:16 AM
  • Hi,

    I would recommend upgrading to a Long-Term Servicing Channel (LTSC) release instead, i.e. SCOM 2016 / SCOM 2019. Because there will be no more Semi-Annual Channel (SAC) releases, SCOM 1801 and SCOM 1807 are both SAC releases.

    Also the support for SCOM 1801 ends on August 8, 2019.

    In the picture below you will see the supported upgrade paths:

    Best regards,

    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 15, 2019 6:00 AM

All replies

  • Hi,

    A side by side migration is basically setting up a new SCOM env from scratch and then adding your custom settings from the old env. 

    Since this is a new env, it's useless even if we have a copy of the data warehouse. If we'd like to keep the data warehouse data, we may consider the in-place upgrading.

    The general side by side migration procedure is like below:

    1, prepare the sheet the collect all the information of the current environment (agents, MPs, integration etc)
    2, after the sizing, prepare the new environment. (DB/Reporting, MS, ACS)
    3, import the fresh (sealed) MPs from the catalog
    4, install the agents from OM1801 console according to requirements (application wise or as needed)
    5, export the custom (unsealed) MPs (contains overrides, groups, etc.) from OM12R2 and import into OM1801
    6, import/export the DA's (if there is any)
    7, checking the third party compatibility with OM1801 and if yes then import it with overrides or import the new one from vendor and recreate the overrides by watching the OM12R2
    8, after verifying everything is working fine, uninstall the agents from OM12R2 console.
    9, uninstallation of OM12R2 and decommission of servers and DB's

    The general in-place upgrade procedure is like below:
    1, backup the servers
    2, Pre-Upgrade Tasks, such as database preparation, remove agents, disable notification subscriptions, stop the services, etc.
    3, upgrade the servers from the installation media
    4, upgrade the agents

    In addition, SCOM2019 is released, with new features, such as enhanced criteria builder with regular expression when creating subscriptions, improvement in agent initiated maintenance mode, new Linux OS support, and so on. It is recommended to migrate/upgrade to SCOM2019.

    Hope the above information helps.

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, May 15, 2019 2:16 AM
  • Hi,

    I would recommend upgrading to a Long-Term Servicing Channel (LTSC) release instead, i.e. SCOM 2016 / SCOM 2019. Because there will be no more Semi-Annual Channel (SAC) releases, SCOM 1801 and SCOM 1807 are both SAC releases.

    Also the support for SCOM 1801 ends on August 8, 2019.

    In the picture below you will see the supported upgrade paths:

    Best regards,

    Leon


    Blog: https://thesystemcenterblog.com LinkedIn:

    Wednesday, May 15, 2019 6:00 AM
  • Hi,

    May we know the current status of the problem? Is there any other assistance we can provide?

    Regards,

    Alex Zhu
    -----------------------------------------------
    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Friday, May 17, 2019 2:58 AM