It is not supported to mix one server being 32-bit and one server being 64-bit to form a hot-standby redundancy server pair. For productive use both Hot-Standby redundancy partners must be identical and must be 64-bit as the 32-bit server can only be operated as an engineering server. Please refer to software-requirements.
Note the restriction for the following connect and query functions regarding the usage with multiple systems: dpConnect(), dpQuery(), dpQueryConnectAll(), dpQueryConnectSingle(), isAnswer() as well as isRefresh().
Note that the entry for the local host, 127.0.0.1
localhost, always has to exist in the host file.
If the active server is stopped under Solaris and the system overview panel is not used, the color of all objects might be set to inactive for few seconds. To avoid this, use the function getLastError() in the work function when using the function dpConnect(). |
A normal installation of WinCC OA version 3.0 or higher is sufficient for using the redundancy. See chapter Installation for more information on installing WinCC OA. The configuration of a redundant system with WinCC OA is described in detail in the chapter creating a redundant system.
For instruction how to perform a WinCC OA version/patch/service pack upgrade in a redundant system, see WinCC OA Upgrade in a redundant system.
When using redundancy for a WinCC OA project under Solaris, it is necessary to deactivate the possibility to call the TCP service by the Network Information Service (NIS). Otherwise a loss of the network connection would lead to the service being blocked. To apply the necessary changes the line "services files nis" inside the file /etc/nsswitch.conf must be changed to "services files". |
V 3.11 SP1
Copyright ETM professional control GmbH 2013 All Rights Reserved