800xA History. Installation. Power and productivity for a better world TM. System Version 6.0

Transcription

1 800xA History Installation System Version 6.0 Power and productivity for a better world TM

2

3 800xA History Installation System Version 6.0

4 NOTICE This document contains information about one or more ABB products and may include a description of or a reference to one or more standards that may be generally relevant to the ABB products. The presence of any such description of a standard or reference to a standard is not a representation that all of the ABB products referenced in this document support all of the features of the described or referenced standard. In order to determine the specific features supported by a particular ABB product, the reader should consult the product specifications for the particular ABB product. ABB may have one or more patents or pending patent applications protecting the intellectual property in the ABB products described in this document. The information in this document is subject to change without notice and should not be construed as a commitment by ABB. ABB assumes no responsibility for any errors that may appear in this document. Products described or referenced in this document are designed to be connected, and to communicate information and data via a secure network. It is the sole responsibility of the system/product owner to provide and continuously ensure a secure connection between the product and the system network and/or any other networks that may be connected. The system/product owners must establish and maintain appropriate measures, including, but not limited to, the installation of firewalls, application of authentication measures, encryption of data, installation of antivirus programs, and so on, to protect the system, its products and networks, against security breaches, unauthorized access, interference, intrusion, leakage, and/or theft of data or information. ABB verifies the function of released products and updates. However system/product owners are ultimately responsible to ensure that any system update (including but not limited to code changes, configuration file changes, third-party software updates or patches, hardware change out, and so on) is compatible with the security measures implemented. The system/product owners must verify that the system and associated products function as expected in the environment they are deployed. In no event shall ABB be liable for direct, indirect, special, incidental or consequential damages of any nature or kind arising from the use of this document, nor shall ABB be liable for incidental or consequential damages arising from use of any software or hardware described in this document. This document and parts thereof must not be reproduced or copied without written permission from ABB, and the contents thereof must not be imparted to a third party nor used for any unauthorized purpose. The software or hardware described in this document is furnished under a license and may be used, copied, or disclosed only in accordance with the terms of such license. This product meets the requirements specified in EMC Directive 2004/108/EC and in Low Voltage Directive 2006/95/EC. TRADEMARKS All rights to copyrights, registered trademarks, and trademarks reside with their respective owners. Copyright by ABB. All rights reserved. Release: Document number: September PAA E

5 Table of Contents About This User Manual Document Conventions...9 Warning, Caution, Information, and Tip Icons...9 Terminology...10 Related Documentation...11 Section 1 - Introduction Overview...13 System Topology...14 Section 2 - Installation Overview New Installation...15 Node Installation...17 Software Installation...17 Section 3 - System Requirements and Prerequisites System Requirements...19 History Server - System Requirements...19 History Embedded Data Collector...22 Prerequisites...25 History Server...26 History Embedded Data Collector...26 Formatting Drives as 64K Blocks...26 Disabling Indexing for Database Drive PAA E 5

6 Table of Contents Section 4 - Automated System Installation Pre-requisites for Installation...27 Installation of 800xA Core Components using Node Preparation Tool...28 Installation of 800xA History Software using System Configuration Console...31 Adding the nodes...31 Assigning the System Functions and Node Functions to the Nodes...33 Standalone History Server...33 History Server High Availability Installation...37 Primary History Server...37 Secondary History Server...41 Primary Data Collector Node...45 Secondary Data Collector Node xA History Archive...50 Post Install Steps for the Automated System Installation...52 Section 5 - Installation Pre-Installation...53 Installing History Installer...53 Node Installation...54 Prerequisites...54 History Server Installation...56 History Server High Availability Installation...78 Software Installation Installing History Embedded Data Collector Post Installation Procedures Firewall Settings History Server History Embedded Data Collector Node Antivirus Exclusions IPSec Exemptions Section 6 - Uninstallation Uninstalling History Server PAA E

7 Table of Contents Uninstalling History Embedded Data Collector Section 7 - Upgrade 800xA History Server xA History Embedded Data Collectors Appendix A - Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) Appendix B - Adding High Availability Server Introduction Revision History Updates in Revision Index A Updates in Revision Index B Updates in Revision Index C Updates in Revision Index D Updates in Revision Index E Index 2PAA E 7

8 Table of Contents 8 2PAA E

9 About This User Manual Any security measures described in this User Manual, for example, for user access, password security, network security, firewalls, virus protection, etc., represent possible steps that a user may want to consider based on a risk assessment for a particular application and installation. This risk assessment, as well as the proper implementation, configuration, installation, operation, administration, and maintenance of all relevant security related equipment, software, and procedures, are the responsibility of the user. This user manual describes the installation of History components using the History Installer. It is intended for the application engineers/system administrators responsible for installing or configuring the History application. Document Conventions Microsoft Windows conventions are normally used for the standard presentation of material when entering text, key sequences, prompts, messages, menu items, screen elements, etc. Warning, Caution, Information, and Tip Icons This publication includes Warning, Caution, and Information where appropriate to point out safety related or other important information. It also includes Tip to point out useful hints to the reader. The corresponding symbols should be interpreted as follows: Electrical warning icon indicates the presence of a hazard which could result in electrical shock. 2PAA E 9

10 Terminology About This User Manual Terminology Warning icon indicates the presence of a hazard which could result in personal injury. Caution icon indicates important information or warning related to the concept discussed in the text. It might indicate the presence of a hazard which could result in corruption of software or damage to equipment/property. Information icon alerts the reader to pertinent facts and conditions. Tip icon indicates advice on, for example, how to design the project or how to use a certain function. Although Warning hazards are related to personal injury, and Caution hazards are associated with equipment or property damage, it should be understood that operation of damaged equipment could, under certain operational conditions, result in degraded process performance leading to personal injury or death. Therefore, fully comply with all Warning and Caution notices. This section includes a complete and comprehensive list of terms that apply to the History application. Terms that uniquely apply to this instruction are included in this section. Term/Acronym GUI MSI CLS Node Client Graphical User Interface Microsoft Installer Central Licensing System Description A computer communicating on a network, for example, the Internet, Plant, Control or I/O network. Each node typically has a unique node address with a format depending on the network it is connected to. Client is a part of the software that subscribes data from the server. 10 2PAA E

11 About This User Manual Related Documentation Term/Acronym Server Client/Server OPC DA OPC AE OPC HDA API DVD HDD A node that runs one or several Afw services. It is a part of the software that supplies data to a subscriber. A client/server network is used for communication between servers and between workplaces and servers. OPC Data Access OPC Alarm and Event OPC History Data Access Description Application Programming Interface Digital Versatile Disk. It is an optical disk storage media. Hard Disk Drive. It is a local online fixed storage drive composed on several magnetic disks. Related Documentation This section includes a complete list of all documents applicable to the History. Title Administration and Configuration Manual Description Describes the details for administrating and configuring History. For more information, refer 800xA History Administration and Configuration (2PAA107563*). 2PAA E 11

12 Related Documentation About This User Manual 12 2PAA E

13 Section 1 Introduction Overview This documentindicates software at the time of release. History Release Notes must be read and understood before performing automated installation, post installation or upgrade procedures. History Software Components: 1. History Server The History Server is the Main Historian Component which seamlessly stores real time-data (process values, events) from the control system and processes the data as per user requirement and makes it available for further analysis. This node should be the first node in the History components installation. This node is required to be installed in a fresh machine. The disk space requirement will depend on the tags on the system. For more information, refer Prerequisites section. Software component such as Data Collector needs History Server details for successful installation. For more information on installation refer Node Installation. 2. History Embedded Data Collector Node History Embedded Data Collector component is the interface between the control system and the History server. History Embedded Data Collector collects, stores, and buffers the data from control system and forwards it to the History Server. 3. History Installer History Installer provides a capability for performing automated installation of History software and its various components. 2PAA E 13

14 System Topology Section 1 Introduction System Topology The History solution consists of following: History Embedded Data Collectors History servers One History Server (either in Standalone or High-Availability) can support connectivity from maximum of 12 data collectors either in single or dual configuration. A History server combines the process information from all data collectors into the History database. History supports redundant (High Availability) configuration in History Servers. A dedicated 1 Gbps network (Consistency Control Network) connection is required in High Availability solutions to connect the redundant history servers for data synchronization. Typical scenarios for History Installation 1. Data collector with History Server Basic (Non-Redundant) 2. Redundant Data collector with History Server Basic (Non-Redundant) 3. Redundant History Server (High Availability) 14 2PAA E

15 Section 2 Installation Overview New Installation This section includes information for installing and setting up History using the History Installer. This document reflects History software at the time of release. The History Release Notes must be read and understood before performing any automated or manual installation, and post installation procedures. Consider the following before performing the procedures described in this document: Do not install any software until the system has been properly designed and configured for the software being installed. 2PAA E 15

16 New Installation Section 2 Installation Overview Figure 1. Graphical Overview of typical History Configuration The History Installer supports the following types of installation: Node Installation Software Installation Before installing ensure that the pre-installation procedures are accomplished. For more information, refer Pre-Installation section. 16 2PAA E

17 Section 2 Installation Overview Node Installation Node Installation The node installation involves the installation of History Server. The History Server is the Main Historian Component which seamlessly stores real time-data (Process values, Events) from the control system and processes the data as per user requirement and makes it available for further analysis. This node should be the first node in the History components installation. This node is required to be installed in a fresh machine. The disk space requirement will depend on the tags in the system. For more information, refer Table 1. Software component such as the History Embedded Data Collector requires History Server details for successful installation. For more information on Node Installation, refer, Node Installation. Software Installation The Software installation using History Installer includes the following: History Embedded Data Collector For more information about Software Installation, refer Software Installation. History Embedded Data Collector component is the interface between the control system and the History server. History Embedded Data Collector collects, stores, and buffers the data from control system and forwards it to the History Server. For more information on installing History Embedded Data Collector, refer Installing History Embedded Data Collector. 2PAA E 17

18 Software Installation Section 2 Installation Overview 18 2PAA E

19 Section 3 System Requirements and Prerequisites This section provides information about system requirements and prerequisites for installing History software. System Requirements The system requirements are listed in the subsequent topics. History Server - System Requirements Typical hardware requirements are described in the below tables. For actual hardware requirement, History log data storage & retention time refer 800xA History disk size estimation sheet available in the ABB Library. Table 1 describes the system requirements for History Server: Table 1. History Server System Requirements History Server (Real Time Database) System Requirements Drive C Footprint (OS and Softwares) Drive D Footprint Real Time Database (64 Block) Drive F Footprint On-line Backup Memory (RAM) Footprint System Tags Supported Disk Size in GB Drive Size in GB Drive size in GB Size in GB Small < PAA E 19

20 History Server - System Requirements Section 3 System Requirements and Prerequisites Table 1. History Server System Requirements (Continued) History Server (Real Time Database) System Requirements Medium Large 5000 to to Enterprise > Specific requirements for the History Server node are given in Table 2. Table 2. Recommended hardware for 800xA History Server Item Size Specifications Processor Dual-socket (4 pcs) Intel Xeon 5600/6500/7500 Series or newer (At minimum Quad-core CPU is required) Memory Minimum 8 Gigabytes Medium Large 32 Gigabytes 32+ Gigabytes Graphics Basic 2D performance of any integral Graphics Adapter is adequate Display Minimum 20" WXGA 1280x800 pixels (maintenance only) Recommended 24" WUXGA 1920x1200 pixels [HDD 1] OS + Applications Minimum Medium/Large Performance 100 Gigabytes SATA 150 Gigabytes SAS, mirrored RAID Gigabytes SSD [SATA] 20 2PAA E

21 Section 3 System Requirements and Prerequisites History Server - System Requirements Table 2. Recommended hardware for 800xA History Server (Continued) Item Size Specifications [HDD 2] History Database Minimum Medium Large Enterprise Performance 150 Gigabytes SATA 600 Gigabytes SAS, min. 4 physical drive spindles, mirrored RAID Terabytes SAS, min. 4 physical drive spindles, mirrored RAID-10 2 Terabytes SAS, min. 6 physical drive spindles, mirrored RAID-10, with HotSpare 500 Gigabytes SSD [PCI-E] [HDD 3] On-line backup Minimum 500 Gigabytes SATA Recommended 1000 Gigabytes SAS, fail-safe RAID-5 Enterprise 1000 Gigabytes SAS, fail-safe RAID-5 [optional] Spare parts Recommended Redundant Power Supply Recommended Redundant System Cooling Fans Recommended Redundant Network Adapters [optional] HW Warranty Extension Recommended 5 Years, 24/7, 4 hr response [operations critical] Networks Connectivity 1. Usage Mandatory Enterprise wide connectivity (to ERP systems) 2PAA E 21

22 History Embedded Data Collector Section 3 System Requirements and Prerequisites Table 2. Recommended hardware for 800xA History Server (Continued) Item Size Specifications 1. Protocols TCP/IP 2. Usage Mandatory Plant wide connectivity (to the Data Collectors) 2. Protocols TCP/IP + UDP + IP Multicast 3. Usage [optional] SAN Backup connectivity 3. Protocols TPC/IP 4. Usage [optional] Lights-Out Management 4. Protocols TPC/IP History Embedded Data Collector Table 3 describes the system requirements for the data collector. Table 3. Data Collector System Requirements Data Collector System Requirements Drive C Footprint (OS and Softwares) Drive D Footprint Real Time Database (64k Block) Drive F Footprint On-line Backup Memory (RAM) Footprint System Tags Supported Disk Size in GB Drive Size in GB Drive size in GB Size in GB Small < Maximum Supported < PAA E

23 Section 3 System Requirements and Prerequisites History Embedded Data Collector Specific requirements for the data collector node are given in Table 4. Table 4. Recommended hardware for Data Collector installation Item Size Specifications Processor 1st choice Intel Xeon 3000/5600 Series or newer 2nd choice Intel Core i3/i5/i7 ((Recommended to use Quad Core CPU) Memory Minimum 4 Gigabytes Graphics Basic 2D performance of any integral Graphics Adapter is adequate Display Minimum 20" WXGA 1280x800 pixels (maintenance only) Recommended 24" WUXGA 1920x1200 pixels [HDD 1] OS + Applications + Data Collector Minimum Recommended Performance 100 Gigabytes SATA 300 Gigabytes SAS, mirrored RAID Gigabytes SSD [PCI-E] [optional] [HDD 2] On-line backup Minimum Recommended 300 Gigabytes SATA 500 Gigabytes SATA [optional] Spare parts Recommended Redundant Power Supply Recommended Recommended Redundant System Cooling Fans Redundant Network Adapters 2PAA E 23

24 History Embedded Data Collector Section 3 System Requirements and Prerequisites Table 4. Recommended hardware for Data Collector installation (Continued) Item Size Specifications [optional] HW Warranty Extension Recommended 5 Years, 24/7, 4 hr response [operations critical] Networks Connectivity 1. Usage Mandatory Plant wide connectivity (to 800xA History Server) 1. Protocols TCP/IP + UDP + IP Multicast 2. Usage Mandatory Automation system connectivity (to 800xA system) 2. Protocols TPC/IP, RNRP [redundant] 3. Usage [optional] Automation system connectivity (to 800xA system) 3. Protocols TPC/IP, RNRP [redundant] 4. Usage [optional] SAN Backup connectivity 4. Protocols TPC/IP 5. Usage [optional] Lights-Out Management 5. Protocols TPC/IP 24 2PAA E

25 Section 3 System Requirements and Prerequisites Prerequisites Prerequisites This section includes the prerequisite software required for the installation of: History Server History Embedded Data Collector The user performing the procedure in this section must be proficient in using the Windows Operating System. This section excludes the detailed procedures on how to perform the installation of each prerequisite. The user should refer Microsoft documentation and online help for information on accurately making the setting. Redundant network configuration between 800xA History Embedded Data Collector and 800xA History Server is currently not supported. Only one network connection can be used for communication between them. For Standalone History Server, it is required to have 1Gbps network for communication between 800xA History Embedded Data Collectors and 800xA History Server. For High Availability History Server configuration, NLB network will be used for data communication between 800xA History Servers and 800xA History Embedded Data Collectors. It is required to have 1Gbps network for NLB. For High Availability History Server configuration, data synchronization between High Availability History Servers, require to have separate and dedicated 1Gbps network termed as Consistency Controller network. The History Installer automatically performs the Regional Settings during the Windows Configuration. Before start of installation, make sure to Disable Antivirus and Firewall. The same can be enabled after completion of post-installation. 2PAA E 25

26 History Server Section 3 System Requirements and Prerequisites History Server Prerequisites for installing History Server is as follows: Server Operating system MS Office Refer to System 800xA Third Party Software (3BUA000500*) for information related to supported operating systems. Log in as local user with administrator privileges. History Embedded Data Collector Prerequisites for installing History Embedded Data Collector is as follows: Server Operating system MS Office Refer to System 800xA Third Party Software (3BUA000500*) for information related to supported operating systems. Formatting Drives as 64K Blocks When a drive is selected as database drive, remember that the recommended cluster size (Allocation unit size) of the drive should be 64KB. Format the selected database drive with cluster size of 64KB before installation. If the software components are installed in the same connectivity server or application server, add an extra HDD. Format the added HDD as 64K blocks. For more information about formatting a drive with cluster size of 64KB, refer the Microsoft documentation. Disabling Indexing for Database Drive It is recommended that the database drive should not have indexing allowed. For more information about disabling indexing, refer Microsoft documentation. 26 2PAA E

27 Section 4 Automated System Installation The section provides the procedure for Automated System Installation of 800xA History. Pre-requisites for Installation In Workgroup Installation, Users and Groups must be created manually on all the planned nodes. For more information on creating users refer System 800xA Installation and Upgrade Getting Started (2PAA111708*) manual. In Domain Installation user has to create the Domain Controller first. For information how to create domain controller refer System 800xA Installation and Upgrade Getting Started (2PAA111708*) manual. The database drives must be formatted with 64bit KB Size. Compress the drive for saving disk space option must be enabled for the History database drives. Configure the Network adapters with planned IP Address. Rename the History Nodes as per the planned network configurations. For High Availability installation NLB must be configured only on History Servers. For more information refer Network Load Balancing (NLB). UAC must be enabled and set to default Windows OS configuration. For further more information on pre-requisites please refer System 800xA Installation and Upgrade Getting Started (2PAA111708*) manual. 2PAA E 27

28 Installation of 800xA Core Components using Node Preparation Tool Section 4 Automated System Installation of 800xA Core Components using Node Preparation Tool 1. Run the NPT tool using setup.exe from the 800xA media. 2. Provide the 800xA Service user account credentials as shown in the Figure xA History Server / Data Collector installation Support only the following characters in the user account password, make sure the password meets the requirement as described below: Installation of 800xA History services may fail if the password of the installation account contains certain special characters other than the one described below Configure the password of the installation account with the following supported characters Supported Characters: Alphabets = A- Z, a - z Numeric = 0-9 Special Characters = #, *, -, +, _ 28 2PAA E

29 Section 4 Automated System Installation Installation of 800xA Core Components using Node Figure 2. Node Preparation Tool and User Account Credentials 3. Select the option 800xA History under the Installation Type. Refer Figure 3. Perform Step 3 only on the History Servers and DCN nodes. 2PAA E 29

30 Installation of 800xA Core Components using Node Preparation Tool Section 4 Automated System Figure 3. Selecting 800xA History and Data Collector Nodes 4. Click OK. Wait for the installation of core components to complete. Perform Step 1 to Step 4 on all the planned nodes. 30 2PAA E

31 Section 4 Automated System Installation Installation of 800xA History Software using System Installation of 800xA History Software using System Configuration Console Adding the nodes 1. On planned Aspect Server node, click Start and then type System Configuration Console. 2. Click on System Setup and then click Configure System. This configures the Aspect Server. 3. Under system Functions tab in SCC tool, click on the Edit functions and select the 800xA History Functions as shown in Figure 4 and click OK. Figure 4. SCCB Tool - Edit functions 2PAA E 31

32 Adding the nodes Section 4 Automated System Installation 4. Click on Nodes Configuration Tab and Click Add Node button as shown in Figure 5. Figure 5. Nodes Configuration 5. Provide the Node name and select Client or Server as applicable. Add all the nodes by performing Step 4 and Step 5. Do not Add History Secondary (Replica) node at this step. 32 2PAA E

33 Section 4 Automated System Installation Assigning the System Functions and Node Functions to Assigning the System Functions and Node Functions to the Nodes Standalone History Server 1. Select the Standalone History server node and click on Edit Node Functions as shown in Figure 6. Figure 6. Standalone History Node - Edit Function 2PAA E 33

34 Standalone History Server Section 4 Automated System Installation 2. Select the option 800xA History Server Non-Redundant and click OK as shown in Figure 7. Figure xA History Server Non Redundant selection 34 2PAA E

35 Section 4 Automated System Installation Standalone History Server 3. Click on the Edit button under Node Content column as shown in Figure 8. Figure 8. Node Content - Edit 2PAA E 35

36 Standalone History Server Section 4 Automated System Installation 4. Assign the 800xA History Server Properties as shown in the Figure 9. Figure xA History Server Properties Select the corresponding Time zone from the drop down menu. Select the database size High, Medium, Low as per the requirement. Select the Database and Backup drive planned for the History Standalone Server. Click Ok. 36 2PAA E

37 Section 4 Automated System Installation History Server High Availability Installation History Server High Availability Installation Primary History Server First install Primary History Server, perform the Online Copy in the Primary History Server then Install the Secondary History Server. Do not deploy both primary & secondary History Server together. If deployed Secondary server installation will fail. 1. Select the Primary History Server node and click on Edit node functions as shown in Figure Select the option 800xA History Server Primary and click OK as shown in Figure 10. 2PAA E 37

38 Primary History Server Section 4 Automated System Installation Figure xA History First Server selection 38 2PAA E

39 Section 4 Automated System Installation Primary History Server 3. Click on the Edit button under Node Content column as shown in Figure 11. Figure xA History First Server Edit 2PAA E 39

40 Primary History Server Section 4 Automated System Installation 4. Assign the 800xA History Server Properties as shown in the Figure 12. Figure xA History Server Properties Select the corresponding Time zone from the drop down menu. Provide the Common System name in case of High Availability as configured in Prerequisites. 40 2PAA E

41 Section 4 Automated System Installation Secondary History Server Provide the IP Address of the History First Server node dedicated for High Availability. Select the database size High, Medium, Low as per the requirement. Select the Database Drive planned for the History First Server. Select the Backup Drive planned for the History First Server. Click OK. Secondary History Server 1. Before installing the Secondary History server, run the online copy of the Primary History Server. Preparing online backup of the first node Perform the Online Backup of the First Node of the History Server. In the First node of the History Server, run the following command from Command prompt: %app_root%\bin\app_backuptool /d Wait for the command to complete and confirm that online copy is successfully completed. 2PAA E 41

42 Secondary History Server Section 4 Automated System Installation 2. After the Deployment is completed successfully for the planned nodes in the system, add the Secondary History server as shown in Figure 13 and click on the Edit Functions. Figure 13. Adding of Secondary History server 42 2PAA E

43 Section 4 Automated System Installation Secondary History Server 3. Under Edit node functions select the 800xA History Server Secondary and click OK as shown in Figure 14. Figure 14. Secondary History server Edit 4. Click on Edit button under Node content field of SCC. Refer Figure 13. 2PAA E 43

44 Secondary History Server Section 4 Automated System Installation 5. Assign the properties for Secondary History Server as shown in Figure 15. Figure 15. Secondary History Server Properties Select the corresponding Time zone from the drop down menu. Provide the Consistency Controller Network IP of Primary History Server. Select the same Database and Backup Drive letter as selected for the Primary History Server. 44 2PAA E

45 Section 4 Automated System Installation Primary Data Collector Node Primary Data Collector Node 1. Select the Primary DCN node and click on Edit node functions as shown in Figure 16. Figure 16. Primary DCN node - Edit node functions selection 2PAA E 45

46 Primary Data Collector Node Section 4 Automated System Installation 2. Select the Node Function 800xA History Data Collector and Basic History Services as shown in Figure 17 and click OK. Figure 17. Primary DCN node - Edit node functions 46 2PAA E

47 Section 4 Automated System Installation Primary Data Collector Node 3. Click on Edit button under Node content column as shown in Figure 18. Figure xA History Data Collector - Edit 2PAA E 47

48 Primary Data Collector Node Section 4 Automated System Installation 4. Assign the properties of History Data Collector as shown in Figure 19. Figure 19. History Data Collector Properties Modify the History Services Service Group and Service Providers name as required. 48 2PAA E

49 Section 4 Automated System Installation Secondary Data Collector Node Select the corresponding Time zone from the drop down menu. Select the Database Drive and Backup Drive from the drop down menu. Provide the History Server name in case of Standalone History Server. In case of HA provide the Common NLB name configured as in Prerequisites. Provide the IP Address of the History Server Node in case of Standalone. In case of HA configuration provide the Common NLB IP address configured as in Prerequisites. Click OK. Secondary Data Collector Node For redundant DCN configuration, user has to manually provide the History Server name and Database Drive selection in the secondary DCN node after performing the Make redundant in SCC. 1. Add the Secondary DCN node as shown in Figure 20. Figure 20. Secondary DCN Node 2PAA E 49

50 800xA History Archive Section 4 Automated System Installation 2. Select the Primary DCN node and click on Make Redundant as shown in Figure Select the Redundant DCN node from the drop down menu as shown in Figure 21. Figure 21. Redundant DCN node selection 4. Select the Node functions 800xA History Data collector and Basic History Services and click OK. Refer Figure Select the Secondary DCN node and click on Edit button under Node content column as shown in Figure Provide the History Server name, IP Address and Database / Backup Drives as in Primary DCN node. Click OK. 800xA History Archive 1. Add the Node planned for 800xA History Archive. 2. Select the Node created in Step PAA E

51 Section 4 Automated System Installation 800xA History Archive 3. Click on the Edit Node functions options. Select the 800xA History Archive and click OK as shown in Figure xA History Archive role should be deployed / installed through system installer only when System function and Node role function both are selected. Make sure that the ABB InformIT History.msi software is not yet installed on the planned 800xA History Archive node before the 800xA History Archive is deployed. Figure xA History Archive functions 2PAA E 51

52 Post Install Steps for the Automated System Installation Section 4 Automated System Installation 5. Click on the Edit properties option and provide the 800XAINSTALLER user name as shown in Figure 23 and click OK. Figure xA History Archive Edit Now configure the other DCN nodes as planned and deploy the configuration. Post Install Steps for the Automated System Installation RTDB Control Panel will be created only for 800xAService Account which will install the database components, even if the interactive user is logged in as 800xAInstaller. 52 2PAA E

53 Section 5 Installation Pre-Installation The History Installer provides a wizard based automated system installation. The History Installer also enables the standalone software installation on an existing node. The installation types included in the History Installer are: 1. Node Installation 2. Software Installation This section includes the installation of History Installer, History Server, and History Embedded Data Collector. Before proceeding with the installation of History server and components: Disable indexing for database drive. It is recommended that the database drive should not have indexing allowed. For more information about disabling indexing, refer Microsoft documentation. Installing History Installer Execute the following steps to install the 800xA History Installer from the 800xA Media/Applications/History/History Installer. Make sure to run History Installer as Run as administrator. Ensure that the media should be available in the local system and not from a mapped drive for installing the software components. However, to make a local copy of media contents for installing, ensure that the absolute path should be minimum. For example, if the contents are copied to D:\, then make a copy in D:\DVD, instead of D:\XXX\YYY\ZZZ\...\DVD. 2PAA E 53

54 Node Installation Section 5 Installation Node Installation If UAC is enabled Click Yes in the User Account Control dialog that appears to allow the program to run. Prerequisites Figure 24. History Installer Screen The Node installation includes the installation of History Server. Installing History Server will install the real time database by default. Following are the prerequisites that must be verified before the start of History Server and History Server High Availability - First and Second nodes. Common 1. Preferred Hardware Configuration with HDD is available. 2. Recommended RAM size is available. 3. Dedicated Network adapters available. 54 2PAA E

55 Section 5 Installation Prerequisites 4. If any network adapter has DHCP configured, disable the adapter during the installation period. Enable the adapter after the installation is completed. 5. Minimum software prerequisite is available before installation is started. 6. ICMP port enabled between DCN and History Server (preferable). 7. DataBase Disk Drive must be formatted with 64K Block Size. 8. Indexing must be disabled for the Disk Drives. 9. Installation must be performed with the user with Administrative privileges. 10. Windows Time Zone must be properly set before starting of installation. 11. Installation of the 800xA History Main Server / 800xA History Data Collector node must be performed only from the Physical DVD media or when the build copied locally. Installation of 800xA History software from the Mapped network or shared drive is not supported. Specific for History Server High Availability - First and Second nodes Apart from the above listed prerequisites there are certain specific requirements to be verified for High Availability servers. First Node 1. Windows Host file must be updated with NLB IPs (refer Configuring Network Load Balancing (NLB)). 2. Time synchronization must be performed between the redundant servers. It is mandatory that High Availability Servers must be synchronized with less than second difference. So it is advisable to use common time source. 3. NLB Settings must be performed (refer Configuring Network Load Balancing (NLB)). Replica Node 1. It is mandatory to have online copy of the first node ready before starting the installation (refer Preparing online backup of the first node). 2PAA E 55

56 History Server Installation Section 5 Installation History Server Installation Installing History Server Before installing ensure that the pre-installation procedures are accomplished. For more information, refer Pre-Installation section. Execute the following steps to install History Server through Node Installation. 1. Press Windows Key > click Start Up Arrow > Launch History Installer. Figure 25 Figure 25. Launching History Installer 56 2PAA E

57 Section 5 Installation History Server Installation 2. The welcome screen appears as shown in Figure 26. Figure 26. Welcome Screen 2PAA E 57

58 History Server Installation Section 5 Installation If the previous installation was incomplete, the History Installer wizard as shown in Figure 27 appears. Figure 27. History Installer Wizard This wizard inludes the following options: Continue with the Previous Installation - Select this option to restore the installation from the point where the previous installation was cancelled. Start a Fresh Installation - Select this option to start the fresh installation. 3. Select one of the above options and click Next to continue with the installation. 4. Click Next in the Welcome screen to view Analyze wizard. The Analyze wizard performs the media verification. If the media folder structure does not include any folder, sub-folder, or a file, an appropriate error message is displayed for locating the missing file or folder. The installation proceeds only after locating files or folders manually. 58 2PAA E

59 Section 5 Installation History Server Installation 5. In the Install Option wizard as shown in Figure 28, select Fresh Installation Install Option wizard appears only when the user attempts to re-install the application using History Installer. If the user is performing the installation for the first time, then they are directed to Step 6. Figure 28. Install Option wizard 2PAA E 59

60 History Server Installation Section 5 Installation 6. In Install Type Selection wizard as shown in Figure 29, select the type of installation. Figure 29. Installation Type Selection wizard a. Select Node Installation option. b. Select History Server from the drop-down list. 7. Click Next to view System Settings wizard as shown in Figure 30 and Figure PAA E

61 Section 5 Installation History Server Installation Figure 30. System Settings Wizard - Join this node to Workgroup is selected 2PAA E 61

62 History Server Installation Section 5 Installation Figure 31. System Settings Wizard - Join this node to an existing Domain is selected 8. Do the following in the System Settings wizard: a. In the System Setting section, enter History Server name in the Computer Name field. A maximum of 15 characters are allowed in the Computer Name field. The computer will be renamed to the name provided in Computer Name field. Select the Use current computer name check box to use the current computer name. b. In the Windows Workgroup / Domain Settings section, do the following: Click Join this node to a Workgroup as shown in Figure 30, if the node should belong to a Workgroup. The users displayed in the Input wizard are automatically created. The complete Workgroup name should be specified in Workgroup/Domain name field. By default, the Workgroup name is 62 2PAA E

63 Section 5 Installation History Server Installation Workgroup and continue with Step 9. Select Use current Workgroup name check box to use the current workgroup name and the workgroup name will be auto-populated in the Workgroup/Domain field. If the entered Workgroup name does not exist, an error message stating Invalid Workgroup Name appears. Click Join this node to an existing domain as shown in Figure 31, to install History under existing domain and provide the domain name in Workgroup/Domain name field and continue with Step 9. If the machine is already added to a domain, then click Join this node to an existing Domain and select Use current Domain check box and the domain name will be autopopulated in the Workgroup/Domain field. If History Server is installed in a Domain Environment, verify the following: Verify that IPv6 in Network Adapters are disabled. Verify that domain user used for installation is existing in Domain Controller. Verify that the domain is in the same network as the History Server. 2PAA E 63

64 History Server Installation Section 5 Installation 9. Click Next to view Local Region Settings wizard as shown in Figure 32. Figure 32. Local Region Settings wizard a. Select the appropriate time zone in the Time Zone Settings drop-down list. 10. Click Next to view System Network Settings wizard. Figure 33 appears if you have selected Join this node to a Workgroup in Step PAA E

65 Section 5 Installation History Server Installation Figure 34 appears if you have selected Join this node to an existing domain in Step 7. Figure 33. System Network Settings wizard 2PAA E 65

66 History Server Installation Section 5 Installation Figure 34. System Network Settings wizard a. Select the appropriate Network Adapter check box to be configured. To use a different IP address, click the IP Address next to the applicable adapter and then type the appropriate IP address. The entered IP address will be set by the History Installer during the installation process. The network adapter selected here will be used for data communication between History Server and History Embedded Data Collector. b. Enter the default gateway in the Default Gateway column. To ignore the default gateway mentioned, select Ignore Default Gateway IP check box. 66 2PAA E

67 Section 5 Installation History Server Installation 11. Click Next to view User Account Settings wizard to specify the System Users details as shown in Figure 35. Figure 35. User Account Settings Wizard 12. In the User Account Settings wizard: a. In the Database user account section, enter the user name in the Username field. Enter the password in the Password field and confirm by re-typing the password again in the Confirm password field. b. In the Service user account section, enter the user name in the Username field. c. Enter the password in the Password field and then confirm by re-typing the same password in Confirm password field. If the Use the Database user account for Service user account check box is selected, the entered Database account user is used for Service account also. 2PAA E 67

68 History Server Installation Section 5 Installation If an existing user account other than the default user account is used, make sure that the user account has administrator privileges. d. If History Server is installed in Domain Environment, then follow the below steps, else continue with Step h. e. It is required to provide the User credentials which is already defined in Domain Controller as shown in Figure 36. Figure 36. User Account Settings f. If the machine is already added to Domain, then ensure that the user name provided is part of local Administrators group. g. When you click Next in User Account Settings dialog, a pop-up appears as shown in Figure 37 or Figure PAA E

69 Section 5 Installation History Server Installation In case of Figure 37, enter the local administrator user name to automatically login to the machine after a restart. Figure 37. Logon Dialog - Administrator In case of Figure 38, where machine is already added to domain, enter domain user name that is added to local administrators group to automatically login to the machine after a restart. Figure 38. Logon Dialog - Installer 2PAA E 69

70 History Server Installation Section 5 Installation h. Click OK to view History Database Settings wizard as shown in Figure 39. This wizard allows the user to select the database installation type. Choose Standalone. Figure 39. Inputs wizard with Standalone selected 13. Click Next to view History Database Settings wizard as shown in Figure 40, which allows the user to select the resource allocation for the database. Make selection based on the following: For minimal system resource use, select LOW. If the computer is used also for some other purposes, select MEDIUM. If the computer is dedicated for the use for History, select HIGH. 70 2PAA E

71 Section 5 Installation History Server Installation Figure 40. History Database Settings - Specifying database size 2PAA E 71

72 History Server Installation Section 5 Installation 14. Select the appropriate option and click Next to view History Database Settings wizard as shown in Figure 41. This wizard allows the user to select the applicable database size for the Real Time Database. Figure 41. History Database Settings - Database and Backup Drive 15. In the History Database Settings wizard: a. Select the appropriate drive option from Database Drive drop-down list to store the database. Make sure that the selected database drive has been initialized using 64K block size. If the selected drive does not have the recommended cluster size (Allocation unit size), an error message indicating the same appears. For more information about formatting a drive in 64K block, refer Microsoft documentation. b. Select the appropriate drive option from Backup Drive drop-down list. The selected drive will be a backup for the database. 72 2PAA E

73 Section 5 Installation History Server Installation 16. Click Next to view History Database Settings wizard, which confirms the 64K block format on the selected database drive. 17. Click Next to view Software License wizard as shown in Figure 42. Figure 42. Software License wizard 2PAA E 73

74 History Server Installation Section 5 Installation 18. Accept the license agreement and click Next to view Confirm Setup wizard as shown in Figure 43. Figure 43. Confirm Setup wizard 19. Click Next to perform Windows Configuration and Product Setup automatically. After the configuration, and product installation is completed, a 74 2PAA E

75 Section 5 Installation History Server Installation Shutdown warning dialog appears as shown in Figure 44. Figure 44. Shutdown Warning 20. In the Shutdown warning dialog, click Restart Now to restart the computer immediately. Alternatively, click Wait to view Shutdown warning dialog as shown in Figure 44. Figure 45. Shutdown Warning Clicking Restart Now in the Shutdown warning dialog as shown in Figure 45 restarts the computer immediately. 21. After automatic restart, Product Setup wizard appears as shown in Figure 46. A list of components will be installed automatically. After all the required components are installed, a dialog box appears to restart the system. 2PAA E 75

76 History Server Installation Section 5 Installation Figure 46. Product Setup wizard If Windows logged in as a user, user credentials will be changed automatically by History Installer. 22. Click Restart Now to restart the system immediately. After restarting, the installation will continue from this step automatically. 23. After restart is completed, Firewall Exceptions wizard appears as shown in Figure 47, which indicates the progress of the firewall configuration. 76 2PAA E

77 Section 5 Installation History Server Installation Figure 47. Firewall Exceptions wizard. 2PAA E 77

78 History Server High Availability Installation Section 5 Installation 24. Click Next to view Finish wizard as shown in Figure 48, which indicates the completion of History Server - Standalone installation. Figure 48. Finish wizard 25. Click Finish to complete the installation of History Server and also to close the History Installer wizard. History Server High Availability Installation Before you begin with the installation make sure the prerequisites are verified. Refer Specific for History Server High Availability - First and Second nodes on page 55. Installing History Server High Availability - First Node Before installing ensure that the pre-installation procedures are accomplished. For more information, refer Pre-Installation section. Refer Configuring Network Load Balancing (NLB) to configure NLB network before starting the installation. 78 2PAA E

79 Section 5 Installation History Server High Availability Installation 1. Press Windows Key > click Start Up Arrow > Launch History Installer. Refer Figure The welcome screen appears as shown in Figure 49. Figure 49. Welcome Screen 2PAA E 79

80 History Server High Availability Installation Section 5 Installation If the previous installation was incomplete, the History Installer wizard as shown in Figure 50 appears. Figure 50. History Installer Wizard This wizard inludes the following options: Continue with the Previous Installation - Select this option to restore the installation from the point where the previous installation was cancelled. Start a Fresh Installation - Select this option to start the fresh installation. 3. Click Next in the Welcome screen to view Analyze wizard. The Analyze wizard performs the media verification. If the media folder structure does not include any folder, sub-folder, or a file, an appropriate error message is displayed for locating the missing file or folder. The installation proceeds only after locating files or folders manually. 80 2PAA E

81 Section 5 Installation History Server High Availability Installation 4. In the Install Option wizard as shown in Figure 51, select Fresh Installation. Install Option wizard appears only when the user attempts to re-install the application using History Installer. If the user is performing the installation for the first time, then they are directed to Step 4. Figure 51. Install Option wizard 2PAA E 81

82 History Server High Availability Installation Section 5 Installation 5. In Install Type Selection wizard as shown in Figure 52, select the type of installation. Figure 52. Installation Type Selection wizard a. Select Node Installation option. b. Select History Server from the drop-down list. 6. Click Next to view System Settings wizard as shown in Figure 53 and Figure PAA E

83 Section 5 Installation History Server High Availability Installation Figure 53. System Settings Wizard - Join this node to Workgroup is selected 2PAA E 83

84 History Server High Availability Installation Section 5 Installation Figure 54. System Settings Wizard - Join this node to an existing Domain is selected 7. Do the following in the System Settings wizard: a. In the System Setting section, enter History Server name in the Computer Name field. A maximum of 15 characters are allowed in the Computer Name field. The computer will be renamed to the name provided in Computer Name field. Select the Use current computer name check box to use the current computer name. b. In the Windows Workgroup / Domain Settings section, do the following: Click Join this node to a Workgroup as shown in Figure 53, if the node should belong to a Workgroup. The users displayed in the Input wizard are automatically created. The complete Workgroup name should be specified in Workgroup/Domain name field and continue with Step 8. By default, 84 2PAA E

85 Section 5 Installation History Server High Availability Installation the Workgroup name is Workgroup. Select Use current Workgroup name check box to use the current workgroup name and the workgroup name will be auto-populated in the Workgroup/Domain field. If the entered Workgroup name does not exist, an error message stating Invalid Workgroup Name appears. Click Join this node to an existing Domain as shown in Figure 54, to install History under existing domain and provide the domain name in Workgroup/Domain name field and continue with Step 8. If the machine is already added to a domain, then click Join this node to an existing Domain and select Use current Domain check box and the domain name will be autopopulated in the Workgroup/Domain field. When installing in a Domain Environment, verify the following: Verify that IPv6 in Network Adapters are disabled. Verify that domain user used for installation is existing in Domain Controller. Verify that the domain is in the same network as the History Server. 2PAA E 85

86 History Server High Availability Installation Section 5 Installation 8. Click Next to view Local Region Settings wizard as shown in Figure 55. Figure 55. Local Region Settings wizard a. Select the appropriate time zone in the Time Zone Settings drop-down list. 9. Click Next to view System Network Settings wizard. Figure 56 appears if you have selected Join this node to a Workgroup in Step PAA E

87 Section 5 Installation History Server High Availability Installation Figure 57 appears if you have selected Join this node to an existing domain in Step 6. Figure 56. System Network Settings wizard 2PAA E 87

88 History Server High Availability Installation Section 5 Installation Figure 57. System Network Settings wizard Select the NLB network. This network will be used for data communication between History Servers and History Embedded Data Collectors. a. Select the appropriate Network Adapter check box to be configured. To use a different IP address, click the IP Address next to the applicable adapter and then type the appropriate IP address. The entered IP address will be set by the History Installer during the installation process. b. Enter the default gateway in the Default Gateway column. To ignore the default gateway mentioned, select the check box Ignore Default Gateway IP. 88 2PAA E

89 Section 5 Installation History Server High Availability Installation 10. Click Next to view User Account Settings wizard to specify the System Users details as shown in Figure 58. Figure 58. User Account Settings wizard 11. In the User Account Settings wizard: a. In the Database user account section, enter the user name in the Username field. Enter the password in the Password field and confirm by re-typing the password again in the Confirm password field. b. In the Service user account section, enter the user name in the Username field. c. Enter the password in the Password field and then confirm by re-typing the same password in Confirm password field. If the Use the Database user account for Service user account check box is selected, the entered Database account user is used for Service account also. 2PAA E 89

90 History Server High Availability Installation Section 5 Installation If an existing user account other than the default user account is used, make sure that the user account has administrator privileges. d. If History Server is installed in domain environment, then follow the below steps, else continue with Step g. e. It is required to provide the User credentials which is already defined in Domain Controller as shown in Figure 59. Figure 59. User Account Settings f. If the machine is already added to Domain, then ensure that the user name provided is part of local Administrators group. g. When you click Next in User Account Settings dialog, a pop-up appears as shown in Figure 60 or Figure PAA E

91 Section 5 Installation History Server High Availability Installation In case of Figure 59, enter the local administrator user name to automatically login to the machine after a restart. Figure 60. Logon Dialog - Administrator In case of Figure 61, where machine is already added to domain, enter domain user name that is added to local administrators group to automatically login to the machine after a restart. Figure 61. Logon Dialog - Installer 2PAA E 91

92 History Server High Availability Installation Section 5 Installation 12. Click OK to view History Database Settings wizard as shown in Figure 62. This wizard allows to select the database installation type. a. In Installation Type section, select High Availability. b. In Inputs for High Availability section, select First Node. c. Enter the Common System Name, which is the NLB name that is defined during Configuring Network Load Balancing (NLB). d. Select the IP address, which is used for High Availability servers. Select the Consistency Controller Network and not NLB network. This network is dedicated for data synchronization between High Availability Servers. Figure 62. History Database Settings wizard with High Availability - First Node selected 92 2PAA E

93 Section 5 Installation History Server High Availability Installation 13. Click Next to view History Database Settings wizard as shown in Figure 63, which allows the user to select the resource allocation for the database. Make selection based on the following: For minimal system resource use, select LOW. If the computer is used also for some other purposes, select MEDIUM. If the computer is dedicated for the use for History, select HIGH. Figure 63. History Database Settings - Specifying database size 2PAA E 93

94 History Server High Availability Installation Section 5 Installation 14. Select the appropriate option and click Next to view History Database Settings wizard as shown in Figure 64. This wizard allows the user to select the applicable database size for the Real Time Database. Figure 64. History Database Settings - Database and Backup Drive a. Select the appropriate drive option from Database Drive drop-down list to store the database. Make sure that the selected database drive has been initialized using 64K block size. If the selected drive does not have the recommended cluster size (Allocation unit size), an error message indicating the same appears. For more information about formatting a drive in 64K block, refer Microsoft documentation. b. Select the appropriate drive option from Backup Drive drop-down list. The selected drive will be a backup for the database. 15. Click Next to view History Database Settings wizard, which confirms the 64K block format on the selected database drive. 94 2PAA E

95 Section 5 Installation History Server High Availability Installation 16. Click Next to view Software License wizard as shown in Figure 65. Figure 65. Software License wizard 2PAA E 95

96 History Server High Availability Installation Section 5 Installation 17. Accept the license agreement and click Next to view Confirm Setup wizard as shown in Figure 66. Figure 66. Confirm Setup wizard 18. Click Next to perform Windows Configuration, and Product Setup automatically. After the configuration, and product installation is completed, a Shutdown warning dialog appears as shown in Figure PAA E

97 Section 5 Installation History Server High Availability Installation Figure 67. Shutdown Warning Progress Alternatively, in Step 19, click Restart Later in reboot prompt to restart the computer later. 19. In the Shutdown warning dialog, click Restart Now to restart the computer immediately. Alternatively, click Wait to view Shutdown warning dialog as shown in Figure 68. Figure 68. Shutdown Warning Clicking Restart Now in the Shutdown warning dialog as shown in Figure 67 restarts the computer immediately. 20. After automatic restart, Product Setup wizard appears as shown in Figure 69. A list of components will be installed automatically. After all the required components are installed, a dialog box appears to restart the system. 2PAA E 97

98 History Server High Availability Installation Section 5 Installation Figure 69. Product Setup wizard If Windows logged in as a user, user credentials will be changed automatically by History Installer. 21. Click Restart Now to restart the system immediately. After restarting, the installation will continue from this step automatically. 22. After restart is completed, Firewall Exceptions wizard appears as shown in Figure 70, which indicates the progress of the firewall configuration. 98 2PAA E

99 Section 5 Installation History Server High Availability Installation Figure 70. Firewall Exceptions wizard. 2PAA E 99

100 History Server High Availability Installation Section 5 Installation 23. Click Next to view Finish wizard as shown in Figure 71, which indicates the completion of History Server High Availability - first node installation. Figure 71. Finish wizard 24. Click Finish to complete the installation of History Server High Availability- First Node and close the History Installer wizard. Preparing online backup of the first node Perform the Online Backup of the First Node of the History Server. In the First node of the History Server, run the following command from Command prompt: %app_root%\bin\app_backuptool /d Wait for the command to complete and confirm that online copy is successfully completed PAA E

101 Section 5 Installation History Server High Availability Installation Installing History Server High Availability - Replica Node Before installing ensure that the pre-installation procedures are accomplished. For more information, refer Pre-Installation section. 1. Press Windows Key > click Start Up Arrow > Launch History Installer. Refer Figure The welcome screen appears as shown in Figure 49 If the previous installation was incomplete, the History Installer wizard as shown in Figure 72 appears. Figure 72. History Installer Wizard This wizard inludes the following options: Continue with the Previous Installation - Select this option to restore the installation from the point where the previous installation was cancelled. Start a Fresh Installation - Select this option to start the fresh installation. 2PAA E 101

102 History Server High Availability Installation Section 5 Installation 3. Click Next in the Welcome screen to view Analyze wizard. The Analyze wizard performs the media verification. If the media folder structure does not include any folder, sub-folder, or a file, an appropriate error message is displayed for locating the missing file or folder. The installation proceeds only after locating files or folders manually. 4. In the Install Option wizard as shown in Figure 73, select Fresh Installation Install Option wizard appears only when the user attempts to re-install the application using History Installer. If the user is performing the installation for the first time, then they are directed to Step 4. Figure 73. Install Option wizard 102 2PAA E

103 Section 5 Installation History Server High Availability Installation 5. In Install Type Selection wizard as shown in Figure 74, select the type of installation. Figure 74. Installation Type Selection wizard a. Select Node Installation option. b. Select History Server from the drop-down list. 6. Click Next to view System Settings wizard as shown in Figure 75 and Figure 76. 2PAA E 103

104 History Server High Availability Installation Section 5 Installation Figure 75. System Settings Wizard - Join this node to Workgroup is selected 104 2PAA E

105 Section 5 Installation History Server High Availability Installation Figure 76. System Settings Wizard - Join this node to an existing Domain is selected 7. Do the following in the System Settings wizard: a. In the System Setting section, enter History Server name in the Computer Name field. A maximum of 15 characters are allowed in the Computer Name field. The computer will be renamed to the name provided in Computer Name field. Select the Use current computer name check box to use the current computer name. b. In the Windows Workgroup / Domain Settings section, do the following: Click Join this node to a Workgroup as shown in Figure 75, if the node should belong to a Workgroup. The users displayed in the Input wizard are automatically created. The complete Workgroup name should be specified in Workgroup/Domain name field and continue with Step 8. By default, 2PAA E 105

106 History Server High Availability Installation Section 5 Installation the Workgroup name is Workgroup. Select Use current Workgroup name check box to use the current workgroup name and the workgroup name will be auto-populated in the Workgroup/Domain field. If the entered Workgroup name does not exist, an error message stating Invalid Workgroup Name appears. Click Join this node to an existing domain as shown in Figure 76, to install History under existing domain and provide the domain name in Workgroup/Domain name field and continue with Step 8. If the machine is already added to a domain, then click Join this node to an existing Domain and select Use current Domain check box and the domain name will be autopopulated in the Workgroup/Domain field. When installing in a Domain Environment, verify the following: Verify that IPv6 in Network Adapters are disabled. Verify that domain user used for installation is existing in Domain Controller. Verify that the domain is in the same network as the History Server. 8. Click Next to view Local Region Settings wizard as shown in Figure PAA E

107 Section 5 Installation History Server High Availability Installation Figure 77. Local Region Settings wizard a. Select the appropriate time zone in the Time Zone Settings drop-down list. 9. Click Next to view System Network Settings wizard. Figure 78 appears if you have selected Join this node to a Workgroup in Step 6. 2PAA E 107

108 History Server High Availability Installation Section 5 Installation Figure 79 appears if you have selected Join this node to an existing domain in Step 6. Figure 78. System Network Settings wizard 108 2PAA E

109 Section 5 Installation History Server High Availability Installation Figure 79. System Network Settings wizard Select NLB network. This network will be used for data communication between History Server and History Embedded Data Collector. a. Select the appropriate Network Adapter check box to be configured. To use a different IP address, click the IP Address next to the applicable adapter and then type the appropriate IP address. The entered IP address will be set by the History Installer during the installation process. b. Enter the default gateway in the Default Gateway column. To ignore the default gateway mentioned, select Ignore Default Gateway IP check box. 2PAA E 109

110 History Server High Availability Installation Section 5 Installation 10. Click Next to view User Account Settings wizard to specify the System Users details as shown in Figure 80. Figure 80. User Account Settings wizard a. Provide the exact username and password that was used for High Availability First Node. This is mandatory requirement. b. Enter the password in the Password field and then confirm by re-typing the same password in Confirm password field. If the Use the Database user account for Service user account check box is selected, the entered Database account user is used for Service account also. If an existing user account other than the default user account is used, make sure that the user account has administrator privileges. c. If History Server is installed in Domain Environment, then follow the below steps, else continue with Step f PAA E

111 Section 5 Installation History Server High Availability Installation d. It is required to provide the User credentials which is already defined in Domain Controller as shown in Figure 81. Figure 81. User Account Settings e. If the machine is already added to Domain, then ensure that the user name provided is part of local Administrators group. f. When you click Next in User Account Settings dialog, a pop-up appears as shown in Figure 82 or Figure 83. 2PAA E 111

112 History Server High Availability Installation Section 5 Installation In case of Figure 82, enter the local administrator user name to automatically login to the machine after a restart. Figure 82. Logon Dialog - Administrator In case of Figure 83, where machine is already added to domain, enter domain user name that is added to local administrators group to automatically login to the machine after a restart. Figure 83. Logon Dialog - Installer 112 2PAA E

113 Section 5 Installation History Server High Availability Installation 11. Click OK to view Inputs wizard as shown in Figure 84. This wizard allows to select the database installation type. a. In Installation Type section, select High Availability. b. In Inputs for High Availability section, select Replica Node. c. Enter name of the first node of History Main server. Please make sure the NLB Configuration is already done. For more information, refer Configuring Network Load Balancing (NLB). d. Select the IP address of the first node of History Main server. Select the Consistency Controller network and not NLB network. This network is dedicated for data synchronization between High Availability Servers. Figure 84. Inputs wizard with High Availability - Second Node selected 2PAA E 113

114 History Server High Availability Installation Section 5 Installation 12. Click Next to view History Database Settings wizard as shown in Figure 85. This wizard allows the user to select the applicable database size for the Real Time Database. Figure 85. History Database Settings - Database and Backup Drive a. Select the appropriate drive option from Database Drive drop-down list to store the database. Make sure that the selected database drive has been initialized using 64K block size. If the selected drive does not have the recommended cluster size (Allocation unit size), an error message indicating the same appears. For more information about formatting a drive in 64K block, refer Microsoft documentation. b. Select the appropriate drive option from Backup Drive drop-down list. The selected drive will be a backup for the database PAA E

115 Section 5 Installation History Server High Availability Installation 13. Click Next to view History Database Settings wizard, which confirms the 64K block format on the selected database drive. 14. Click Next to view Software License wizard as shown in Figure 86. Figure 86. Software License wizard 2PAA E 115

116 History Server High Availability Installation Section 5 Installation 15. Accept the license agreement and click Next to view Confirm Setup wizard as shown in Figure 87. Figure 87. Confirm Setup wizard 16. Click Next to perform Windows Configuration, and Product Setup automatically. After the configuration, and product installation is completed, a Shutdown warning dialog appears as shown in Figure PAA E

117 Section 5 Installation History Server High Availability Installation Figure 88. Shutdown Warning Progress Alternatively, in Step 19, click Restart Later in reboot prompt to restart the computer later. 17. In the Shutdown warning dialog, click Restart Now to restart the computer immediately. Alternatively, click Wait to view Shutdown warning dialog as shown in Figure 88. Figure 89. Shutdown Warning Clicking Restart Now in the Shutdown warning dialog as shown in Figure 89 restarts the computer immediately. 18. After automatic restart, Product Setup wizard appears as shown in Figure 90. A list of components will be installed automatically. After all the required components are installed, a dialog box appears to restart the system. 2PAA E 117

118 History Server High Availability Installation Section 5 Installation Figure 90. Product Setup wizard If Windows logged in as a user, user credentials will be changed automatically by History Installer. 19. Click Restart Now to restart the system. After restarting, the installation will continue from this step automatically. 20. After restart is completed, Firewall Exceptions wizard appears as shown in Figure 91, which indicates the progress of the firewall configuration PAA E

119 Section 5 Installation History Server High Availability Installation Figure 91. Firewall Exceptions wizard. 2PAA E 119

120 Software Installation Section 5 Installation 21. Click Next to view Finish wizard as shown in Figure 92, which indicates the completion of History Server High Availability - Second Node installation. Figure 92. Finish wizard 22. Click Finish to complete the installation of History Server High Availability- Second Node and close the History Installer wizard. Software Installation The Software Installation is categorized into: Installing History Embedded Data Collector Installing History Embedded Data Collector Installing the History Embedded Data Collector will install the real time database collector PAA E

121 Section 5 Installation Installing History Embedded Data Collector Installing History Embedded Data Collector Before installing ensure that the pre-installation procedures are accomplished. For more information, refer Pre-Installation section. Execute the following steps for installing History Embedded Data Collector. 1. Press Windows Key > click Start Up Arrow > Launch History Installer. Refer Figure The welcome screen appears as shown in Figure Click Continue to view Welcome screen. 4. Click Next in the Welcome screen to view Analyze wizard. 5. In Install Type Selection wizard as shown in Figure 93, select the type of installation. Figure 93. History Embedded Data Collector - selected a. Select History Embedded Data Collector check box in the Software Installation pane as shown in Figure 93. 2PAA E 121

122 Installing History Embedded Data Collector Section 5 Installation 6. Click Next to view Local Region Settings wizard as shown in Figure 94. Figure 94. Local Region Settings wizard a. Select the applicable time zone in the Time Zone Settings drop-down list PAA E

123 Section 5 Installation Installing History Embedded Data Collector 7. Click Next to view History Database Settings wizard as shown in Figure 95. Figure 95. History Database Settings wizard - History Server details a. Enter the name of the History server. b. Select the IP Address of the main server in the drop-down list. If the IP address of the History server is not available in the drop-down list, enter the IP address manually. In case of high availability main server, enter the common name and enter IP address manually. 2PAA E 123

124 Installing History Embedded Data Collector Section 5 Installation 8. Click Next to view History Database Settings wizard as shown in Figure 96. Figure 96. History Database Settings wizard 9. In the History Database Settings wizard: a. Select the appropriate drive option from Database Drive drop-down list to store the database. Make sure that the selected database drive has been initialized using 64K block size. If the selected drive does not have the recommended cluster size, an error message indicating the same appears. For more information about formatting a drive in 64K block, refer Microsoft documentation. b. Select the appropriate drive option from Backup Drive drop-down list. The selected drive will be a backup for the database. 10. Click Next to view History Database Settings wizard, which confirms the 64K block format on the selected database drive PAA E

125 Section 5 Installation Installing History Embedded Data Collector 11. Click Next to view History Database Settings wizard for entering the user details as shown in Figure 97. Figure 97. History Database Settings wizard - Data Collector User Settings 12. In the Service User Account section: a. Enter the user name in Service User field. Entered user should have local administrator privileges. b. Enter the password in the Password field and then confirm the password by re-typing the same text in the Confirm Password field. 13. In the History Server Database User Account section: a. Enter the database account user name in the Username field. 2PAA E 125

126 Installing History Embedded Data Collector Section 5 Installation b. Enter the password in the Password field and then confirm it by re-typing in Confirm Password field. Use the following syntax to provide History Server user credentials, if the Standalone History Server or High-Availability History Servers is installed in Workgroup environment: For Standalone History Server, username must be machinename\username For High-Availability History Servers, username must be commonname\username Use the below syntax to provide History Server user credentials, if the Standalone History Server or High-Availability History Servers is installed in Domain environment: For Standalone and High-Availability History Servers, username must be domainname\username 126 2PAA E

127 Section 5 Installation Installing History Embedded Data Collector 14. Click Next to view Software License wizard as shown in Figure 98. Figure 98. Software License wizard 2PAA E 127

128 Installing History Embedded Data Collector Section 5 Installation 15. Accept the license agreement, click Next to view Confirm Setup wizard as shown in Figure 99. Figure 99. Confirm Setup wizard 16. After automatic restart, Product Setup wizard appears as shown in Figure 100. A list of components will be installed automatically. After all the required components are installed, a dialog box appears to restart the system PAA E

129 Section 5 Installation Installing History Embedded Data Collector Figure 100. Product Setup wizard If Windows logged in as a user, user credentials will be changed automatically by History Installer. 17. After the product installation is completed, click Restart Now. A Shutdown warning dialog appears as shown Figure 101 displaying the restart time. Figure 101. Shutdown Warning 2PAA E 129

130 Installing History Embedded Data Collector Section 5 Installation 18. In the Shutdown warning dialog, click Restart Now to restart the computer immediately. Alternatively, click Wait to view Shutdown warning dialog as shown in Figure 102. Figure 102. Shutdown Warning Clicking Restart Now in the Shutdown warning dialog as shown in Figure 102 restarts the computer immediately. 19. Click Restart Now to restart the system immediately. After restarting, the installation will continue from this step automatically. 20. After restart is completed, Firewall Exceptions wizard appears as shown in Figure 103, which indicates the progress of the firewall configuration PAA E

131 Section 5 Installation Installing History Embedded Data Collector Figure 103. Firewall Exceptions wizard 2PAA E 131

132 Post Installation Procedures Section 5 Installation 21. Click Next to view Finish wizard as shown in Figure 104. Figure 104. Finish wizard 22. Click Finish to complete the installation of History Embedded Data Collector and also to close the History Installer wizard. Post Installation Procedures Firewall Settings This section describes the post installation procedures. The following TCP or UDP port numbers must be open between the History Node (M) and Data Collector Nodes (D) in the direction indicated. Direction Component Port Number Description D <--> M VtrinStd-K 443/TCP Vtrin Web Socket Secure 132 2PAA E

133 Section 5 Installation History Server The ports for Kerberos authentication does not need to be open between the two computers if they are not in the same domain, because Kerberos authentication can not be used between them anyway. History Installer does not exclude RTDB-EcOPCClient from firewall automatically. Make sure to add RTDB-EcOPCClient to Firewall exception list. During History Server - High Availability configuration, add the UDP ports 7890 and 7980 to firewall exception list in both the servers. This is not required for Standalone History Server configuration. History Server When NAT (Network Address Translation) or Hardware Firewall Switch is used between the Data Collector Nodes and History Servers, then it is required to perform the following steps in all Data Collector nodes. 1. Navigate to Start > Run. In Run window, enter %app_root%\setup. 2. Create a batch file with file name as: APP_query_configuration_getparameter_P_MYIPFORMAIN.bat. 3. Edit the batch file and add this entry in the "P_MYIPFORMAIN=NAT_IP_OF_HISTORYSERVER". 4. Replace NAT_IP_OF_HISTORYSERVER with Actual IP Address of History Server. Incase of HA Configuration, use the Common IP. 5. Save the file. 6. Restart the RTDB-Scheduler Service in Data Collector Nodes. Refer Antivirus Exclusions to exclude certain locations or folders related to 800xA History Server. History Embedded Data Collector Node Refer Antivirus Exclusions to exclude certain locations or folders related to History Database. 2PAA E 133

134 Antivirus Exclusions Section 5 Installation Refer IPSec exemptions to configure in 800xA network for Data Collectors to communicate with History Server, if IPSec is configured. Antivirus Exclusions Exclude the following location related to History from the AntiVirus software. RTDB: Exclude the following path for History Server and History Embedded Data Collector: For x86 OS versions: <drive>:\program Files\ABB Oy For x64 OS Versions: <drive>:\program Files\ABB Oy <drive>:\program Files (x86)\abb Oy RTDB Database Drive: Following folders must be excluded: RTDBData Application RTDB Backup Drive: Following folders must be excluded: Onlinecopy EssentialBackup Backup UpgradeBackup IPSec Exemptions Use the IPSec rule, with name 800xA History Server, for Data Collector nodes to communicate with History Server. IPSec rule with name User Defined Protocol can also be used as an alternative PAA E

135 Section 6 Uninstallation This section describes the uninstallation procedure for History Server and History Data Collector. You can uninstall History Server and History Embedded Data Collector through History Installer. Uninstalling History Server To uninstall using History Installer, do the following: 1. Press Windows Key + W to open the Windows search pane. 2. Search for LaunchHistoryInstaller and open it. The Welcome Screen appears. 2PAA E 135

136 Uninstalling History Server Section 6 Uninstallation 3. Click Next to view Install Option wizard. Click Uninstall option as shown in Figure 105. Figure 105. Upgrade Option - Uninstall 136 2PAA E

137 Section 6 Uninstallation Uninstalling History Server 4. Click Next to view Unistall wizard, which shows details of the products that will be un-installed. Figure 106. Uninstall wizard 2PAA E 137

138 Uninstalling History Server Section 6 Uninstallation 5. Stop RTDB services and click Next to view Confirm Setup wizard as shown Figure 107. Figure 107. Confirm Setup wizard 138 2PAA E

139 Section 6 Uninstallation Uninstalling History Server 6. Click Next to view Product Setup wizard as shown in Figure 108. Figure 108. Product Setup wizard 7. After the process is completed, click Next to view Finish wizard. 2PAA E 139

140 Uninstalling History Embedded Data Collector Section 6 Uninstallation 8. Click Finish to complete the uninstallation of History Server. Figure 109. Finish wizard Uninstalling History Embedded Data Collector To uninstall History Embedded Data Collector, do the following: 1. Press Windows Key+ W to open the Windows search pane. 2. Search for Launch History Installer and open it. The Welcome Screen appears PAA E

141 Section 6 Uninstallation Uninstalling History Embedded Data Collector 3. Click Next to view Install Option wizard. Click Uninstall option as shown in Figure 110. Figure 110. Upgrade Option - Uninstall 2PAA E 141

142 Uninstalling History Embedded Data Collector Section 6 Uninstallation 4. Click Next to view Unistall wizard, which shows details of the products that will be un-installed. Figure 111. Uninstall wizard 142 2PAA E

143 Section 6 Uninstallation Uninstalling History Embedded Data Collector 5. Stop RTDB services and click Next to view Confirm Setup wizard as shown Figure 107 Figure 112. Confirm Setup wizard 2PAA E 143

144 Uninstalling History Embedded Data Collector Section 6 Uninstallation 6. Click Next to view Product Setup wizard as shown in Figure 113. Figure 113. Product Setup wizard 7. After the process is completed, click Next to view Finish wizard PAA E

145 Section 6 Uninstallation Uninstalling History Embedded Data Collector 8. Click Finish to complete the uninstallation of History Embedded Data Collector. Figure 114. Finish wizard The History Embedded Data Collector Node entry in Main Server Database Node list must be deleted manually and RTDB-Scheduler service must be restarted in the main server. 2PAA E 145

146 Uninstalling History Embedded Data Collector Section 6 Uninstallation 146 2PAA E

147 Section 7 Upgrade This section describes the upgrade procedure of the History Server(s) and 800xA History Embedded Data Collectors. 800xA History Server To upgrade 800xA History server, do the following: Log on to the History Server using the previously installed user. 1. From Programs and Features, uninstall the currently installed ABB 800xA History Installer. 2. Stop RTDB by double clicking on Stop RTDB.bat file using Desktop > RTDB Control Panel > Starting and Stopping. 3. Insert System 800xA Media and navigate to \Applications\History\History Installer. 2PAA E 147

148 800xA History Server Section 7 Upgrade 4. Double-click setup.exe to install the installer. Figure 115. History Installer Screen 148 2PAA E

149 Section 7 Upgrade 800xA History Server 5. Click Next to view Install Option dialog. Figure 116. Install Option Dialog 2PAA E 149

150 800xA History Server Section 7 Upgrade 6. Select Upgrade from Previous version and click Next to view Prerequisite page. Figure 117. Prerequisite for Upgrade Dialog 7. Stop RTDB Services, if not stopped previously and click Next to see Ready for Installation dialog PAA E

151 Section 7 Upgrade 800xA History Server 8. Click Next to start upgrade. Wait for the upgrade to complete. Figure 118. History Real Time Database Upgrade 2PAA E 151

152 800xA History Embedded Data Collectors Section 7 Upgrade 9. When prompted for restart, please restart the machine and continue with Firewall Exceptions. Figure 119. Firewall Exceptions setting Automation 10. Click Next to configure Firewall and reach Finish page. 11. Click Finish. 800xA History Embedded Data Collectors To upgrade 800xA History Embedded Data Collectors, do the following: Install.Net Framework 4.5 before proceeding with following steps..net version can be located in the path \Applications\History\3rd Party SW\Common\DotNetRuntime4 and double-click dotnetfx45_full_x86_x64.exe Log on to System using the previously installed user. 1. From Programs and Features, uninstall the currently installed ABB 800xA History Installer PAA E

153 Section 7 Upgrade 800xA History Embedded Data Collectors 2. Perform Maintenance Stop of 800xA in the Data Collector where database is being upgraded. 3. Stop RTDB by double clicking on Stop RTDB.bat file using Desktop > RTDB Control Panel > Starting and Stopping. 4. Insert System 800xA Media and navigate to \Applications\History\History Installer. 5. Double-click setup.exe to install the installer. 6. Click Next to view Install Option dialog. 7. Select Upgrade from Previous version and click Next to view Prerequisite page. Figure 120. Prerequisite For Upgrade 8. Stop RTDB and 800xA Interface services, if not stopped previously and click Next to see Ready for Installation dialog. 9. Click Next to start upgrade. Wait for the upgrade to complete. 2PAA E 153

154 800xA History Embedded Data Collectors Section 7 Upgrade 10. When prompted for restart, please restart the machine and continue with Firewall Exceptions. 11. Click Next to configure Firewall and reach Finish page. 12. Click Finish PAA E

155 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) The NLB Settings are required only in case of redundant History Server. Before performing NLB settings, verify the following: a. Availability of common subnet IPs between History Servers and DCN. b. Define the IPs in the hosts file of the History Servers. The path of windows hosts file is: C:\Windows\System32\drivers\etc. NLB Configuration is not possible if Network Adapter Speed is 100 Mbps. If you try to configure an error message mis-configured appears. Network adapter which is chosen for NLB configuration also requires 1 Gbps. It is extremely mandatory to have separate network, other than the NLB network between History Servers and Embedded Data Collector Nodes, for data synchronization and consistency between High Availability Servers The Reliable Multicast Protocol should be Enabled only for NLB network card in Network Card > Properties. Installation of NLB in History Server Nodes Perform the following steps in both History Server Node: 1. In Windows screen search for Server Manager and open it. 2PAA E 155

156 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 2. Click Add roles and features. Figure 121. Server Manager Dashboard 156 2PAA E

157 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 3. Click Next in the Add Roles and Features wizard. Figure 122. Add Roles and Features Wizard 2PAA E 157

158 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 4. Select the installation type Role-based or feature based installation and click Next. Figure 123. Installation selection wizard 158 2PAA E

159 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 5. Select a server from the server pool and click Next. Figure 124. Server selection wizard 2PAA E 159

160 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 6. Select server Roles and click Next. Figure 125. Server roles selection wizard 160 2PAA E

161 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 7. Select Network Load Balancing check-box and Click Install. Figure 126. Server Manager - Select Features Installation confirmation page appears once NLB is successfully installed. 8. Click Close to complete the NLB installation. NLB Configuration for Common IP in History Servers Perform the following steps in First (or Primary) node of the History Server: 2PAA E 161

162 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 1. In the Windows screen, search for NLB Manager. Select and launch Network Load Balancing Manager. Figure 127. Network Load Balancing Manager- Cluster 2. From the menu bar, select Cluster > New. Alternatively right-click on Network Load Balancing Clusters and select New Cluster PAA E

163 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 3. In the pop-up window, enter the Computer Name of the First (Primary) History Server Node. Click Connect. A list of Network Interfaces with IP details will be populated. Figure 128. New Cluster - Connect 4. Select the Interface which will be used for NLB. 5. Click Next to view the Cluster IP Addresses dialog. 2PAA E 163

164 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 6. Click Add.. to define the common IP Address. Figure 129. New Cluster - Host Parameters Ensure that this common IP address is having same subnet as the interface of history servers which has been used for NLB PAA E

165 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) Figure 130. New Cluster - Cluster IP Addresses Figure 131. Add IP Address 7. After adding the common IP, click OK and then Next to define the cluster parameters. 8. In the cluster parameters window: 2PAA E 165

166 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) a. Enter the Full Internet name. This will be common name for the High Availability for the History Servers. b. Select the Multicast option in the Cluster operation mode. 9. Click Next. Figure 132. New Cluster - Cluster Parameters 10. In the port rules window, define port rules as applicable for the installation. By default, all port range ( ) are allowed. As a minimum following ports should be allowed: UDP ports: 7890 and PAA E

167 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 11. After the port rules are added click Edit. Figure 133. New Cluster - Port Rules 2PAA E 167

168 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 12. Select Single host in the Add/Edit Port Rule window. Figure 134. Edit Port Rule Wizard 13. Click OK and then Finish to complete the configuration for First or Primary Node. 14. From the Network Load Balancing Manager, select the common name, rightclick and select Add Host to Cluster PAA E

169 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 15. In the pop-up window, enter the Second (or Secondary) History Server Node Name and click Connect. Figure 135. Add Host to Cluster - Connect 16. Select the appropriate Interface. Ensure that, the Interface IP is in the same range as of First (or Primary) History Server. 2PAA E 169

170 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 17. Click Next. Figure 136. Add Host to Cluster - Host Parameters 170 2PAA E

171 Appendix A Network Load Balancing (NLB) Configuring Network Load Balancing (NLB) 18. Refer Step 10 above for assigning Port Rules. Figure 137. Add Host to Cluster - Port Rules 2PAA E 171

172 Configuring Network Load Balancing (NLB) Appendix A Network Load Balancing (NLB) 19. Click Finish to complete the NLB Configuration. Figure 138. Network Load Balancing Manager 172 2PAA E

173 Appendix B Adding High Availability Server Introduction This section describes the procedure to convert single history server to High Availability servers only when the current history server is already installed and running. To convert a single history server to HA servers, do the following: 1. Login to the current History server with the installed user name. 2. Install the NLB mentioned in Configuring Network Load Balancing (NLB). The current History Server will now be considered as HA1. 3. Prepare another machine to behave as Second History Server in HA Configuration i.e., HA2. 4. In HA2, use the same user name and password as that of HA1. Add the newly created user name to the local administrators group. In HA2, login to the machine with the newly created user and configure NLB. Refer Configuring Network Load Balancing (NLB). Perform the following steps in HA1: 1. Stop the RTDB by running Stop RTDB.bat file. 2. Navigate to <RTDBDatabaseDrive>\RTDBData folder and delete the following: RTDB_ConsistencyControlFile*.Table* RTDB_ConsistencyControlFolder*.Table* 3. Navigate to the following path available in System 800xA media:...\applications\history\\history\realtime_db\project CPIMS\ 2PAA E 173

174 Introduction Appendix B Adding High Availability Server 4. Open the command prompt, drag and drop the Upgrade Project CPIMS.bat from the above path. 5. Append /CC:ON as follows. This is done to run the upgrade with consistency controlled enabled to convert to HA configuration....\applications\history\history\realtime_db\project CPIMS\Upgrade Project CPIMS.bat/CC:ON 6. Provide the following inputs: Give Command [] : 1 Do you want to configure NLB first? [Y/N] []: N Have users been notified? <Y/N/Q> [N] : Y Have local applications been stopped? <Y/N/Q> [N] : Y 7. After successful upgrade, following message appears in the command prompt: SUCCESS: "APP_Install_RTDB_Project"/Upgrade Completed successfully, returning exit code 0 8. Press any key in the command prompt to continue further. 9. Close the command prompt window. 10. Close the ToDo* notepad information file, which opens during the Step Modify DSN: Since the High-Availability scenario requires a common name. You need to modify the DSN name. Typically, the name will be <NLBNAME>-RTDB. NLBNAME is the Full Internet name given during NLB Configuration. a. Go to Windows > Run. Enter following to open the Setup_Answer.bat file notepad "%app_root%\setup\setup_answers.bat" b. Setup_Answer notepad opens. Modify the row: SET "ANS_P_DSN=oldname-RTDB" to SET "ANS_P_DSN=<NLBNAME>-RTDB" c. Save and close the file. d. Execute the following command in the command prompt. "%app_root%\config\application\install_odbc_dsns.bat" /remove 174 2PAA E

175 Appendix B Adding High Availability Server Introduction e. Go to Windows > Run. Enter following to open App_Defenvironment.bat file. notepad"%app_root%\config\application\app_defenvironme nt.bat" f. App_Defenvironment notepad opens. Modify the row: cscommon_cmd -defsysenvvar APP_DSN "oldname-rtdb" to cscommon_cmd -defsysenvvar APP_DSN "<NLBName>-RTDB" g. Save and close the file h. Run the following command in the command prompt. "%app_root%\config\application\app_defenvironment.bat" i. Close all command windows. j. Open a new command prompt and execute command: "%app_root%\config\application\install_odbc_dsns.bat" 12. Reinstall the services so that the new URL name is written to the necessary configuration files. a. To remove Services, open command prompt and run following "%app_root%\config\application\app_install_services" /remove all b. Enter Y when asked for confirmation to remove all services. c. Install the services. Open command prompt and run following. "%app_root%\config\application\app_install_services" /install all d. In the command prompt, enter Y when asked for confirmation. 2PAA E 175

176 Introduction Appendix B Adding High Availability Server Ignore the following error that shows on command prompt: 01:06: :06: ERROR: APP_RtdbServiceInstaller "RTDB- Scheduler E:\RTDBData" install failed -- see log file E:\RTDBData\diag\APP_RtdbServiceInstaller.log" 01:06: ERROR: "E:\Application\config\FeatureInstall\APP_FeatureInstaller.bat": 15 application features successfully installed, 1 failed See log file "E:\RTDBData\diag\APP_FeatureInstaller_SelectedFeatures.log" e. Go to Windows > Run > Services.msc and set the startup type of RTDB <DriveName>\RTDBData service to Automatic. 13. To re-create RTDB control panel run the following in the command prompt. "%app_root%\config\application\app_createcontrolpanel.bat" 14. Press any key to continue... until you get the command prompt. 15. Run the following in the command prompt to rename the Setup_Answers file for the History Server: ren "%userprofile%\abb oy\parameters\setup_answers_<old History server name>-rtdb.bat" "Setup_Answers_<NLBNAME>- RTDB.bat" 16. Define consistency controller IP address by running the following in the command prompt: %app_root%\setup\app_config_cc.bat 176 2PAA E

177 Appendix B Adding High Availability Server Introduction Figure 139. Multicast adapter IP address a. Enter the consistency controller network IP address in Multicast adapter IP address. This is the dedicated network that will be used for data synchronization between History Servers. Multicast adapter IP address []: b. When Multicast IP address is asked to enter again, leave it blank and press the Enter key. 17. Restart the HA1 machine. 18. Go to Windows> Search for Vtrin and open with Run as Administrator. 19. Login with "tcp:// /<nlbname>-rtdb" location. Click OK to open the GUI. 20. In Vtrin GUI, navigate to Maintenance > Basics > DatabaseNodes as shown in Figure PAA E 177

178 Introduction Appendix B Adding High Availability Server Figure 140. Database Nodes 21. Select all the entries, right-click and select Delete. 22. Click Yes to confirm the delete. 23. Run the following in the command prompt to accept the new keys generated for Vtrin access. %app_root%\bin\app_acceptvtrinserverkeychangesforservices.bat 178 2PAA E