Edit the hosts.etc file for WebGIS DR tool

[forestknutsen1]

We want move our Enterprise environment to a new servers. We want to move from 10.8.1 to 10.9.1. We are deployed on a single machine, e.g. Portal, ArcGIS Server, datastore are all installed on a single machine.

I would like to edit the hosts.etc file on the target machine so I can run the import. My question is this: what is the public URL in this case and what exactly should the edit look like.

Is the public URL the on configured in the portal web context? The web context is pointing to the portal web adaptor via the load balancer, e.g. https://maps.domain/portal_webadaptor. What about the server web adaptor? Do I need that as well (I would think so). Then what about the enterprise URLs that are from the machine not via the load balancer, e.g. https://machineanme.domain/webadaptor? Do I need to worry about that?

I don't know maybe I just need one line in the hosts file -- IP and the load balancer URL before the web adaptors. So something like:

101.53.34.95     https://maps.domain/

Looking at some of the services json files they appear to point to https://machineanme.domain:6443/arcgis/rest/services and in other cases point to the web adaptor via the load balancer.

The "url" element is pointing to the load balancer and the "privateUrl" is pointing to the machine/port url.

[rshihab]

Hi,

in the webgisdrtool, you can either use the same public URL or use the machine name in the properties file.

[RyanUthoff]

This blog post was incredibly helpful for me when I migrated an Enterprise environment to a new machine. Migrate to a new machine in ArcGIS Enterprise using the WebGIS DR tool

Basically, you will add a new entry into the hosts file.

10.0.0.2 newmachine.domain.local enterprise.domain.com

10.0.0.2 = target machine IP address

newmachine.domain.local = target machine FQDN

enterprise.domain.com = DNS alias of source machine (and also target machine)

The purpose of the hosts entry is so that you can maintain your DNS alias without it affecting your source environment. You will still be able to access your DNS alias of your target machine (which might be required for installation/configuration), but only on machines where you modify the hosts file.

Once everything is configured on your new machine, just update your DNS to resolve all requests to the new machine, and remove the hosts file entry.

It's been a while since I've done this, but for your public URLs, I believe all you will need to put in your hosts file is https://maps.domain/ and that will take care of all of your contexts (like your Portal/Server web adaptor). I don't think you need an entry for each context/web adaptor.

[forestknutsen1]

Thanks for the feedback. I am going to try it.