Our current environment consists of 6 total virtual servers each running Windows Server 2012 R2: 1 Main Poller running all the modules 1 Dedicated SQL server for the databases 1 Server for DPA 3 Servers running WPM Orion Platform - 2017.3.5 Volumes 1836 Nodes 813 SAM - 6.6.0 Components 1835 NPM - 12.2 Interfaces 1165 IPAM - 4.6.0 Used IPs 4123 WPM - 2.2.1 Transactions 26 Toolset - 11.0.6 Seats Taken 2 VMAN - 8.2.0 Used Sockets 92 SRM - 6.6.0 Disks 148 CloudMonitoring - 2.0.0 NetPath - 1.1.2 NTA - 4.2.3 DPAIM - 11.1.0 Obviously, we're behind just a tad so I've been tasked with the upgrade/migration/re-architecture of our Orion implementation. I plan to follow the instructions described in How to Migrate Orion to a New Server With Zero Downtime but was wondering if anyone had any thoughts on any glaring changes to our implementation that may need attention or if simply setting up new 2016 or 2019 servers and following the blog sufficient. Thanks in advance!

This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Upgrade & Migrate

blitzsonik over 5 years ago

Our current environment consists of 6 total virtual servers each running Windows Server 2012 R2:

1 Main Poller running all the modules

1 Dedicated SQL server for the databases

1 Server for DPA

3 Servers running WPM

Orion Platform - 2017.3.5	Volumes 1836 Nodes 813
SAM - 6.6.0	Components 1835
NPM - 12.2	Interfaces 1165
IPAM - 4.6.0	Used IPs 4123
WPM - 2.2.1	Transactions 26
Toolset - 11.0.6	Seats Taken 2
VMAN - 8.2.0	Used Sockets 92
SRM - 6.6.0	Disks 148
CloudMonitoring - 2.0.0
NetPath - 1.1.2
NTA - 4.2.3
DPAIM - 11.1.0

Obviously, we're behind just a tad so I've been tasked with the upgrade/migration/re-architecture of our Orion implementation. I plan to follow the instructions described in How to Migrate Orion to a New Server With Zero Downtime but was wondering if anyone had any thoughts on any glaring changes to our implementation that may need attention or if simply setting up new 2016 or 2019 servers and following the blog sufficient. Thanks in advance!

0 wluther over 5 years ago

blitzsonik Other than the zero downtime part, I rebuilt our environment at the start of 2018. We made the transition away from Server 2012, and built out all new Server 2016 servers. (All VMs, of course) Prior to rebuilding everything, I found some very helpful blog posts from KMSigma, showcasing how he automated/built his VMs. I used his methods for our new environment, and it has been running super smooth ever since.
Automating Orion Server Installs - Builds from Scratch
Automating Orion Server Installs - After the O/S
Automating Orion Server Installs - Final Prep
After a few adjustments to fit our setup, I was able to get everything configured, up, and running without any real issues. Now, I keep a few master images (IIS, SQL, and just a plain one) running, installing system updates as they come out. Whenever I need to spin up a new system, I just clone whichever type I need, and I have a near fully provisioned, and very optimized system up in a matter of minutes.
Let us know how it goes.
Thank you,
-Will
Cancel
Vote Up 0 Vote Down

Cancel