Latest Contributions by danbecker

We just created an Az db for Postgres -Single server instance for Enterprise gdb storage.   Using PGAdmin, I logged in as postgres_admin, then created an sde user that does not have super user permission. I then created a db, with sde user as owner. In Pro 3.1, I connect to the db as sde user, then run the Enable Enterprise Geodatabase tool. I then created dbo user using the Create database user tool, connect as dbo in Pro and start creating FCs. Im seeing 2x performance/speed with the managed instance compared to our 4-cpu 32gb memory Linux Ubuntu Azure VM.  ... View more

The only advise I have is to not mix Linux/Windows OSs in an ArcGIS Enterprise stack. I wish this would be added to the Enterprise install documentation. We currently run Portal and Datastore on Linux Ubuntu 20.04 VMs and Server on Windows. This prohibits us from using the webgisDr backup utility, REST /exportSite, REST /importSite or Join-Site methods of migration. I.e. we cannot move our Enterprise stack to Azure (all Windows), without manually scripting a solution in Python. ... View more

"source": "https://ourdomain.com/portal/sharing/servers/8227a14cb3704f4bba79df3963bf297c/rest/services/World_Imagery/MapServer", "error": "{\"code\": 35, \"messageCode\": \"OffPkg_ 35\", \"message\": \"Export tile operation https://tiledbasemaps.arcgis.com/arcgis/rest/directories/arcgisoutput/World_Imagery_MapServer/_ags1642778840_ch failed error {\\\"code\\\": 30, \\\"messageCode\\\": \\\"OffPkg_ 30\\\", \\\"message\\\": \\\"Accessing url https://tiledbasemaps.arcgis.com/arcgis/rest/directories/arcgisoutput/World_Imagery_MapServer/_ags1642778840_ch?token=longtokenhere.. returned error <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1091)>\\\", \\\"params\\\": {\\\"url\\\": \\\"https://tiledbasemaps.arcgis.com/arcgis/rest/directories/arcgisoutput/World_Imagery_MapServer/_ags1642778840_ch?token=longtoken..   New Enterprise site on Azure is having above issues when generating offline areas. Is this a cert. trust issue between our Server machine and https://tiledbasemaps.arcgis.com? ... View more

Our Enterprise deployment of Portal (Linux), Datastore (Linux), Postgres (Linux) and Server/webadaptor (Win) is NOT recommended for anyone reading this. There's not an out of the box method of migrating Enterprise site/data with mixed OS. webgisdr - not an option since the backup operation must access the same file share across all VMs. Lin/Win UNC paths are different. REST export/importSite - not an option since importSite also restores all site settings on the target VMs, so they have to be the same OS the backup was taken from. Azure Enterprise VMs are all windows. Enterprise components installed on separate VMs (new local domain names as well). Using hosts file edits on the VMs, Azure Server machine was federated with the same production.domain.com alias as used on-prem. In order to use ArcGIS API for Python to copy data between sites, both sites had to be accessible, so Azure webadaptors were configured with newsite.domain.com DNS alias. Public DNS A-record for newsite.domain.com was created, pointing to Azure Web App Gateway. I noticed that attempting to login to Azure server manager via internal.domain.com:6443, you're redirected to federated URL (production.domain.com) to login, again a hosts file manipulation so that Azure site handles the request. ArcGIS API for Python is the only method of migrating content, I'm using these examples: https://developers.arcgis.com/python/samples/clone-portal-users-groups-and-content-rn/ Users and groups were easy. Web maps were also copied, but I'm noticing the feature service layers (none are hosted, all are referenced) in web maps point to newsite.domain.com?id=guidFromProductionItem So, when I used the above python GIS.content.add() method to move the feature services, I specified item_id=guidFromProductionItem. Now the feature services in Azure have the same itemID, but the referenced REST service (production.domain.com/server) is obliviously not created. Using Pro, I attempted to overwrite the Portal feature service that I had copied using Python, but that doesn't work, error: unable to retrieve server details. That makes sense because the services doesn't actually exist in Azure. So, I published a new feat. service from Pro using the same folder/serviceName, but this creates a duplicate feature service item in the Portal. Any pointers here? Can you publish services from Pro, and not create a Portal Item in the federated portal? That workflow is accomplished via Python GIS.content.add() since we need to maintain the itemID. The good news is that the web maps that were copied using Python work without issue after the service is published to Azure. Webmaps contain the old layer references (id=guidFromProductionItem), which were moved to Azure, which point to the newly published Feat Service, so all is well. But, I have that duplicate portal feature service item? If I delete it in Portal, then the server service is also deleted. It's like I need to delete the Pro-created feat service Portal Item, then link the service to the feat service Portal Item that I copied with python. Is this possible?    ... View more

So, after portal is installed on Linux, there's no way to ever move that to a win machine? ... View more

This problem was fixed by simply rebooting the VM, all is well now, Lol. I uninstalled datastore from C:\, then reinstalled on E:\ without rebooting in between. ... View more

Maybe this issue is related? My install path was E:\Program Files\ArcGIS\DataStore ..with a space   https://support.esri.com/en/technical-article/000015832             ... View more

Thanks for the help. Yes, we're aware of the ArcMap services, and are staying at 10.9.1 during the migration. I figured it was best to not upgrade versions in the middle of the lift-and-shift to Azure.   How about we deploy an Azure VM for PostgreSQL, replicating our on-premise environment. We can deploy it as newdb.ourdoamin.com, migrate the db's, then, when we edit the external DNS record to point traffic to Azure, disjoin currentdb.ourdomain.com from AD, then rename the Azure equivalent?   We can then casually start using Azure hosted PostGresql, and eventually re-publish all services pointing to the hosted instance and shut down the Azure PostgreSQL VM.    ... View more

After migration, (ArcGIS Enterprise site & SDE gdbs from on-prem to Azure db for Postgres), what if we had the  oldhostname.ourdomain.com FQDN resolve to the IP of the Azure db for Postgres, where the dbo and password are identical. Would this split-horizon DNS setup require re-publishing every service? ... View more

Can someone elaborate on the process of updating the SDE connections after migration? Our old on-premise DNS name will be different in Azure and there are issues with setting up a split-horizon DNS policy that resolves Azure requests to the new hosted postgres instance. After migration, do we just update the datastore connections, or does it require re-publishing each service? ... View more