High availability on Azure

[mody_buchbinder]

We are trying to build High availability of server + Portal in Azure.

We have a common arcgisserver directory.

It works very slow and we found that there is a lot of requests to this directory that does not work so fast.

Did anybody implemented HA on Azure?

What is the best practice here?

Thanks

[Anonymous User]

Hi @mody_buchbinder,

Are you trying to build this environment from scratch, or by using the ArcGIS Enterprise Cloud Builder for Azure tool? 

We'll typically encourage you to use the Cloud Builder tool as this simplifies a lot of the configuration steps and sets things up using our preferred values. The resource I linked contains a wealth of information on ArcGIS Enterprise in Azure that should help clear some things up.

[mody_buchbinder]

Hi Elliot

Thanks for the answer.

The original installation was a simple installation on Azure machines.

Yesterday we started to check the cloud builder to indeed use it as an example to see what is esri best practice are.

We are in the process of building the machines and we will have to try to change parameters to see how it is affecting performance.

There are a few other options in Azure, for example use only one machine but make Azure keep a copy of it.

Best practice is good but people that really uses it is even better 🙂

[ChristopherPawlyszyn]

Hello @mody_buchbinder,

Can you elaborate a bit further on the shared storage in-use on your ArcGIS Server site? I have seen some performance issues with the standard Azure Files shares as they are not quite responsive enough to host the config-store and directories. The premium shares did alleviate the issues I faced when deploying a multi-machine site, or you may consider hosting a network share on one of the Azure VMs you have deployed already or using a dedicated file server depending on your architecture needs.

[ElliotJones]

Hi @mody_buchbinder,

Are you trying to build this environment from scratch, or by using the ArcGIS Enterprise Cloud Builder for Azure tool? 

We'll typically encourage you to use the Cloud Builder tool as this simplifies a lot of the configuration steps and sets things up using our preferred values. The resource I linked contains a wealth of information on ArcGIS Enterprise in Azure that should help clear some things up.

[JonathanQuinn]

You can also look into storing the content in Azure BLOB containers, which gives you redundancy out of the box. It'll be slower than what you get out of the local file system, but perhaps comparable or even faster than what you see in a shared location, depending on your storage tier.

[MengLi]

We had an Azure AGE deployment (manually installed) with one Portal, one Data Store and 2 Servers accessing config store and content directories from Azure File Share (standard). Two major issues:

1) 2 AGE servers often end up one being stopped in accessing the file share, and we were told some issues for the redundancy servers accessing an Azure file share, and hence to consider blob or a file server VM. But Azure file share is a standard storage resource, and why AGE servers couldn't work well with it? and what are pros and cons of using a Azure File Share and a server VM for the config store?

2) since our Azure AGE upgrade from 10.6.1 to 10.8.1 in mid Match 2021, the cost (based on volume and transactions) of our Azure file share is tripled; and noticed that the daily transactions and traffic from our 2 AGE 10.6.1 servers to Azure file share was 3-5 millions, while after the upgrade to 10.8.1, it is 15 millions, and now after we removed one of the 2 AGE servers, the daily transactions decreased to 10 millions, but still significantly higher than AGE 10.6.1, is it by design? Our Azure contractor argued that he didn't see any server software triggering such huge amount of transactions for accessing a config / content store.

We are planning to relocate our servers config/content store from the Azure File Share to a dedicated file server VM on Azure.

Any other suggestions and experience would be much appreciated.