more quick actions
minimize quick actions
Topic starter
Hello!
One of our customers reports problems with single active server archiving into ODBC databases.
I checked his configuration and everything appears to be correctly configured.
That means:
- Both archiving servers are in the same association of historical servers.
- Association is set to "historical" and "single active server".
- Station list for historical servers contains this association.
- ODBC archive unit is assigned the correct station list.
The problem: both servers are permanently archiving data in parallel, also the inactive server. The connection between both servers is fine, they agree which one is the active server of the association.
Do you have any experience with single-active server redundancy for ODBC?
Is there any known limitation which prevents the described scenario from working? The documentation reads "You can use client-server with either proprietary or database type archive units.". That seems to exclude ODBC archive units...
Posted : 17/08/2017 6:19 pm
Hi,
To my knowledge neither ODBC nor proprietary units support redundancy.
And for sure when you see 'database unit' in the online help, it's about HDS archive units, and not ODBC.
Experience from others is welcome, and a confirmation from the R&D would be good.
In all cases Armin, please forward the inputs under the form of an SPR so that the doc can be fixed if it is misleading.
Regards
Posted : 17/08/2017 7:28 pm
Hello Armin,
As I know, only HDS archive units can work in single-active redundancy mode.
All the other archive units (Proprietary, ODBC) use multiple-active redundancy.
It seems to me, that whatever the type of association inside the historical server list (used in the archiv unit), PcVue will consider as a multiple-active association.
However, like BL wrote : a confirmation from the R&D would be good
RT
Posted : 22/08/2017 7:03 pm
I confirm, only HDS.
Posted : 18/12/2017 2:26 pm