Does anyone agree that Orion Services and IIS should be stopped before taking a snapshot and upgrading?
I just want to make sure if we have to revert a snap, its best to have no connections in memory etc.
Or, a combination of both?
Thanks
I have done solarwinds upgrade and even reinstallation. We never stopped the services and took snapshot. We even rolled back those snapshots but there was no issue.
Haven't really done that on my past upgrades. But feel free to do it. Just follows the guidelines below.
documentation.solarwinds.com/.../install-prepare.htm
Our upgrade was flawless - my PTSD from the 12.3 upgrade era feels diminished.
I was just "reminiscing" about those days with a colleague. My first in person consulting gig was a SolarWinds upgrade that I completely butchered the first time around, but thankfully we had taken backups and so I took a second crack at it and everything worked. It was back when you needed to navigate through the matrix of products and compatible versions and step through the installer like 10 times to get where you wanted to be and somewhere along the way I must have messed up one of those jumps.
I remember those days well. Upgrading each individual product one at a time and step through the upgrades when to get to the latest one. Fun times
We normally just clone our VMs.
We used to do snap shots, but based off the change in log files in SW, the snaps would grow pretty large. We then normally hold onto them for a couple weeks, just to make life easier. There is the inherit loosing potentially weeks of data with this approach, but we question the stability of rolling back versions as well.
