Finance | Project Operations, Human Resources, ...

Failover Clustering for SQL & AOS - AX 2012

(0) Share

Report

Posted on by Muneeb

895

Hi,

I am using AX 2012 R3 CU13 ... No Failover is implemented in the current scenario. ... Now suppose if I am looking for new Architecture where Failover clustering needs to be implemented if any of the servers is down.

Like we have 4 servers, 2 for SQL & 2 for AOS.

SQL1, SQL2 - If one is down, other should be up without any interruption to the end user while user is using Application.

AOS1, AOS2 - If one is down, other should be up without any interruption to the end user while user is using Application.

AOS1 - Primary AOS

AOS2 - Batch Server

Now when the user is using the Application, if i make any of the servers down i.e. SQL1 or SQL2, the Application remains uninterrupted; this works perfectly fine as failover clustering is implemented for SQL.

QUERY: I have not implemented this failover scenario for AOS servers, can we implement the same behaviour for AOS1 & AOS2 servers i.e. When either of the servers is down i.e. AOS1 0r AOS2, the Client Application on the end user's machine should remain uninterrupted? IF IT IS POSSIBLE, CAN YOU PLEASE BRIEF ME ABOUT IT???

[Refer to below image for the new architecture which i am thinking of]

Would Appreciate for your advice.

Sincerely,

Muneeb

I have the same question (0)

All responses (4)

Answers (0)

Sort by

André Arnaud de Cal... 304,729 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Muneeb,

There is a blog with some best practices on High availability: community.dynamics.com/.../high-availability-best-practices-for-dynamics-ax-2012.

When something occurs like an AOS becomes unavailable, there is always a client interruption. Even with an SQL fail-over, there might be a hick-up if there was some temporary data used on the SQL node which got unresponsive.

Was this reply helpful? Yes No
Muneeb 895 on at

Like (0)

Report
Copy link

Link copied!

Hi Andre,

I was reading your blog,

1. If SQL failover is configured, there will not be any interruption to the user meaning the client wont close for the user.

2. If the AOS failover is implemented, the client for the user that is pointing to AOS1 will close when AOS1 is down. But he can reopen the client which will now point to AOS2 as AOS failover is configured.

Is this point #2 correct?

Sincerely,

Muneeb

Was this reply helpful? Yes No
Suggested answer

guk1964 10,888 on at

Like (0)

Report
Copy link

Link copied!

The terminology often overlaps and some times so does the functionality so it can be confusing. However, there is a difference between AOS load balancing, or Network load balancing,or a SQL cluster, or a failover 'heartbeat' software that also fails over at application level.

I suggest start by reading the help:

https://docs.microsoft.com/en-us/dynamicsax-2012/appuser-itpro/configuring-network-load-balancing-for-services

https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/use-a-sql-server-cluster-for-the-site-database

https://docs.microsoft.com/en-us/windows-server/networking/technologies/network-load-balancing

Microsoft comment to consider "Based on our experience, the most common issue that users encounter when they use Network Load Balancing (NLB) is that they are not informed enough about the technology."

Was this reply helpful? Yes No
André Arnaud de Cal... 304,729 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi Muneeb,

Users can indeed reopen the client, but they need to start the latest action(s) from scratch. E.g. open the sales orders form, find the order where they worked on. Check the last changes and continue editing.

Was this reply helpful? Yes No