Can we have Multiple Azure WEB servers hosting common Nav Instances to a single Azure database

mathmos_uk

- NAV 2016 CU13(9.0.47256.0)
- IIS 8
- Servers all 2012 R2

We have 4 Azure Classic Servers with NAV Instance for RTC, Clickonce and SOAP all connecting to a common Azure Database and using the Load Balance End point to share the opened ports to allow the traffic through.

We have named all the NAV Instances (one on each server) the same.
This works perfectly for the the services (RTC, SOAP, OData and Clickonce) and balances perfectly, splitting the clients across the cluster.
I Need to extend this to the Webclient and Tablet users as they are currently connecting to a single server (one of the instances).

Duplicating the existing working IIS and NAV web server to another of the servers and extending the Load balancing(LB) port to the new server kills the web traffic. (previously working Web clients cant find the NAV instance)

I removed the the Old Server from the LB set and the Web access to NAV is fine once again(and vice versa), but as soon as I have two Servers handling the web traffic it all falls down. I have looked online and cant really find a definitive answer to whether this is possible to do in the Classic VM Azure environment (There is plenty of info relating to this being possible in the Azure ARM -New Client using the newer Load balancing but not the Classic clients).

If anyone has any insight on this it would be great.
Thanks
Matt

Jan_Veenendaal

I think this is because the default Azure Loadbalancer does not send calls from the same client to the same server every time - causing e.g. a query to be run on server1 and the client trying to get results from server2.

Only solution that I know is to use a custom-built load balancer that remembers which client is using which webserver-instance; distributing clients to servers only on first contact.

mathmos_uk

Thanks for the info, I have since managed to get the servers balancing but on the new NAV server I now get "The connection to the server was suspended" from a Web or cloud client after just a few seconds on inactivity. I have checked the Client Timeout set on the NAV instance and cants see an issue.