Third Party Module Redundancy

3rd Party Modules
1

I have a third party module that requires a tag provider and database connection to startup, so when setting up redundancy, I create these manually on the backup gateway and restart it. I then follow the steps of setting up redundancy outlined here, that all works fine and redundancy status shows good on both gateways. The problem I'm seeing is that the tags that exist on the master gateway don't get copied to the backup gateway, so failing over, the application doesn't look right. I know the first step of redundancy says to:

  1. Start with a fresh install.
    Because the current configuration of the backup node will be overwritten, make sure that it does not contain anything valuable. It is a good idea to export any projects that are unique to the backup before enabling redundancy.

Are the tags not getting copied to the backup gateway because I manually created that tag provider and it wasn't the master gateway that created it when syncing?

2

Yes.

No configuration is to be done on the backup gateway, except that which is necessary to talk to the master.

Was the module designed to support redundancy?

1 Like
3

It was not, this was just to see if it was possible, but I have my answer, thanks Phil!