Using webgis DR to recover Enterprise installation in the same machine with new machine name

231
2
02-13-2021 06:43 AM
PierPy
by
New Contributor II

Hi all,
We have an installation of Arcgis Enterprise 10.6.1 on a single machine (server and portal federated).
For security reasons, and without planning, we have changed the internal domain name of the machine where the applications are installed (Portal, Server, Data Store and Web Adaptors).


After these changes our Enterprise environment was broken. Our customer support suggested using the file hosts configuration to map the internal IP address to the old internal FQDN. This solution worked well and, therefore, now, our Arcgis Enterprise is reachable and working well, but this configuration is not ideal for production...

We have applied the latest patches to our applications and used the webgis dr tool to back up everything, and now we are planning to restore a production environment with the new real FQDN machine name on the same machine without mapping the old name in file hosts.
We decided to proceed like this:

  • uninstall all applications,
  • deletion of the mapping of the old machine name in the file ... \ etc \ hosts
  • reinstall everything,
  • apply the same patches (or only the latest (cumulative?))
  • restore with webgis dr.

Reading this blog post {BLOG_link}, on a slightly different scenario {Migrate to a new machine in ArcGIS Enterprise using the WebGIS DR tool} we understood, thanks to this link {
https://enterprise.arcgis.com/en/portal/latest/administer/windows/overview-disaster-recovery-replica...}, that the webgis dr tool can handle the machine name change.

This table show wich item or setting must be identical across deployments when running the webgisdr utility

 

Item or setting10.6.1, 10.7.x, 10.8

Public portal URLs

Yes

Services URL for federated servers

Yes

Registered data stores other than ArcGIS Data Store

Yes

ArcGIS Server directory paths (for example, arcgisjobs)

No

Security information (LDAP URLs, proxy information)

No

Deployment type (single machine or highly available)

No

Private portal URL

No

Admin URL for federated servers

No

Machine names

No

Portal content directory

No

ArcGIS Server configuration store

No


Is there anyone who has successfully tried this solution for our problem?
Any other steps to keep in mind in this work?

Thanks in advance for your help!

Other, useful information:

  • xxx.yyy.it public host name (not modified)
  • zzz.www.local old private host name
  • name of the machine in the portal [... / portaladmin / machines] zzz.www.local
  • machine name on server [server / admin / machines] zzz.www.local
  • machine name in Data Store [... / server / admin / data / items / enterpriseDatabases / AGSDataStore_ds_DBNAME / machines] zzz.www.local
  • federation using this server name [.../portal/portaladmin/federation/servers]  xxx.yyy.it
  • Webgis dr output in --export mode

 

 

 

===============================================
Starting the WebGIS DR utility.
===============================================
The basic backup time and configuration in the current Web GIS
-------------------------------------------------- -----------
Portal: https://xxx.yyy.it/portal at 2/7/21 22:27
|
| - Hosting Server: https://xxx.yyy.it/server at 2/7/21 22:27
| |
| | - Relational data archive: https: //zzz.www.local: 2443 / arcgis

 

 

 

Greetings Pierpaolo

Tags (1)
2 Replies
AngusHooper1
Occasional Contributor II

I have been able to move a single-machine ArcGIS Enterprise deployment from one virtual machine to another using webgisDR. The SOP was pretty straight forward and the local hosts file change needed to be made before any software was installed on the new VM. 

To make your life easier, ensure your existing enterprise GIS is using a DNS alias across all configuration items that require a URL (where possible). Therefore any routing issues based on FQDN url (e.g. federated AGS service url) are mitigated.

You should have a thorough look at the portal and server admin settings (federation values, web adaptor settings, etc) and change FQDN to the DNS alias or to the new FQDN. You can easily test your changes by removing the entry from the hosts file and accessing the system from a separate client.

0 Kudos
PierPy
by
New Contributor II

Thanks AugusHooper1

can you confirm that after installing Arcgis Enterprise in the second VM (VM2) the machine name for Portal for Arcgis (the one you see in Portaladmin ... / portaladmin / machines) was different from that of VM1?

The problem in restoring the same machine is slightly different and more complicated and I cannot find any documentation on this solution.

In this situation the solution seems to be:

1) reinstall everything

2) change the machine name in the conf file. File

For the first point I don't understand what "reinstall" means. Is it possible to restore items and data (for example using webgis DR) or do you have to start from zero?

0 Kudos