Latest Contributions by JonathanQuinn

The problem is the trailing slash on the WebContextURL property in Portaladmin, ex.   https://prod.[our-on-premise-portal].net/portal// Remove the trailing slash and things should start working. ... View more

The WA URL is set based on the URL you used to access the registration page if you go through the browser, or the /w argument if configuring via the command line. If you have an alias and the wrong URL is used when registering, you don't really need to update it because the WA can still proxy requests to the server it's registered to even if it's accessed through a URL that wasn't used in the registration. That's not the same for Portal, though. Once you federate, the URL you used for the services URL is what is stored in items in the portal. You can update the URL without unfederating/refederating, but you'll need to update references to the URL across all service items in the portal. ... View more

Agreed with @ReeseFacendini; you could create both WebGIS DR and separate Data Store backups, and restore only the Data Store backup if there's only a problem with the Data Store. The problem is potential orphaned services and content. Publishers or administrators may have published data that didn't make it into a Data Store backup, (i.e. they you create a Data Store backup at 12:00PM and someone publishes at 12:10PM). If you restore the backup from 12:00PM, the data associated with those new services can't be found, so the item is unuseable. ... View more

Yeah, that guy is the problem. It's a cloud based cache store, (AWS S3 bucket or Azure BLOB container). Can you edit the directory to see if the information related to how it was registered is familiar? The restore sees that forward slash and thinks the backup is from a linux environment. You may be able to unregister it, restore, then re-register it with the same name so existing services that use it can still access the cache, if any are configured to do so. ... View more

There's really no need to continue to create Data Store backups since backups for Enterprise need to capture everything at a single point of time. The only argument for both types is if you only have to restore data from hosted services. The challenge, though, is there's a chance you may be left with services that are missing data if those services have been published after the last backup of the Data Store. ... View more

You can update both the Services URL and the Admin URL via the Sharing API without unfederating/re-federating: https://community.esri.com/t5/arcgis-enterprise-questions/edit-portal-services-url/m-p/430617/highlight/true#M16656 However, as @ReeseFacendini indicates, all existing services will have the incorrect URL. You can also edit the URL for each service via the item details, which can be scripted or done manually. ... View more