question

notmyname-5434 avatar image
0 Votes"
notmyname-5434 asked CyrAz answered

scom 2016 migration to 2019 on new server with remote database

hi,
our existing scom 2016 environment is distributed and has all of the databases located on a remote sql server (sql 2016 sp2). we'd like to upgrade scom to 2019, but we don't want to continue running the scom servers on the old server os (2012R2). i understand i can upgrade the 2012 R2 windows os in place, but I was wondering if it's possible to just deploy a new server with server 2019, install scom 2019 and join it to the management group and then remove the scom 2016 servers on the 2012 R2 os's from the management group? i'm having trouble searching the internet for that scenario.
thanks!

msc-operations-manager
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LeonLaude avatar image
1 Vote"
LeonLaude answered Crystal-MSFT commented

Hi @notmyname-5434,

SCOM 2016 can coexist with SCOM 2019 (see Supported coexistence), so it is possible to install a SCOM 2019 environment on the side, then you can make your SCOM 2016 agents report to your SCOM 2019 management group, and slowly perform a side-by-side migration.


If the reply was helpful please don't forget to upvote and/or accept as answer, thank you!


Best regards,
Leon

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ok. i think i understand. with the side-by-side migration i'll have to create new databases correct? meaning i lose whatever's in the old databases. also, am i making a new management group as well?

0 Votes 0 ·

With side-by-side migration you install a new database & management group on the side yes.

0 Votes 0 ·

i don't love the idea of new databases. we don't want to lose historical data. what about this as a scenario:
1. we deploy 2 new management servers on windows server 2019
2. we install scom 2016 and join them to the existing management group
3. migrate the roles like web server to the new management servers
4. decommission the old management servers on 2008 R2
5. upgrade scom 2016 to 2019 on the new servers with server 2019.

that way we don't have to create new databases or management groups or do any other side by side migration. like an in place upgrade with extra steps.



0 Votes 0 ·
Show more comments
Crystal-MSFT avatar image
0 Votes"
Crystal-MSFT answered

@notmyname-5434, Agree with Leon, For SCOM 2019, we can install it on Windows server 2019. And SCOM 2016 with the latest update rollup can coexist with SCOM 2019. Here is a link for the reference:
https://docs.microsoft.com/en-us/system-center/scom/system-requirements?view=sc-om-2019#software-requirements-for-operations-manager-components

Before the side-by-side migration, we need to verify something like if the SQL version and service pack levels are supported for both SCOM 2016 and SCOM 2019, if all AGENT managed Operating Systems are supported for SCOM 2019. if all MANAGEMENT PACKS in use are supported for SCOM 2019. here a blog from Kevin for the reference:
https://kevinholman.com/2021/01/13/upgrade-from-scom-2016-to-scom-2019-checklist/
Note: Non-Microsoft link, just for the reference.

We can plan a side by side migration with the steps which Leon mentioned:
https://social.technet.microsoft.com/Forums/en-US/b5fbc511-28b6-4d2e-9bcb-f760113029e4/scom-upgrade-side-by-side?forum=operationsmanagergeneral

Hope it can help.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

CyrAz avatar image
1 Vote"
CyrAz answered

If you want to stick to an in-place upgrade, what you could do is :
- Install a new server with windows 2019 and SCOM 2016 and join it to the current management group
- Upgrade it to SCOM 2019
- Decommission the old server


5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.