ClearScada 2013 Download

[Anonymous user]

Recently due to Covid and other issues, our Clear Scada server running 2013r1.1 has been misplaced and (in all likelihood) destroyed (during an operational slowdown where the Scada was offline and shutdown and then some flood damage to the office)

I have a full drive backup including the ClearScada folders, but I have realised as the databases were not backed up individually, that I cannot migrate the system to a newer version of ClearScada, by simply downloading the oldest version available here

Would you happen to have a link for me download and run ClearScada 2013r1.1 so I can properly backup the databases and then we can request an upgraded licence/dongle when we re-instate the machine with a newer version of ClearScada or any way/method or otherwise to migrate this setup

i have trued migrating folders from drive backup, but the newer versions of CS dont appear to recognise them or identify them for viewing

Many Thanks

[sbeadle]

Try: https://schneider-electric.box.com/shared/static/48v02b4e93b6df2bt75m.zip

Please check exact build number in this zip vs your expected version.

[AndrewScott]

---

@Anonymous user wrote:

I have tried migrating folders from drive backup, but the newer versions of CS don't appear to recognise them or identify them for viewing.

It sounds like the database location settings haven't been configured correctly to point at the folders / filenames from the backup:

https://tprojects.schneider-electric.com/GeoSCADAHelp/Geo%20SCADA%202020/Default.htm#ServerAdministrationGuide/LocationsoftheDatabaseFolders.htm 

Any newer version of ClearSCADA can load a database from an older version. The only thing that might have changed is the default location of the database folders:

https://tprojects.schneider-electric.com/GeoSCADAHelp/Geo%20SCADA%202020/Default.htm#SystemInstallationGuide/Windows64BitFileLocations.htm 

[BevanWeiss]

It's also possible that the database was still configured for SCX filenames.  I've had a client in this situation before.

It was a relatively simple fix, just the configured paths needed to be adjusted to point to the base filename, I forget the exact names, but it was pretty obvious when looking in the registry location settings vs the file explorer extraction of the database files.