In Place Os upgrade from 2008 R2 to 2012 R2 in Additional Web Server

Hi,

I am running the environment with 2008 O/S in Main Poller and in some Addition Poller, but as per Orion upgrade (NPM 12.x) requirement we need to 2012 O/S, So we are planning upgrade accordingly,

but i am worry, when we are doing the o/s upgrade from 2018 to 2012, Can we face any challenges?.

i want your advise, Upgrade activity can create any issue in orion application, If yes ,please provide your suggestion or steps that i can use and upgrade the O/S of in Main Poller and addition Poller.

Find more posts tagged with

operating system upgrade

Accepted answers

All comments

dodo123

I think the easiest way and will have the least amount of impact would be once the new server is ready use the old name and ip to save losing data and not having to tell all your clients you have a new ip address. Or have to tell security to add new ip to allow list.

I would follow this one Migrate SolarWinds products to a new server using the same IP and hostname - SolarWinds Worldwide, LLC. Help and Support

Any reason your going for server 2012 would go straight to 2016 (I was already on 2012 looking at moving to 2016)

Windows Server 2012, 2016 and SQL Server 2012, 2014, 2016 and 2017 Support - SolarWinds Worldwide, LLC. Help and Support

Also dont forget the sql box would upgrade this to sql server 2016 (I have done this already)

dgsmith80

I might be wrong, but it sounds like the OP was asking if an in-place OS Upgrade from Win SVR 2008 to Win SVR 2012 will provide any issues.

If that is the case then I would say that in-place upgrades are rarely reliable and whilst they might work fine and your SolarWinds software should continue to operate in today's market there are very few reasons to want to keep the old machine as the hardware specifications for NPM12.2 and onward are ever increasing. It would be easier to provision a new machine and then use the instructions above from dodo123 to migrate your environment to the new server keeping the same IP (Hostname is not as big of an issue there is a workaround for that).

If you totally must perform an in-place OS upgrade then I would suggest that you make sure you have a backup of your SQL Database (which is hopefully on a separate machine anyway) and then if possible take a machine image or snapshot. Then run the upgrade. If it doesn't work then simpy rollback and re-install the existing version of SW (You can upgrade to NPM12.1 on 2008 so if you do that first you can then use the new 12.1 installers to recover)

Hope that helps. If I was wrong then just ignore me and do what dodo123 said above !

- David Smith

Kenson - SolarWinds Authorized Partner

Training, Licenses & Professional Services

- LinkedIn

- Twitter

- Facebook

krishnamishra0786

I created the clone of additional web server machine VM and put out from network.

- Upgrade the OS successfully in clone machine .

- Once i disconnected the original machine and attach the Clone machine in network getting the below error, All orion service are showing stop.

i thought i should run the configuration wizard that might be can fix the issue. hence i ran the configuration wizard and i started getting the additional below issue.

then i went on below link and installed the .NET 4.5 in additional web server and then all issue auto fix.

dgsmith80

I think maybe I missed something from the original post. Is this JUST the Additional Web Server that you are trying to upgrade?

If I was you I would just uninstall all the SolarWinds application and re-install from scratch, the AWS isn't holding anything specific to your installation as it's all held on your main server.

I apologise I think I mistook your original post as a question about upgrading your main Orion Server not the AWS.

krishnamishra0786

No Problem,

We are still in queue to upgrade the Additional Poller, Main Poller,

the same above step i will use to upgrade the all poller one by one, Hope the same will help us which i followed.

thanks

bourlis

From my recollection from when upgraded our systems, there shouldn't be any issues. Except, possibly the web console not being available during the OS upgrade.

As for steps this is how I would do it.

Upgrade the OS of the AWS first.
Give the system a day or 2 for burn in time and to fully test the web console.
Upgrade the OS on any APE's you might have.
Give the system a day or 2 for burn in time and to ensure the polling engine is working accordingly.
Upgrade the OS on the Primary Poller.
Give the system a day or 2 for burn in time and once again to fully test everything.
<optional - have a "cold one" to celebrate.>
Upgrade to NPM 12.2 HF3 and Orion Platform 2017.3 HF5 on the Primary, then the APE and then on the AWS.
<optional - have 2 "cold one's" to celebrate and brag>

krishnamishra0786

thank you Bourlis for suggestion, i was just in testing phase of all action (in place or side by side OS upgrade) so that if any community user trying to select any option and getting error, he could solve.

however as per above all suggestion are true and useful for all of us and we will use anyone to upgrade the OS and Orion environment.

thanks in Advance to take time for suggestion.