Welcome to the new Schneider Electric Community

It's your place to connect with experts and peers, get continuous support, and share knowledge.

  • Explore the new navigation for even easier access to your community.
  • Bookmark and use our new, easy-to-remember address (community.se.com).
  • Get ready for more content and an improved experience.

Contact SchneiderCommunity.Support@se.com if you have any questions.

Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel

[Imported] ClearSCADA HOT Standby probelm after restoration of Crashed server.

EcoStruxure Geo SCADA Expert Forum

Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.

Janeway Janeway

[Imported] ClearSCADA HOT Standby probelm after restoration of Crashed server.

>>Message imported from previous forum - Category:ClearSCADA Software<<
User: florian, originally posted: 2018-10-24 17:50:41 Id:187
This is a re-posting from the obsoleted (October 2018) "Schneider Electric Telemetry & SCADA" forum.


I have faced an issue with HOT standby server with ClearSCADA 2013 R1
Last week we have faced problem with server HDD crashed, we are restore server and ClearSCADA re-setup done as well as License restoration is also done. But after configration HOT stand by configuration it's shown Synchronizing since 8-Hour but it's ot changed to standby mode.
Please refer attached snap for the same._**

![]((see attachments below) 9y/jkdfch2cd96a.jpg "")


I've seen cases where it has taken a long time to synchronise ClearSCADA 2013 when the hot standby pair hasn't been swapped in a long time. Never that long, but a big database and a slow network connection could cause it to take any amount of time.

In ther server status tool it gives information on the progress of the synchronisation; I would have a look there to see whether it is getting anywhere.

It is also worth starting a wireshark log to see if the two servers are talking to each other corretly. I've seen firewall issues block some traffic and prevent the servers from completely synchronising.

Then there is the database logs. I would open the ones on the standby server and see if that has any hints.


There are a significant number of improvements in synchronisation in more recent versions of ClearSCADA also, in particular around the 2015R2 releases.

Upgrading versions of ClearSCADA is generally a very straight forward process, although it is non-reversible (once the DB has been upgraded, you can't run it on an older release, so you should retain an offline backup just prior to upgrade).

You should confirm that the appropriate firewall ports are open, and that there is no significant impediment to high speed network transfer (firewall Deep Packet Inspection can often burden down high speed transfers, so ideally you'd not be performing this activity on the synchronisation traffic).

If it is taking a very long time, then you can manually copy across the most recent database backup, including historical data. ClearSCADA can be smart about only synchronising files which are out of date (or not available on the Standby) which can speed up the online synchronisation process.


Please suggest which ports are need to be open from firewall_**


By default, TCP 5481, both directions

Server Standby - Links on the main server for how far through the sync things are and if there are any errors.


The list of Server/Client ports can be found here

As Adam has said, TCP 5481 deals with the default one. If you have changed the default port then this will need to be different also.


No there is a same default 5481 port is configure for HOT-Standby configuration_**


Has it synchronised yet?

It sounds like the amount of data that you're attempting to send during the synchronisation process is too much for your network to appropriately handle.

Options are:
1. Reduce the amount of data you store (you should have appropriate settings for historical compression, event and journal logging, alarm summary and configuration change retention)
2. Speed up the network between the two servers attempting to synchronise
3. Perform an out of band transfer of as much data as possible between the two servers before starting the secondary up and relying on the network to synch the remainder.


Thanks a lot for your support
Actual problem was found configuaratin of the server.
there is problem with changed storage locatin of thr program data._**

Attached file: (editor/9y/jkdfch2cd96a.jpg), Error7.jpg File size: 1909