web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Micrososft AX on DR
Microsoft Dynamics AX (Archived)

Micrososft AX on DR

(0) ShareShare
ReportReport
Posted on by zero00roma 37

after installing DR site and install AOS how to redirect AX users to use DR after live is down ??

when I try to connect to AOS on DR a faced this error: 'The description for Event ID 110 from source Microsoft Dynamics AX cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.'

but everything is ok on my network and there is no problem with the connectivity between DR and Live.

what I need to do to resolve this and allow users to auto shifing to DR after live is down ??

*This post is locked for comments

I have the same question (0)
  • Martin Dráb Profile Picture
    Martin Dráb 237,996 Most Valuable Professional on at

    Please give us more information. First of all, what you mean by "DR" in your particular case? Disaster recovery?

    What do you mean by "connecting to AOS on DR"? That you install an AOS somewhere and you can't connect to it? If so, how are you trying to connect to it and from where? Do you get an error message?

    Regarding the event log message, are you looking at the right machine (the server with AOS)?

    Have you installed an independent AOS or are you trying to build a cluster?

    There is little we can do for you if you don't give us enough information about your situation...

  • Martin Dráb Profile Picture
    Martin Dráb 237,996 Most Valuable Professional on at

    Regarding "auto shifing to DR after live is down", please explain which component are you trying to address at this moment.

    If you mean AOS, you should use a cluster. When one AOS is the cluster is down, the remaining AOS servers in the same cluster will keep serving users.

  • zero00roma Profile Picture
    zero00roma 37 on at

    I have 2 sites

    1- live with 2 AOS and SQL server on HQ.

    2- Disaster recovery with 1 AOS and SQL server on different location.

    so I already configured a failover between 2 AOS on live site and I need to do same between DR & Live which allow users while live is down to shift to DR AOS.

  • Martin Dráb Profile Picture
    Martin Dráb 237,996 Most Valuable Professional on at

    Think about what kind of failure you want to recover from - it's not clear from your description.

    I still don't know what you have done (because you told us so little), but if "Disaster recovery with 1 AOS and SQL server on different location" is a completely separate environment, you can't expect " to do same" as what you see inside a single clustered environment, because these are two completely different things. Please confirm whether it's the case.

  • zero00roma Profile Picture
    zero00roma 37 on at

    I am talking about any failure on production environment.

    Disaster recovery on different location but not completely separate environment because its connected together such as synching database and active directory database.

    so its not separated on connection but on different location.

  • Martin Dráb Profile Picture
    Martin Dráb 237,996 Most Valuable Professional on at

    Unfortunately there is no single solution for all possible kinds of failure.

    Your answer seem to suggest that you indeed mean a separate installation of Dynamics AX, therefore it's a completely different thing than what happen inside a single (clustered) environment.

    I wonder why you decided to use this architecture and installed servers if you don't know whether it can achieve the goal. You should stop and go back to the design phase.

    I suggest you start with thinking about scenarios you want to cover. For example: a single AOS is down, a single database server node is down, there is a problem with storage, the whole site is unreachable, Active Directory isn't responding and so on.

    Then think about your options, such as DB replication, AOS clustering, load balancing, network interface redundancy etc. Also, think about requirements such as the time of recovery, the acceptable data loss and maintenance costs.

    When you decide that you need a separate installation of AX (and not just having redundant components at a different site), and you cover all issues such as keeping code, metadata and data in sync with the production environment, then it'll be time to start thinking about how to do it.

    Because users normally connects to the production environment and not your backup environment, you'll have to either change the configuration to point to the backup environment (e.g. by replacing a shared .axc file), or you'll have to change meaning of what it's inside the configuration (e.g. 'AxLive' hostname will start translating to a different address).

  • zero00roma Profile Picture
    zero00roma 37 on at

    thanks for your reply

    sure there is no single solution for all failures. that's why I am talking here about basic configuration between DR and production.

    if a single AOS is down there is another 2 instances on the AX cluster to recover it, I have S2D cluster to recover all resources not just storage and DPM backup system and 3 domain controllers to recovering any issues with AD.

    our DB administrators already configured the DB replication between both sites DR & Pro, and we have complete recover solution for disaster except my question.

    on AX cluster on production (check the attachment) any instance is down user will go to a second one. so i need to make AX on DR same like this.

    i hope my explanation and my language is clear enough and sorry if its not.

    Screenshot-_2800_158_29005F00_LI.jpg

  • Martin Dráb Profile Picture
    Martin Dráb 237,996 Most Valuable Professional on at

    You're looking at a cluster configuration of a single environment. As I mentioned a few times, that a completely different case than having two separate installations. If you want to extend the cluster, stop building another independent cluster.

    And if you want two separate environments, playing with cluster configuration of any of your two environments won't help you. Look at the last paragraph of my previous reply if you decide to go this way.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Martin Dráb Profile Picture

Martin Dráb 4 Most Valuable Professional

#1
Priya_K Profile Picture

Priya_K 4

#3
MyDynamicsNAV Profile Picture

MyDynamicsNAV 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans