Hello Experts,(this post follows up on yesterday's discussion regarding using Aveva/Wonderware InTouch 2014 Runtime with dual MSSQL servers)I am interested in establishing redundancy for 2 InTouch 2014 Servers, and I would like to know the steps needed to synchronize them to ensure redundancy. Currently, there is one InTouch 2014 Server with 2 or 3 connected clients, and I have been tasked with setting up a second InTouch server to act as a redundant backup for those clients. I would appreciate any guidance, tutorials, or resources on how to accomplish this task. Any advice or insights on this topic would be highly valued! I apologize if this question has been asked before, but I have not found the specific answers I am seeking. Thank you and Regards, AK
Are you referring to the tag server? Let's proceed with that assumption. To set up a secondary server, you will need to follow these steps: 1. Install the System Platform Management Console (SMC) and the necessary communication drivers (such as OI.ABCIP, GESTRP, etc) on the new server. Refer to your existing server's SMC to determine which drivers are required. 2. Create the appropriate communication paths/topics on the new server's SMC. Mirror the settings from your existing server's SMC. 3. In your InTouch access names, enable the "Secondary Source" option and input the same information as the primary source, except for the node name, which should be the server name or IP address of your new server. 4. After pushing out the changes to clients, your secondary server should become operational. To test, temporarily disable the communication driver on your primary server. Keep in mind that the switchover process may take several minutes depending on the size of your InTouch application's tag database.
Thank you, @lmscar12, for your prompt and thorough response! I am looking forward to getting more involved in the project soon. I will implement your suggestions and provide an update on this thread with the outcomes. Best regards, AK.
Hi AK, great question! I agree that setting up redundancy is a critical step to ensure your system's resilience. Here's a brief overview of setting this up with InTouch servers: Firstly, you'll need to ensure that both servers have the same version (InTouch 2014 as per your details). Next, it's important to establish the ODBC connection to the SQL Servers on both machines, ensuring each server is updated with identical specifications and settings, especially the Database Names, Database Usernames and Passwords. Install InTouch on the backup server and run both servers with the same application name. Avenue Suite should be installed on both servers, this provides redundancy. Remember to set the redundancy settings (active/passive or active/active) based on your requirement. Do read more on Wonderware's System Platform ReadMe and redundancy section in InTouch's help for a detailed understanding. Also, get in touch with the Aveva's customer support, they should be able to direct you to step-by-step guides or tutorials. You're on the right track, and I'm confident that you'll get it set up in no time! Good luck!
Hi AK, it sounds like you're taking the right steps for your project. To establish redundancy, you'll need to make sure your two servers are continuously synchronizing data. Wonderware's Redundancy Manager can be of great help in this as it helps manage the switchover between primary and secondary servers. Also, verify your licensing allows redundancy as you might require additional licensing for the redundancy setup. The WW SuiteLink provides an option for mirrored I/O servers that might be useful. I'd suggest referring to Aveva's 'Wonderware System Platform Installation Guide' (you can find it online) as it provides quite comprehensive steps on redundancy setup. Make sure your servers are identical in terms of their configuration to avoid unforeseen issues. This process can be a little complex, don't hesitate to reach out for more help if needed. Good luck!
Hi AK, achieving redundancy with two InTouch servers is a wise strategy to ensure system availability in the event of downtime. The Wonderware Information Server (WIS) provides redundancy mechanisms that could be beneficial to you. Utilize the InTouch Transaction Manager redundancy feature along with Microsoft SQL Server replication. A tutorial in Wonderware System Platform's online help files explains this pretty well. Do bear in mind that establishing this configuration might affect your system performance, so ensure your servers can handle it. Managed switches and a good LAN network will minimize synchronization issues. Also, consider using a professional service to oversee the setup to avoid pitfalls. The work upfront pays off in reliable data continuity. Good luck!
Hi AK! Setting up redundancy for your InTouch 2014 servers is a smart move to ensure continuous operation. A good starting point is to configure your servers to use a shared database setup—this way, both servers can read and write to the same MSSQL database, which helps keep them in sync. You might want to look into using the Redundant Server feature within InTouch, which guides you through setting up failover configurations. I recommend checking out the Aveva documentation for detailed steps or even community forums where others might have shared their experiences. Don't forget to test your setup thoroughly to ensure everything switchover seamlessly when needed. Good luck!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - Redundancy is important to ensure continuous operation in case of server failures. It allows for seamless switching to a backup server to minimize downtime.
Answer: - The steps typically involve configuring both servers to share data, ensuring data synchronization between them, setting up failover mechanisms, and testing to ensure the redundancy system works as expected.
Answer: - There may be official documentation provided by Aveva/Wonderware, online tutorials, or community forums where experienced users share their insights and best practices for setting up redundancy in InTouch servers.
Answer: - Setting up proper failover mechanisms, ensuring data synchronization, and testing the failover process are crucial steps to ensure a smooth transition for clients from one server to another in case of a failure.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.