Support Forums
Server redundancy for thin client connection

Hi,

We have configured 2 SCADA server. Both are having different public IP. when both servers are up thin client connections are distributed among two servers. but when primary server goes down we are not able to connect new thin client connection with the link of primary server public IP even if backup server is up. we need to connect to the secondary server's public IP manually.

So is there any way to have a single thin client link which can manage thin client connection even if any one server is down?

Hi, We have configured 2 SCADA server. Both are having different public IP. when both servers are up thin client connections are distributed among two servers. but when primary server goes down we are not able to connect new thin client connection with the link of primary server public IP even if backup server is up. we need to connect to the secondary server's public IP manually. So is there any way to have a single thin client link which can manage thin client connection even if any one server is down?

Not possible with VTScada.

You would likely need a DNS service which monitors the servers and switches over DNS Records dynamically. That'd still have a downtime.

You could also play with proxy servers.

Not possible with VTScada. You would likely need a DNS service which monitors the servers and switches over DNS Records dynamically. That'd still have a downtime. You could also play with proxy servers.

How to configure DNS for VTSCADA sever ? and what do you mean by proxy server.

How to configure DNS for VTSCADA sever ? and what do you mean by proxy server.
edited Jan 12 '22 at 10:35 am
75
2
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft