ArcGIS Server Pre-Install Questions

[JD1016]

Hello,

Within the next few weeks we will be switching to ArcGIS Server 10.9.1..  We are currently running ArcGIS for Server 10.4.1. on one machine.  This machine will soon be retired and a new one put in it's place that will be running ArcGIS Server 10.9.1..  As with all things, there is a certain degree of trepidation with hoping everything continues to function normally and a overwhelming desire to not over think the process.  I was not here when the original machine was configured and have never gone through this type of upgrade so I am somewhat anxious at the thought and have some questions.  I apologize in advance if my questions seem too mundane but my knowledge in this arena is somewhat lacking.

Question 1:  Should I "create a new site" or should I "join an existing site"?  I am assuming the reference to "site" is that which is visible through ArcGIS Server Manager and those services currently running on the, what will be, old server?  When I see "join an existing site" I'm wondering if by doing so it would be a way of migrating over those services currently on the old server to the new server without interruption.

Question 2:  Is there an easy way of doing this entire process that I may have overlooked given the fact we are starting with a new server and we have a server currently running services for ArcGIS Online?

Question 3: How can I tell if I have a "federated server"?

Question 4: Are there any good sources out there that offer a step-by-step guide for this installation?  By "good" I mean the literature takes you through it without missing a beat and is not afraid to insult your intelligence by including any and all minutia.

Thank you in advance for your patience and understanding.

Jeff

[Scott_Tansley]

Actually i now see how you’re reading that.  

I was in the distributor community and it was always harder to upgrade/migrate when new operating systems were required.

aboit 4 years ago there was a blog which showed how to stand up new machines, instal the same version, join site, deprecate old and then upgrade new.  It made a lot of sense and changed the game.

I maybe reading too much into this given you’re only using server and not full enterprise.

I’m risk averse and especially when working with client system/. I’d still approach this in the way I described because I know it works.

[JD1016]

Possibly yet another case as Brian was eluding to where information credibility comes into play.  It's terribly unfortunate to not be able to trust the directions being given by an entity that we are relying on to take us through something this important.

[Scott_Tansley]

“

If you are using Join Site to migrate, the new and existing machines do not need to match, but if you intend to keep all machines in the site, it is recommended that you ensure they meet the following criteria:

• It must be at the same version number as the other ArcGIS Server machines in the site.”

it’s talking about the operating system, memory and CPU, not the ArcGIS software version

[JD1016]

Unfortunately, the way that it was written is completely unclear.  I'm not seeing anywhere in there that it says if you are using the Join Site to migrate, the new and existing machines do not need to match...except for the ArcGIS software version.  

[Scott_Tansley]

back when I was a lad in the days of 8.x and 9.x the documentation was very geeky and technical.  It was awesome, in fact.  People complained it was too geeky.  It then became (IMO) a marketing style of documentation.  The information you need is often split over multiple pages and sometimes is contradictory.

personally I’ve been around server sans enterprise since the beginning of both and have installed and upgraded each version.  Sometimes I think I can do it in my sleep.  So returning to the document you shared. I can only say I can read it in two ways.  I know how I’d approach it and I know I’d get the results.  That’s experience though…. 

[JD1016]

You have the advantage of experience, which is what I wish I had.  When you look at things you can read into it based on a vast library of past knowledge.  Unfortunately, for someone like me, doing this for the first time, I rely on documentation to take me through the process and in this case it has left me with nothing but questions and frustration.

[Scott_Tansley]

I hear you.  I would hate to be a technical writer.  Like you, I prefer depth.  So many other people want it easy.  I honestly don't know what the right answer is in putting so much documentation out to such a wide audience.  I feel for them, and the support teams that have to support software on AWS, Azure, Google cloud, a myriad of IaaS providers, and probably on someones IBM 386 sx25!  😞

[Brian_Wilson]

Only Server! Ah! That will be much easier to upgrade.

Seriously I wonder if I might be happier without Portal. It was never my place to make that call.

Lots of the glitches I've had to work through involve problems with Portal and Server not being perfect partners.

[Scott_Tansley]

That’s a shame Brian.  When you do lots of installs, upgrades and healthchecks you learn how to tune it and make it sing.  They actually work together beautifully.

[Brian_Wilson]

Too bad Esri Support can't do that!