Move Controller / Project to another Connectivity Server
HI
Our Basic History has too many Logs. (20000 instead of 10000). So i would like to move a Project to our new Connectivity Server Pair.
What do I have to do? Just Settings in the OPC Server?
Who decides which data is stored on which server. What is happening with "old" Data after moving the Controller to the other Server Pair?
System 6.0.3.1
3 Aspect Sever
2x2 Connectivity Server
Thx
Our Basic History has too many Logs. (20000 instead of 10000). So i would like to move a Project to our new Connectivity Server Pair.
What do I have to do? Just Settings in the OPC Server?
Who decides which data is stored on which server. What is happening with "old" Data after moving the Controller to the other Server Pair?
System 6.0.3.1
3 Aspect Sever
2x2 Connectivity Server
Thx
Asked 2 months ago
Answers
1
In the control structure on your network you find a aspect "History Source". This point to the service group. You may set such an aspect for your controller and point to a different service group for your new CS pair. But the old data will get lost I assume:
/Erik
2
There is an explanation of how the History Source Aspects are utilized in the manual, 3BUF001092-600, starting on page 183. Even though this is an IM manual, it applies to the Aspect System in general. As has been stated in other comments to this question, the History Source/ Service Group selection will determine the location of where the system will place the Basic History Logs. The typical configuration of this Aspect will place the resulting logs into the Connectivity Server(s) associated with the data responsible application, in the default location, C:\OperateITData\History, under the site specific GUID directory.
Regards,
Geof Ledin
Regards,
Geof Ledin
1
Hi!
A good idea is to export key history data w DataDirect or...
If possible, you can stop Basic History Service and copy (all) the history directory from your old server pair to a separate disk.
It is then later possible to access/investigate (old) data with "AdvHtLogDataViewer.exe"
The hard part is to manually resolve LogId (GUID).
BR
A good idea is to export key history data w DataDirect or...
If possible, you can stop Basic History Service and copy (all) the history directory from your old server pair to a separate disk.
It is then later possible to access/investigate (old) data with "AdvHtLogDataViewer.exe"
The hard part is to manually resolve LogId (GUID).
BR
Answered 2 months ago
Add new comment