Hi all,
Image above is the database configuration in the gateway which is the Failover Datasource and Failover Mode. May I know that anyone use this before and how does it work actually ?
Currently, I have two NAS (Database) and two of my database actually have the replication features which means all my data will be replicate within these two database. In my case, it is necessary to use the failover datasource so I would like to understand more about this.
For example, if my reporting modules (Tag Historian Query) is getting the data from Database 1 then when the Database 1 down. Will my report still function correctly or I need to update the Tag Historian Query in my Ignition Designer.
Thanks in advance.
In almost all scenarios, I would recommend relying on your RDBMSâs failover rather than Ignitionâs failover settings.
Many RDBMS failover scenarios offer some kind of âvirtual IPâ or hostname; Ignition connects to that as a client, and if thereâs a problem with DB A, queries will automatically be rerouted to DB B.
Ignitionâs failover is basically the same idea, but itâs âdumbâ; all it does is see that a query to DB A failed and immediately attempt to run the same query on DB B. You donât need to change anything in your queries or project settings, because to the rest of Ignition, it attempted a query to A and it succeeded; the only place that âknowsâ something failed is the actual database connection.
However, the big downside is that this is direct translation of queries, thus DB A and DB B must be exactly identical for queries to have any hope of succeeding. If theyâre exactly identical, then youâre already using some form of DB replicationâŚand usually those do a much better job of keeping track of which DB is alive anyways - which is why I generally recommend not using Ignitionâs failover settings at all.
3 Likes
