novaPro Open Master / Backup configuration - sauter-controls.com ...

novaPro Open
Master / Backup configuration

Summary
1. PDM CONFIGURATION 3
1.1 IP ADDRESS 3
1.2 NPO STATION CONFIGURATION 4
1.2.1 MASTER station configuration 4
1.2.2 BACKUP station configuration 8
1.3 NOVAPRO OPEN CONFIGURATION 10
1.3.1 MASTER station 10
1.3.2 BACKUP station 10
1.4 CMVPI.DAT 10
2. DATA POINT ENGINEERING 11
2.1 TAG DEFINITION 12
2.2 HISTORICAL DATA STORAGE 14
3. ALARM MANAGEMENT WITH MBAS 17
3.1 MBAS CONFIGURATION 17
3.2 EAM CONFIGURATION 17
4. SQL DATABASE CONFIGURATION 19
4.1 INSTALLATION ON MS SQL 2005 STANDARD 19
4.2 INSTALLING MS-SQL 2008 29
5. SQL TABLE DEFINITION 33
5.1 CMUM 33
5.2 AUDIT TRAIL 36
5.3 TAG HISTORY 38
6. CONNECT NOVAPRO OPEN TO THE SQL DB 40
6.1 CMUM USER MANAGEMENT 40
6.2 AUDIT TRAIL 43
6.3 TAG HISTORY – ODBC NETWORKING 49
7. ROBOCOPY 55
8. TIPS AND TRICKS 58
8.1 SUPPORT CASES 58
8.2 POLL BACKUP STATION STATUS 58

1. PDM configuration
1.1 IP address
In the Hot Backup, PDM1 is the Master station and PDM 2 is the Backup station.
a) Check that both stations are on the same network (192.168.1 in this case).
- Master IP address: 192.168.1.22
- Backup IP address: 192.168.1.23
Checking the IP address of the Master
Checking the IP address of the Backup
b) Check whether communication is present between the Master and Backup stations: Enter
the Backup IP address on the Master.

Backup station ping from Master station
1.2 nPo station configuration
1.2.1 MASTER station configuration
a) Open the novaPro Open project on Master station
b) Define network properties of the Master: Network > Local Station and Network Properties, or via the
novaPro OpenNetwork icon
novaPro Open Studio

c) Activate network
General tab of the Network Properties tab
The following options are available:
Message control
The following options are available:
- Activate network: The network is activated. Select this option to activate the
network.
- Network, maximum delay: Maximum period for which an inquiry waits for a
reaction from a remote station.
- Max. delay, network time: Maximum period for which a station waits before the
other stations are updated with tag and alarm changes. Default is 1000 ms.
- Max. delay, network change: Maximum number of messages accumulated by
an output station before the data buffer is sent to a target station. Default is 48
messages. As soon as one of the two settings reaches the defined value, the data
buffer is sent.

d) Define the station name and station ID
Configuration of Master station name and ID
Make sure that the stations in the network have unique station names and IDs. It is advisable to keep an
interval of 10 between the different station codes. For example, if a code has the ID 80, the next should have
the ID 90, the next ID 100 etc. The range for ID numbers if from 1 to 999.
Protocol configuration Master station

e) If the TCP/IP protocol is used, enter the IP address of the Backup station on the Master station in
the Network Properties - Backup tab, in the TCP/IP address field.
Define automatic change-over and enter the IP address for the Backup station
f) Save project on Master station
g) Once the network configuration for the Master station is complete, copy the project directory to the
Backup station with the same path.

novaPro Open project directory
Note: Install the nPo projects with the same path on the Master and Backup stations.
1.2.2 BACKUP station configuration
a) Open novaPro Open project on Backup station
b) Activate the network.
c) Set the station as the Backup station and define the period for monitoring of the Master station by
the Backup station.
d) “Combine Hist. Data” updates the Master with the GT*.* data logged on the Backup station.

Backup station configuration
e) Define the protocol.
Define the IP address for the Master station and the automatic change-over.
Define automatic change-over and enter the IP address for the Master station
f) Save novaPro Open on Backup station

Note: For more details on setting up Master – Backup stations, read Section 19, Network of the EY3600
novaPro Open 3.0 - Operator's Manual, Volume I.
1.3 novaPro Open configuration
1.3.1 MASTER station
nPOpro settings on the Master station
Read tag: Activates the nPOPro tag reading mechanism.
Tags are read according to the read rate defined for the tag in the Tag definition dialogue box. If you do not
enable this option, no tags are read. In Master mode, tags are read from PDM 1.
1.3.2 BACKUP station
nPOpro settings on the Backup station
1.4 CMVPI.dat
To enable reading of tags from PDM 2, after switching over to Backup mode nPOpro parameter "Read tag"
must be enabled on the Backup station. This parameter is enabled thanks to WIZVPI.dat.
On Backup station
a) Open CMVPI.dat file.

CMVPI.dat in project directory
b) In WIZVPI.dat on the Backup station, check that G is present with the +sign; replace the -
sign with a + if necessary. This activates the “Read tag” parameter in nPOpro after
switching to Backup mode.
CMVPI.dat on the Backup station
2. Data point engineering

2.1 Tag definition
Tag definition - General tab

Setting the recording interval and ODBC logging

Tag definition - Start value tab
The start value defines the value that is shown for this tag on the user interface when nPo starts. The last
value recorded in the Tag History is used as the start value. It is advisable to select the "Last historical
value" as the start value so that the displayed value remains consistent with the last saved value (e.g. after
a data restore).
2.2 Historical data storage
Storage of the Tag History and Alarm History files is defined as follows:
Create two folders in the project directory on PDM1 and PDM2:
AlertHistory
GateHistory
In the AlertHistory directory, you will find the AL*.* files that contain the Alarm History data.
In the GateHistory directory, you will find the GT*.* files that contain the Tag History data.

Storage directories for GT*.* and AL*.* files
In nPO Master and Backup
The path for these storage directories should also be defined in novaPro Open.

Path setting in novaPro Open
Path setting for Alerthistory and Gatehistory directories

3. Alarm management with MBAS
MBAS is used to synchronise the Alarm History files after the Master station has been.
3.1 MBAS configuration
- Save mbas.exe in Autostart on the Master station and Backup station
mbas.exe in nPO Manager in Autostart of the Master and Backup station
On starting the nPo application, the “MBAS Manager” window must appear with the configured
parameters: Station Name, Station ID, Backup Mode (Auto/Manual), Station Status, IP Address of Active
Station, IP Address of Second Station (depending on operating mode - Master or Backup), Type of
Active Station (Master or Backup).
Note: After installing MBAS on the Backup station, redefine the path for the MBAS in the Start-up settings.
3.2 EAM configuration
- After configuration of alarm management has been completed using the Extended Alarm
Management (EAM) module, copy the Jericho directory (containing EAM parameters)
from the Master to the Backup, in the Bin directory (same path).

Storing the Jericho directory on the Master and Backup stations

4. SQL database configuration
Note: Tag and Alarm History can also be entered in the SQL DB using the CMlogger tool.
4.1 Installation on MS SQL 2005 Standard
Registration - Licence, MS SQL 2005

Requirements for installing MS SQL 2005
Installation of SQL server components

MS SQL Installation Wizard
Check the system configuration

Registration and product key
Select SQL components

Enter SQL instance name
- N.B.: The instance name should not exceed five characters.
Definition of service account

Authentication mode and password definition
- The defined password is needed in order to set up access to the SQL server in novaPro
Open ( 6.1 CMUM User Management)
Definition of collation: this depends on the regional settings (language, alphabetic characters)

Installation option: default configuration
Error message and application report setting

Installation start
MS SQL 2005 setup process

MS SQL 2005 CD 1 installation: completion
- Insert CD 2 for MS SQL in the CD drive
SQL 2005 Surface Area Configuration

- Select "Surface Area Configuration for Service and Connections"
Settings for "Surface Area Configuration for Service and Connections"
- In SQL> Database Engine>, click on Remote Connections
- Select “Local and Remote Connections”
- Click “Using TCP/IP and named pipes” and “Apply”

4.2 Installing MS-SQL 2008
Attention: if you are using MS SQL Express 2008, the user sa can be connected maximum one time
simultaneously. If you are using more than one connection from nPO, you should create one user
per connection.
Install the SQL server

Select features, but don't forget Studio
Define the Instance Name with no more than 5 letters up to nPO 4.1

Define the service owner
Select Mixed Mode and don't forget the Windows User

Assign Windows Account for service access

5. SQL table definition
For the HotBackup configuration we advise to define the 3 following databases:
• CMUM.mdf designated as CMUM
• Audit Trail designated as NPO_HAT
• Tag History designated as NPO_Hist
5.1 CMUM
CMUM contains the user-relevant data such as the user ID and name, password and password settings etc.
In order to protect these data, they are placed in a password-protected SQL table.
- Copy the database CMUM that you can find in the installation folder from nPO
novaPro Open\Utilities\Central UM DB\ to the wanted folder in your project or on the
SQL server.
Folder which contain the CMUM.mdf

- Attach a new table in MS SQL Management Studio.
Adding a new SQL table
- You must add the MDF file that was used under the name "CMUM".

SQL table configuration
- Let the standard name from the DB which is CMUM.

5.2 Audit trail
The Audit Trail lists user activities such as setpoint change, log in/out, password change, entering a zone
etc.
The "Audit Trail" table has to be created. In the database browser context menu, select "New Database".
Adding the Audit Trail table in SQL
- Give the name “NPO_HAT” to the Database.
- Select the path: for NPO_HAT and NPO_HAT_log.

- Click on OK.

5.3 Tag History
Add a new table for the Tag History in the same way as described for CMUM and Audit Trail.
- This table should also be created. To do it add a new database in the SQL
Management Console.
- The name must be NPO_HIST.
- Then choose the folder which will contain the database and the log.

- Then validate by clicking OK.

6. Connect novaPro Open to the SQL DB
Attention: if you are using the HotBackup functionality from novaPro Open, the points 6.1, 6.2 and
6.3 must be done on the master and the backup stations.
6.1 CMUM User Management
- Open the station properties menu.
- Select the user management and activate “Microsoft SQL Server”.
Data source definition for the user management data

- Choose the server and indicate the username (sa) and his password.
- Check “Synchronize” and, in the combined box “Synchronization options”, select “Overwrite
central database”. When you click on apply, a popup window will be opened. Click on “Yes”.
- In the combined box “Synchronization options”, select “Overwrite local database”, then click on
OK.

The programme has to be restarted for the changes to become effective.

6.2 Audit trail
- Open the station properties and select Audit Trail.
- Activate Audit Trail.
Audit Trail activation in novaPro Open
- Click on “Add data source”.

- Select “System data source”, then “Next”.
- Select “SQL server”, then “Next” and “Finalize”.

SQL server definition as data source for the Audit Trail
- Define one name for the data source, the description and the SQL server where novaPro
Open should be connected.
Data source definition in novaPro Open
- Choose “SQL server authentication”, indicate the username (sa) and his password. And
click on “Next”.

Authentication configuration for the data source
- Select the NPO_HAT table.
SQL table choice for the data source
- Select “Use regional settings” and “Perform translation”, then click on “Finish”.

- In the new window test the connection.
- If this message comes, it’s working.

SQL data source creation confirmation
- Validate the configuration after giving the username (sa) and password.
The programme has to be restarted for the changes to become effective.

6.3 Tag History – ODBC networking
The ODBC networking menu can be used to save historical data in various databases via Microsoft
ODBC.
- Open the station properties and then go on the “ODBC connectivity” tab.
- Check “Enable” and click on “Add data source”.
- Choose the system source.

- Choose SQL Server.
- Choose the server and give the login password for this conection.

- Choose “SQL server authentication”, indicate the username (sa) and his password.
And click on “Next”.
- Choose the NPO_HIST table.

- Activate the regional settings.
- Test again the connection.

- Give the login credential and check “Enable tag name logging”.

The programme has to be restarted for the changes to become effective.

7. Robocopy
After restoring the Master station, the Audit Trail and Tag History SQL tables are completed with the
temporary files. This synchronisation process is controlled by a PLC on the novaPro Open of the
Master station and is described here.
Directory "ODBC_Back Up" must be created in the project directory on the Master and Backup
stations. In Backup mode, the temporary files in the ODBC_Backup directory are saved on the Backup
station.
ODBC_Back Up directory with Tag History and Audit Trail temporary data

Robocopy.exe and exec_robocopy.bat in the project directory
PLC "EXE_SQL_BCK_PRG", created with the Codesys development tool, launches the
exec_robocopy.bat program in order to copy the ODBC_Back Up directory from the Backup to the
Master.

PLC for copying the ODBC_Backup directories from the Backup to the Master
Content of the exec_robocopy.bat file
As defined in the exec_robocopy.bat file, all the files in the ODBC_Backup directory are copied from
the Backup (PDM 2) to the ODBC_Backup from the Master (PDM 1).

8. Tips and tricks
8.1 Support cases
- "After the last backup to DVD (Nero) a blue screen appears. The backup was
aborted and novaPro Open has become very slow and inactive on PDM 1."
Solution: Check whether entries such as "init retain fails" are to be found in
errors.dat. If so, Wizretain.dat should be deleted.
- "On repeated occasions, incoming and outgoing unacknowledged alarms are
printed out only as outgoing."
Solution: The parameter "Suppress alarms" in nPoPRO should not be checked.
- "Non-synchronous events windows between all stations."
Solution: In the Events window > Filters > Filter Properties > Network: check "All
stations" or select all stations manually.
8.2 Poll Backup station status
The status of the Backup station can be polled with WizGetBackupMode (Wiz "Prefixes" up to nPo
Version 3.0 SP4) using SoftPLC or an add-on.
It is also possible to use System Tag WIZSYS_BACKUP or the "$Backup Application language tag"
on the Backup station.
These tags (read only) are set to 0 when the Backup station is in standby mode.
When the Backup station becomes active (Backup mode), the value of the tag is changed to 1. On the
Master station, these tags always have a value of 0.