Configuration and Embedding of the Disaster Recovery System

This chapter describes step by step how to embed the Disaster Recovery System into a WinCC OA standard project. In this example project, historical archiving with Oracle® is used with the help of the WinCC OA RDB Manager.

The project in this chapter is a standard project; however, the embedding can be done in exactly the same way in a redundant project. To learn how to create a project, see chapter Create project.

General preparation before embedding

Create the project directories on all servers used and make them accessible to all users who should have this permission.
Set up both databases (PSS and SSS database) with the same schema name, password and configuration. The installation of the WinCC OA database schema is described in the First-Time Installation.
Please make sure that for each real driver also a corresponding simulation driver exists! This means that e.g. for the IEC driver a simulation driver with the manager number 1 (-num 1) exists, whose manager number is also 1.

Embedding the Disaster Recovery System

The section describes step by step how to embed the Disaster Recovery System into a standard WinCC OA project. In the project, historical archiving is deployed with Oracle® using the WinCC OA RDB Manager.

Therefore, the following steps must be performed:

Registration of the WinCC OA Project on the first PSS server

Copy the WinCC OA project to the first PSS Server, if this has not already been done
Register the project on the first PSS Server using the project management. For information on how to register a project, refer to the chapter Register project.
Open the shell of the operating system and change the system name and the system number in the project using the WinCC OA WCCOAtoolSyncTypes tool. In the following example, the system name and system number of the TEST_REDU_4 project are changed to "System1" and "1". However, any user-defined number and name that are not already occupied by another distributed system can be used.

Figure 1. Change System name and system number

Redundant configuration of the project (creating the second server of the Primary Server System)

This step is only necessary if the project is not already configured as a redundant project!
Open the config file of the project and define the name of the two PSS servers in the [general] section. For example:
```
[general]
data = "PSShost1$PSShost2"
event = "PSShost1$PSShost2"
```
Add a redundancy manager (WCCILredu) below the default control manager (pvss_scripts.lst) in the WinCC OA console.

Configuring the project as a distributed system (creating the Secondary Server System)

Open the config file of the project and define the project as a distributed system. This can be done using the following config entries:
```
[general]
distributed = 1
```
The config entry states that the project is a distributed project.
Add a DIST manager (WCCILdist) in the WinCC OA console under the redundancy manager.

Adding the control manager disRecSystem_Controller.ctc

Add a new control manager to the project's WinCC OA console with the disRecSystem_Controller.ctc option. In this sample project, the control manager has the number 5 and a manual start mode. Normally, managers are always set to the alwaysmode. Setting a manager to manual should only be done temporarily during setup and changed again later.

CAUTION: Note that the CTRL manager must have the same manager number on all systems!

Copy the project to all servers

Copy the complete project to the second PSS server and then to the two SSS servers. Note that the project names must be different for the PSS and SSS. After copying the project, change the project name.
Open the config files for the two SSS servers and change the data and event entries to the appropriate SSS server entries:
```
[general]
data = "SSShost1$SSShost2"
event = "SSShost1$SSShost2"
```
Add the distPeer entry and define the PSS server and primary server system number (this number was configured in step I):
```
[dist]
distPeer = "PSShost1$PSShost2" 1
```
Copy the entries from the config file of the first SSS server to the config file of the second SSS server, if this has not already been done.

Register the project on all servers

Register the project on the second PSS server and on the two SSS servers using the project project administration (see also Register project).
Open the Shell of the operating system on both SSS servers and change the system names and system numbers of two SSS servers using the WinCC OA tool WCCOAtoolSyncTypes. In the following example, the system name and the system number of the TEST_REDU_4 project are changed to "System2" and "2". However, any user-defined number and name that are not already used by another distributed system or by the PSS system can be used.

Figure 3. Change the system names and system numbers

General configuration of the Disaster Recovery System

Start the project on a PSS and an SSS serverbut without starting the control, driver and simulation driver managers). This should already be prevented by the manual setting in the manager properties (see step II. 5.).
Open the GEDI on the PSS Server.
Open the 2x2 Redundancy tab in the WinCC OA System Management.
Figure 4. System Management - 2x2 Redundancy
Click on the Configuration button in order to open the Disaster Recovery System configuration wizard.
The configuration wizard helps to guide the user through the first steps of configuring the Disaster Recovery System (for detailed information, see Configuration). The general configuration wizard can be started at any time via the system management in order to change the configuration of individual steps.

Starting the synchronization script

In the WinCC OA console on the active PSS server, change the start mode of the control script that starts the disRecSystem_Controller.ctc script to always. Thereby, the control manager starts and carries out the synchronization script.
Start the synchronization script on the remaining servers of the PSS and the SSS by changing the start mode of the control manager to always.
On the PSS, all drivers and control scripts are now started automatically via the control manager.
On the SSS, all simulation drivers are now started automatically via the control manager.

Configuration of the automatic file synchronization

Open the WinCC OA system management with the tab 2x2 Redundancy.
Click on the File synchronization” button in order to open the panel displayed below. See chapter File Synchronization for more information.

Figure 5. Synchronization of the project files

Installation of the package for historical synchronization in Oracle®

See Requirements and Installation.

Installation on the client host

There are two ways to install the project on the client host:

Viewing and controlling panels in a web browser using the Desktop UI
Setting up the client as a remote User Interface.

Both ways are described in the corresponding chapters of the WinCC OA online help. However, it is important to note that two UIs (one on the PSS and one on the SSS) must be installed.