Move Basic History from an existing Connectivity Server to a new Connectivity Server
Has anyone done something like that if an 800M OPC server got overloaded and you had to split into two?
At the moment at K+S we have 1 Control Network and 3 Projects with 3 pair of AC800M OPC Servers.
And want to add a 4 th pair and reduce the load of the first pair of connectivity Servers.
Specific want all the Well Pad Controllers to be moved under the new Connectivity Server.
At Application level we defined the OPC Data Source Definition aspect which points out the appropriate pair of Connectivity Servers.
It is not a big deal to change the OPC Source Definition aspect to point to the new OPC Servers, but
- How do I move the Basic History from CS-1-A/B to the new CS-6-A/B? (only for those Applications that I moved over)
Voted best answer
One way you can move the basic history is upon adding the new connectivity pairs and changing the basic history source in the respective applications, Log points will be created automatically then you have to do the following:
1. Compare the log points (new flat files vs old log points in the existing pair)
2.stop the basic history SG for the running/existing and new history source pairs.
3. Cut paste the equivalent log points and restart the basic history SG for both new and existing CS pairs.
I have doubt why don't you increase the RAM/changing servers with high HDD/RAM capacity with RAID1 fasten the process
As per recommendation, Always its better idea to create data source definition under Control network level rather than under apps level, if you want to create more projects then create under projects for OPC sharing.