{"id":1376,"date":"2016-10-10T02:03:14","date_gmt":"2016-10-10T02:03:14","guid":{"rendered":"https:\/\/wireless-telemetry.com\/blog\/?p=1376"},"modified":"2016-10-10T02:03:14","modified_gmt":"2016-10-10T02:03:14","slug":"increased-scada-system-robustness-with-a-redundant-server","status":"publish","type":"post","link":"https:\/\/wireless-telemetry.com\/blog\/?p=1376","title":{"rendered":"Increased SCADA System Reliability with a Redundant Server"},"content":{"rendered":"
\"admin\"

Jim Mimlitz, NRI<\/p><\/div>\n

The SCADA Server is a vital component of the Water Utility \u2013 providing 24×365 critical services in the areas of realtime monitoring, historical trending, alarming, remote access, and supervisory control.<\/p>\n

It is noteworthy that Navionics Research\u2019s SCADA Server design is not based upon a master\/slave architecture. Therefore a loss of the Server will not cause a loss of automatic control operations throughout the filtration plants, pumping stations, water towers, and other sites. However, if the SCADA Server were to suffer a catastrophic failure, the Water Utility would need to resort to human oversight in order to maintain equivalent vigilance over the system\u2019s operation.<\/p>\n

\"in_case_of_emergency_break_glass\"<\/a><\/p>\n

For large Water Utilities, human oversight would generally be very difficult; as the number of sites that require monitoring \u2013 and the distance between them \u2013 could be substantial. A SCADA Server provides monitoring and alarming around the clock; and therefore the diversion of personnel from their normal duties and the extra overtime work to provide equivalent oversight would be costly to the District, as well.<\/p>\n

In order to minimize the negative effects of a catastrophic failure to a SCADA Server, Navionics Research recommends that large Water Utilities purchase and store a Redundant, Cold-Swappable SCADA Server<\/strong> which would be ready for quick deployment in case of failure of the primary SCADA Server.<\/p>\n

Preparation.<\/strong> The Redundant SCADA Server should be thoroughly\u00a0prepared in advance so that the switchover can be performed quickly and easily<\/strong>. \u00a0The procedure should basically\u00a0consist of switching over the signal and power cables from the Primary Server to the Redundant Server.<\/p>\n

\"Primary

Primary SCADA Server, Alongside Redundant\/Cold-Swappable SCADA Server.<\/strong><\/p><\/div>\n

 <\/p>\n

Hot-Swappable Versus Cold-Swappable:<\/strong> A hot-swappable redundant server refers to an extra server that is always powered-up and automatically activates if the primary server is lost for any reason. A cold-swappable redundant server refers to an extra server (disconnected from power and stored in a safe location) that requires manual installation by Water Utility personnel. Because certain conditions that could cause loss of the primary Server may also simultaneously damage the redundant hot-swappable Server (e.g. power surge), we recommend a cold-swappable Redundant Server.<\/p>\n

Navionics Research has deployed redundant SCADA Servers, and concurrently developed documentation that details the steps required to build, test, store, and deploy a redundant, cold-swappable SCADA Server. \u00a0The procedures are briefly summarized in this article:<\/p>\n

Construction and Configuration:<\/strong><\/h3>\n
    \n
  1. Operating System Installation. The Operating System (e.g. Microsoft Windows 7 Professional) should be installed onto the target machine.<\/li>\n
  2. Device Driver Installation. The motherboard Device Drivers should be installed onto the target machine.<\/li>\n
  3. Peripherals Installation. Extra peripheral devices should be installed onto the target machine. Examples include USB-Serial Adapters, Graphics Adapters, etc.<\/li>\n
  4. Operating System Updates. The Operating System should be updated to include all available patches. For example, Microsoft Windows Update.<\/li>\n
  5. User Account Setup. The required User Account(s) should be configured on the target machine.<\/li>\n
  6. SCADA Software Installation. The SCADA Software should be installed onto the target machine.<\/li>\n
  7. SCADA Software Configuration. The client-specific configuration files should be installed onto the target machine. These files should be identical to those installed on the primary machine.<\/li>\n
  8. Network Configuration. The client-specific network settings should be programmed into the target machine. These settings should be an exact match to the primary machine.<\/li>\n
  9. TeamViewer Installation and Configuration. TeamViewer should be installed and configured on the target machine. This will allow remote management of the system immediately after deployment.<\/li>\n<\/ol>\n

    Testing:<\/strong><\/h3>\n
      \n
    1. The Redundant SCADA Server should be placed into operation to verify that the redundant machine will provide identical service as the primary machine.<\/li>\n<\/ol>\n

      Storage:<\/strong><\/h3>\n
        \n
      1. The Redundant SCADA Server should be stored in a sealed plastic bag, along with all peripherals. The Operating System CD\/DVD and Device Driver CD\/DVD should be included.<\/li>\n<\/ol>\n

        Deployment Procedures:<\/strong><\/h3>\n
          \n
        1. The Redundant SCADA Server should be retrieved from its sealed plastic bag and placed alongside the damaged primary SCADA Server.<\/li>\n
        2. Power to the Damaged Primary Server should be turned OFF; and power to the Monitor(s) should also be turned OFF. The Redundant Server should not yet be powered up.<\/li>\n
        3. One-by-one, the following cables should be moved from the Primary Server to the Redundant Server:
          \n\u2022 Serial Cable(s)
          \n\u2022 Monitor Cable(s)
          \n\u2022 Network Cable
          \n\u2022 Mouse Cable (Unless Redundant Mouse provided)
          \n\u2022 Keyboard Cable (Unless Redundant Keyboard provided)
          \n\u2022 Power Cord<\/li>\n
        4. Turn ON power to the Display Monitors.<\/li>\n
        5. Turn ON power to the Redundant Server, and press the ON button on the front of the machine. Turn ON power to the Monitor(s).<\/li>\n
        6. The Redundant SCADA Server should boot up normally.<\/li>\n
        7. After the boot-up procedure completes, the monitor(s) should display the SCADA screens.<\/li>\n
        8. Initially, all remote sites should show communication talkback failures (flashing RED antenna icons). These should all clear out within about 15-20 minutes, as normal communications are re-established.<\/li>\n<\/ol>\n

          \"img_2577\"\u00a0\u00a0\"img_2579\"<\/p>\n

          Redundant SCADA Server with Connected Peripherals and Software DVD’s. \u00a0Sealed Plastic Bagging Added For Protection During Storage.<\/strong><\/h6>\n

           <\/p>\n

          Would a redundant SCADA Server benefit your Water Utility? \u00a0Give us a call; and we’ll be glad to discuss the details!<\/p>\n

          Telemetry, SCADA, & Controls Newsletter<\/strong><\/p>\n

          Was this article helpful?\u00a0 Would you be interested in receiving updates such as these in our occasional email-delivered newsletter?\u00a0 If so, here’s our sign-up page:<\/p>\n

          Subscribe to\u00a0Navionics Research’s\u00a0“Telemetry, SCADA, & Controls Newsletter”<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

          The SCADA Server is a vital component of the Water Utility \u2013 providing 24×365 critical services in the areas of realtime monitoring, historical trending, alarming, remote access, and supervisory control. It is noteworthy that Navionics Research\u2019s SCADA Server design is not based upon a master\/slave architecture. Therefore a loss of the Server will not cause …<\/span> Read More →<\/span><\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":1431,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6,7,10],"tags":[43,44,75,76,119,120,121],"class_list":["post-1376","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-disaster-recovery","category-general","category-interface","tag-cold-swap","tag-cold-swappable","tag-hot-swap","tag-hot-swappable","tag-redundancy","tag-redundant-scada-server","tag-redundant-server"],"_links":{"self":[{"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1376","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1376"}],"version-history":[{"count":0,"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/1376\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=\/"}],"wp:attachment":[{"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1376"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1376"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wireless-telemetry.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1376"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}