Select to view content in your preferred language

Migration and Upgrade Steps

863
14
08-04-2025 06:49 AM
ZachBodenner
MVP Regular Contributor

Hello,

We're planning a migration/upgrade combo soon, and I want to make sure I have my steps down pat before we kick it off. I have a ticket open with support and they have essentially ok'ed this workflow, but it has taken a few rounds of explaining and research, so I wanted to post here also to see if anyone has done something like this before and if there's anything I'm missing. Here's the scenario:

We have Enterprise at 11.1 installed all on one machine, with web adaptors pointing to the Server and Portal on a DMZ machine. We are going to 11.5 on a multi-machine deployment, with two Server for ArcGIS Servers, a Portal server, and a Datastore server. The idea behind the two Servers (Server 'A' and Server 'B') is that one will serve the high throughput/heavy usage services, and the other will be for shared instance, less used services. So, we will need to republish all of our services and recreate our maps and Experiences. 

For these reasons, WebGISDR wont work, because we are going to an un-mtaching multi-machine, with new URLs for the Server services, but we would like our Portal URL to remain the same during and after the migration. We would also like to be able to continue operations as normal during building our new services, as that will take quite a while. 

So here are the steps as I understand them using the Join Sites method:

  1. Create new Portal VM Machine and install Portal 11.5
  2. Create new Server VM Machine and install Server (A at 11.5)
  3. Create new Server VM Machine and install Server (B at 11.5)
  4. Create new Datastore VM Machine and install Datastore (11.5)

                4.b Install 11.5 Server Web Adapter A and B on existing DMZ VM Machine

  1. Join new Portal to Old Portal using Join Sites, remove old Portal

                5.b. Uninstall the Portal 11.1 Web Adapter and install 11.5 Web Adapter (expected downtime during this process)

At this point, what we have is a Portal running 11.5 that is otherwise identical to our current Portal, referencing all of our services on current Server (11.1). All of the maps and apps our users are using are still drawing from the older servers, but that’s fine because then they can continue to use them while we migrate their services?

  1. Publish new services on the A,B, and DataStore machines.
  2. Join Server A to site
  3. Join Server B to site
  4. Join Datastore to site

Now, we have a Portal with three ArcGIS Servers registered with is (existing 11.1 and two new at 11.5), and a server hosting DataStore 11.5 (so four total)

     10. Create new web maps, apps, etc using the new services. (this part takes a while.

     11. When all maps and apps are recreated and tested, remove current 11.1 Server and Datastore from site.

     12. Portal automatically Federates Server A and recognizes the B and Datstore machines?

 

Does that order of events make sense? Does it sound like the behavior I expect from the process is what would actually happen? Like I said, ESRI Tech Support has said this should work, but I have only done a migration from AGOL to a totally fresh Enterprise, and also in-place version upgrades. This is a next-level up in complication and I want to do it right.

Happy mapping,
- Zach
14 Replies
ZachBodenner
MVP Regular Contributor

Okay that makes sense, so really the webgisdr will recreate our existing Server instance but I can just kind of ignore it as we go about publishing our new services.

And so that last idea about just utilizing a web adaptor to point to a totally new Portal isn't something super advisable?

Happy mapping,
- Zach
0 Kudos
ZachBodenner
MVP Regular Contributor

@JakeSkinner I've done a bit more on this migration and I think I understand just about everything except the web adaptor portion. So I tried to import a webgisdr file to the new environment, just as a test, but I hadn't installed a 11.1 web adaptor that pointed at the new Poral yet, so technically the public URLs were not the same. That makes a lot of sense to me, so I'm trying now to install the temporary web adaptor for Portal and running into some issues. The install goes fine but I can't access the web-based configuration. When I attempt to hit the config URL ( https://ep-gisportal.ci.eden-prairie.mn.us/portal/webadaptor/portal ) I get a an error 404 The request resource is not found. Per your suggestion, I'm installing this on the machine that will eventually run our Portal and it the machine that the webgisdr import is going to. 

Happy mapping,
- Zach
0 Kudos
JakeSkinner
Esri Esteemed Contributor

@ZachBodenner did you update the hosts files on each server?  Each server that has an ArcGIS application installed should have the following entry in their hosts file:

IP Address of Web Adaptor/Portal server |  FQDN of Web Adaptor/Portal server | DNS of original Enterprise environment

Ex:

10.0.0.1        portal.esri.com     gis.esri.com

After the entries are made, each machine should be able to hit https://gis.esri.com and it will resolve to the new Web Adaptor/Portal server.

0 Kudos
MichaelVolz
Esteemed Contributor

Jake:

Is the hosts file that you need to update located at C:\Windows\System32\drivers\etc on a Windows Server server?

0 Kudos
JakeSkinner
Esri Esteemed Contributor
0 Kudos