Hi everyone,
Luckily we do have InTouch Unlimited Packages since a while now. If needed also for a redundant setup.
As an example I'd like to take the InTouch Unlimited Professional License which includes the following:
- Unlimited Tags
- Unlimited Web Clients or RDS Clients
- Historian 5k
- Professional Com Drivers
- InTouch Web Workspaces
- Aveva Reports
- MQTT, OPC UA Server
So when running two of these licenses (redundant setup) I have everything times two.
When setting up an architecture I have a few options, two of them are mainly relevant:
1. InTouch Web to provide data to clients via a browser (https) with the Web Server
2. InTouch Tag Server on a Terminal Server with RDP Clients using remote tag referencing to connect to the tag server application.
There are few things to consider for a redundant setup:
- Historical process data
- Historical alarm data
- I/O
- License Server and so on
Running a secondary I/O source for InTouch should not be an issue with two com driver licenses, just add a secondary source for whatever I/O there is available.
To my problem now:
Running a second Historian, configured as Partner Historian, seems to be a problem with the current setup.
Since a few versions it's possible to directly define a Historian in InTouch that is used for process data and/or alarms and events historization. My problem is that the second Historian doesn't get any data at the same time as this is the case for Application Server. So there is no redundant data Historian in place.
Does this have to be done manually? Or what best practices do you use setting up a "complete" redundant setup with InTouch?
It would be great to have some discussion on this topic because not every customer is going to use App Server instead.
Thanks
Peter
