Hi,
I have a newly deployed galaxy with a historian server running. When I deployed my instances for the first time the tags were added to the Runtime database as expected.
I then later decided to add a partner historian, after installing historian on the computer hosting the partner historian, I added the reference in the parameters window on both servers. Like described in the manual.
Now my question is.... in the runtime database on the partner historian how do the tags get added, I was hoping it would function in the same manner as with the primary, i.e the tags get created automatically on the partner server as well....
That does not seem to happen. Do I need to export the runtime database from the primary historian? and import to the partner? It does say anything about this in the admin manual see below.
file:///C:/Program%20Files%20(x86)/Wonderware/Historian/Docs/1033/HistorianAdmin.pdf
Page 290
Using a Redundant Historian
You can configure the AVEVA Historian to have a "partner" AVEVA Historian that can be used as a hot backup if
the primary historian is not available. This is called a "redundant historian" setup.
If AVEVA Application Server is configured to send data to the AVEVA Historian, the AppEngine automatically
sends data to both the primary historian and the specified partner. If one of the historians goes offline, the
AppEngine stores the historized data until the historian comes back online. After the connection is restored, the
AppEngine forwards the data to the historian that was offline.
The Historian Client automatically detects and selects the online Historian from the redundant pair.
The historians in a redundant setup are not intended to be a synchronized pair, where both the historian
configuration and data are fully and automatically synchronized. It is up to you to make sure that the two
historians are symmetrical and synchronized. The following recommendations are examples of actions you
should take to keep the pair synchronized, or else incoming data is not stored as previously described.
• If you make configuration changes for one historian, be sure to perform the same actions on the partner.
• If you import a CSV file on one historian, you will need to repeat the import on the partner.
• If you add or update data to one Historian using SQL or the Historian SDK, you will need to repeat the action
on the partner.
To specify a historian partner:
1. In the Operations Control Management Console, expand Historian Group, expand the server, and then
expand Configuration Editor.
2. Expand System Configuration and then click Parameters. A list of all system parameters displays in the
details pane.
3. Double-click the Historian Partner system parameter. The System Parameter Properties dialog box appears.
4. In the Value box, type the computer name of the partner historian. You can use either the host name, fully
qualified name, or an IP address. Leading backslashes are optional.
Note: In network environments where AppEngine and Historian Client computers on different subnets must
access the partner, be careful to use a name or IP address that can be correctly resolved from all of those
network locations and not just between the historian servers themselves.
regards
Jakob
