Latest Contributions by JonathanQuinn

If you were to stop the standby portal, do you still see problems? What kind of settings are changed within the web maps or feature layers? ... View more

What behavior are you seeing in the Portal? Are you unable to sign in to Portaladmin or the home app? What errors are there in the portal logs? ... View more

I would also suggest contacting Technical Support and relaying that the errors returned to from the tool are not descriptive enough for you to know how to fix the problem. ... View more

You can delete that account. It's created to do some intermediary work during the upgrade and was leftover in the index as an oversight. Run a user reindex via the Portal Administrator Directory and that will get rid of the user. ... View more

I believe a graph database is able to store relationships/hierarchy between data elements, which is what "nodes" and "edges" refers to. I don't think that the Data Stores "node" reference is equivalent of a "node" in a graph database. But take all that with a grain of salt, , just speculation on my end. No, that's definitely not the strategy. The spatiotemporal data store can support terabytes upon terabytes of data; that's of course not going to memory. Due to the immense amount of data the spatiotemporal data store can store, which would also involve indexing and other operations, the memory requirements of the spatiotemporal Data Store are significant. ... View more

Part of the challenge you may run into is that if the WA creates the "public" or "frontend" URL for you, (the URL clients use to reach the Portal and the URL), then it's stored in all items and within the federated server. If your new server has a different FQDN and you move the WA onto it so you can register with Portal, you'll need to handle the new URLs in all data. If it's a new machine but has the same CNAME, then you just need to make sure you use the same URL to register the WA and you'll be fine. ... View more

Those logs are transaction logs and integral to the internal database used within Portal. You typically won't want a database writing to a share for internal processes, so there won't be an option to store the transaction logs on a share or outside the local file system of the database. We are working on separate options for the DR tool, one that expects you to run them on a scheduled basis so the transaction logs won't be a problem, (replicating to a standby environment), while the other creates a backup for point-in-time restores, (backup/restore workflow). The latter would not cause the problem with the transaction logs. The same information applies to Windows: Common problems and solutions—Portal for ArcGIS (10.6) | Documentation for ArcGIS Enterprise  ... View more

Not too versed in database nomenclature, but I'd say, no, ES is a document database, not a graph database. Both fall into the category of NoSQL though. ... View more

Yes, the DR tool does support a local drive for the BACKUP_LOCATION. It may look for the path within it's own directory after it can't find the absolute path on the file system. Can you provide a screenshot of the properties file you're using, obscuring/omitting sensitive information? ... View more

Once you run the DR tool, the expectation was that you'll be scheduling backups on a regular basis. In order to clear out those logs, you'll need to run the DR tool again to create a new backup, which deletes them: Common problems and solutions—Portal for ArcGIS (10.6) | Documentation for ArcGIS Enterprise  There is an enhancement to improve this behavior: ENH-000123248 Allow users to completely turn off the incremental backup at their discretion ... View more

No, there are no plans to support Scality at this time. ... View more