Hardware & Software configuration

Ignition
1

Hello,
I have a project with Ignition 8.3 that requires a little attention and the last option was to ask here:

  1. I have two servers that need to run redundantly, one master and the other slave, but at the same time on both servers run Microsoft SQL linked via failover cluster with always on availability.

The problem is that it works for a while and then the SQL services don't start, or Ignition doesn't connect to the listener anymore. Has anyone tried this configuration?
In the end I had to reinstall Win Server because I couldn't fix the services.

If that's not possible, maybe buying a third server to run SQL exclusively?

  1. If the Ignition Servers are redundant and redundancy is active, I simply can't make any changes in the designer, I have to disable redundancy and it just works. Is this normal?

Thank you!
I hope you can help me with these topics.

I attached a picture of what I found in the examples but nowhere was it described what I tried.

image
image985×681 61.4 KB

2

Don't run the redundant SQL in the same servers as Ignition. The SQL cluster needs to be separate, and present a single connection address for Ignition to target.

3 Likes
3

And your question on redundant servers is correct. Changes are only allowed on the master server even if it is unavailable. The idea here (in my mind) is that if your master server is down/unavailable, that should be priority #1 to get it running again to restore redundancy rather than making changes to the system. (But that's my opinion).

2 Likes
4

Michael's right. If your designer is connected to the primary server and not the backup then you should be able to make changes to it without touching the redundancy settings and it will push changes to the backup automatically. If your saying you can't make changes on the primary without disabling redundancy then you'd need to contact support.