nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Webgisdr in to replicate a highly available deployment (portal url)

MichaelSchoelen

We have two data centers, each with highly available, single-machine deployments:

mainmachine01.domain.com:7443/arcgis (active)
mainmachine02.domain.com:7443/arcgis (standby)
and
altmachine01.domain.com:7443/arcgis (active)
altmachine02.domain.com:7443/arcgis (standby)

Currently, the main site is active (bold). You can get to it from https://maps.portal.com/portal. If we flipped to the alternate data center, it would still be the same maps.portal.com/portal

We want to replicate the deployment between the two sites. So two questions:

When I backup the main site using the webgisdr utility, what should I specify as the Portal URL in the export webgisdr properties file? maps.portal.com/portal? Or the active machine name mainmachine01.domain.com:7443/arcgis
When I restore the site to the alternate data center, what should I specify as the Portal URL import webgisdr properties file?
maps.portal.com/portal (likely not)? Or the active machine name altmachine01.domain.com:7443/arcgis

Find more posts tagged with

Accepted answers

JonathanQuinn

How did you federate Portal and Server? On Site A, did you do something like this:

Services URL:

https://maps.portal.com/server

Admin URL

https://maps.portal.com/server

And on Site B, you did the same thing? If so, you're right, requests are being routed to the primary data center/deployment because Site B is resolved https://maps.portal.com/server to the primary environment. What you need to do is have your standby environment resolve maps.portal.com/server to the standby machines. This can be done through DNS or using a web adaptor to "fake" the URL:

For example, I have a traffic manager resolving traffic to my primary environment. I set up a standby environment and use a Web Adaptor as the front end. This machine's hostname is defined as maps.portal.com through etc\hosts and the entry is added to all machines in the deployment. You'll need to have also defined the web context URL in the second environment. When you take backups and restore them using the DR tool, all traffic will be routed to the standby machines based on the etc\hosts file entries. In the event you need to failover, remove the entries in the etc\hosts file so maps.portal.com resolves to your traffic manager.

All comments

JonathanQuinn

For the active site, you can use the "public" URL, (maps.portal.com/portal) or the internal machine name, (mainmachine01.domain.com:7443/arcgis). Both resolve ot the same machines.

On the DR site, you must use the machine name as requests to maps.portal.com/portal will resolve to the active environment.

Abdullah_AlFazari_1-1635679819185.png

MichaelSchoelen

So I'm trying the following:

Export site from: primarymachine:7443 on the main site

Success

Import site on: primarymachine:7443 on the standby site

Failed
Cannot find the portal properties from the server https://maps.portal.com/server

Interesting that the tool is looking at the load balancer name, as that would route traffic to the main datacenter.

When looking at the logs, I'm also seeing that the alternate site is attempting to reach out to the primary site machine, and failing. Which that doesn't seem right--this tool should be able to run in the event that the primary site went down.

Thoughts?

JonathanQuinn

How did you federate Portal and Server? On Site A, did you do something like this:

Services URL:

https://maps.portal.com/server

Admin URL

https://maps.portal.com/server

MichaelSchoelen

So my portals are already using web adaptors with the webcontext url set. Is it possible to just change the etc hosts file to point to that one?

I'm guessing that the alternative would be to wait until we fail over to the standby site, then restore the backup? Albeit, there would be 20 minutes of downtime as the portal restored.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.