Pulse DRC Guide

8/16/2019 Pulse DRC Guide

1/15

Pulse 2.0 DRC 1

PulseSCADA/HMI

Version 2.0

Disaster Recovery Control Guide(DRC)

January 2013


2/15

Pulse 2.0 DRC 2

Copyright

The information in this document is subject to change without prior notice and doesnot represent a commitment on the part of AFCON Control and Automation LTD.,AFCON Software and Electronics Division.

No part of this document may be used or reproduced in any manner whatsoeverwithout written permission from AFCON Control and Automation LTD., AFCONSoftware and Electronics Division.

The software described in this document is furnished under a license agreement ora non-disclosure agreement.

The software may be used or copied only in accordance with the terms of theagreement. It is against the law to copy this software on any other medium for anypurpose other than the purchaser's personal use.

Copyright 2012 AFCON Control and Automation LTD., AFCON Software andElectronics Division.

All rights reserved.

Pulse logos are registered trademarks of AFCON Control and Automation LTD.,AFCON Software and Electronics Division.

Windows is a registered trademark of Microsoft Corporation in the United Statesand other countries.


3/15

Pulse 2.0 DRC 1

Table of ContentsCopyright ..............................................................................2Introduction ..........................................................................2High Level Overview ............................................................... 3System Diagram .................................................................... 4

Pulse Server Configuration ...................................................... 4


4/15

Pulse 2.0 DRC 2

Introduction

The Pulse Disaster Recovery Control (DRC) Station (a feature, system component),is a system level backup and restore capability. This capability gives the Pulsesystem an integrated, simplified backup and restore as well as disaster recovery

operation (continuity). This feature is beyond the Hot Redundancy capabilityalready available for Pulse servers. DRC adds another Pulse server station with aserver and a client in one computer. This solution is designed to assure operationof critical systems at all times. The feature is simple to configure, runstransparently from normal operation and does not require any additional hardware(redundant switches, redundant networks, redundant storage), additional outsideapplications, or virtualization platforms. It is an economic solution alleviating acritical system availability challenge when disaster strikes.

Backup and restore operations can be performed externally from standard Pulsesystem operation. Users can perform these operations on a file, directory or disk

level. Many commercial products backup and restore a running system, evenmission critical systems. Yet, the Pulse system as a controller for large installationsneeds to offer more resilience. The Pulse DRC feature uses internal files andoperation states to assure fast and reliable backup and restore. Each project's filesare transferred to the DRC Station at a set period of time, usually set in minutes.DRC Station monitors the main server operation and takes over when failure isdetected. Since the DRC solution is an integrated into the Pulse system, operationrestore is seamless and takes over from the last known state.

The Pulse DRC solution is not intended to replace a redundant fail-over, highavailability (HA) secondary server. A separate, redundant server solution is alsooffered in the Pulse system. In the case of the redundant HA solution, only a failingserver or network communication to the server (i.e. failure of a network switch) ishandled by a second Pulse server. In the case of Pulse DRC, the Pulse server, Pulseclient and network operation can be recovered.

The new Pulse DRC server feature is designed to assure system operation whenboth Pulse servers (primary and redundant) fail (in case of a redundant systemconfiguration). In case of catastrophic power failure, facility failure or networkconnection failure, the Pulse DRC server can still keep a system operational(monitor and control SCADA controllers). These failures are usually referred to asdisaster condition, which affect a geographic or functional area in a system. Usuallya site wide failure due to physical event (flood, fire, power failure, attack, etc.) is

considered a disaster condition. Failures of large network sections due toequipment or external factors are also considered disaster condition.


5/15

Pulse 2.0 DRC 3

High Level Overview

Pulse DRC solution is an additional server and client node (i.e separate hardware).

The DRC station contains a copy of the project running on the primary (active)Pulse server. It connects to the primary system and keeps a snapshot of thesystem, database and operating state, through FTP file transfers. When a disasterstate occurs, system operation stops on the primary server. Operation of thesystem: communication on the Controller TCP Network and communication on thePulse client LAN is transferred to the Pulse Server running on the Pulse DRC station.

The Pulse DRC station includes both one Pulse server instance and one Pulse clientinstance in one computer. Each primary Pulse server runs a DRC Agent whichsynchronizes operation with the Pulse DRC server. During normal operation (nonedisaster state) a DRC Agent synchronize data and state with the Pulse DRC Server.

During DRC configuration, synchronization parameters such as file locations,synchronization time period (how often a state is backed up, in seconds orminutes), length of time a backup set is stored (number of days), as well as otherparameters are configured. DRC agents start operation at a system startup.

The Pulse DRC feature is designed to keep a site operating when a large systemfailure occurs. It is designed to give operators a way to bring up the failing systemwhile the controllers are still being monitored by the Pulse server. Pulse DRC alsogives operators full client operation in order to monitor and control systemoperations. This capability is vital in mission critical deployments where there isabsolute need to keep controllers running nonstop. The DRC is also crucial indeployments where control capability is mission critical, where a Pulse monitor or

control failure can cause catastrophic results.


6/15

Pulse 2.0 DRC 4

System Diagram

The existing Pulse client-server system configuration (topology) stays the same(right side of the figure below.) The addition of Pulse DRC station component (anode), simply connects to the existing system to a new server. Notice the DRC

Agent (box representing processes) added in the Main server instance. Theprocesses related to DRC feature are shown in the boxes next to each Pulse Server.DRC Agent runs on each machine. FTP Server and FTP Download processes areused to transfer blocks of data from each machine to the DRC Station. DRC Agentsare key components to transferring data and state from normal operation to DRCoperation (disaster state) and back once the main (primary) Pulse server isoperational again. This simplified diagram applies to standard configurations withmultiple clients and server instances. This configuration works with a single mainPulse server as well as with redundant fail over HA server topology.

Pulse Server Configuration

Preparation for DRC configuration using a wizard:

Create a project configuration file with a minimal set of folders set (category.)

Include the database without log tables or history files. This DRC configuration filewill not be backed up.


7/15

Pulse 2.0 DRC 5

Create a new project using the AFCON Project setup utility:

Start > AFCON Pulse > Pulse Setup > Project

Install windows FTP feature on the primary Pulse server. (Notice how FTP server

needs to be installed even if IIS is installed. This process is described in detail onthe Microsoft knowledge base. Search for "setting up ftp server")

Pulse DRC Configuration Wizard

1 Start the Pulse DRC Configuration Wizard:

Start > AFCON Pulse > Pulse Setup > DRC Configuration


8/15

Pulse 2.0 DRC 6

The wizard is used for DRC Server and DRC Station configuration as well as toremove DRC configuration parameters.

To configure DRC Server parameters,

Select the DRC Server > Next

The DRC wizard will configure files for the Primary Pulse Server. This is the serverrunning Pulse at normal operation (not disaster condition.)

To configure DRC Station parameters:

Select the DRC Station > Next

The DRC wizard will configure files for the DRC Pulse Station. This is the serverrunning Pulse at a disaster condition operation.

To delete the DRC configuration completely:

Select the Remove DRC Configuration > Next

The DRC wizard will delete configuration files for the DRC Pulse Station and all thePulse servers.

2. Configure the DRC Server [Dialog Box] start a multi step wizard:

Select the DRC Server > Next


9/15

Pulse 2.0 DRC 7

Create/Select DRC Backup Settings:

1 Settings name: Select a backup settings script name, this will load the localpath from the settings, and the virtual directory name from the project nameof the script ("DRC"+Projectname)

2 Create settings […]: Will execute the backup and restore wizard in a DRCmode, that will check the Save Backup settings checkbox and will have defaultscript name ("DRC"+ProjectName) (this is the button with three dots […])

3 Refresh button: Will reload script names

4 Backup Interval: The agent will execute an automated backup on every n minutes.

FTP Setting (these are parameters for the DRC Station to FTP into the Pulse Server)

5 Local Path: The backup file will be stored in this path, and the wizard willcreate an FTP virtual directory to this path. By default this data will beextracted from the selected backup settings definitions.

6 Server Name: The FTP server name, by default is the machine name.


10/15

Pulse 2.0 DRC 8

7 Virtual Folder Name: The FTP virtual directory name that the wizard willcreate.

8 Anonymous User: A security level flag, check if you do not need a FTPpassword protection.

9 FTP User Name: If not anonymous, local machine user name.

10 FTP Password: If not anonymous, local machine password.

3 Configure History rules [Dialog Box]:

Manage history files to be included:

1 Override History Category: If Checked - Will unselect the history category fromthe selected backup settings script, and add individual Include Files rules ofhistory files in Last n days.

2 Backup history files of _ _ [number] last days: Before each automated backup,

the agent will evaluate the history files in Last n days. These will be saved intothe directory parameterized in the backup configuration script.


11/15

Pulse 2.0 DRC 9

4 Finishing the DRC Configuration Wizard [Dialog Box]:

Complete the DRC Configuration process and start the DRC operation:

1 Summary: Shows the DRC Type, the FTP URL and the local backup pathlocations. Verify all the parameters and go back if they need correction.

2 Export DRC Configuration: Will create a DRC configuration for DRC stations.

Use this file, by copying to the local machine:C:\Afcon\Pulse\ProjectName\Utilities

3 Finish button will complete the DRC configuration process:

Check if FTP Feature is installed

Create FTP Virtual directory

Configure the DRC Agent to run at pulse startup

Stop DRC Agent if running


12/15

Pulse 2.0 DRC 10

Run DRC Agent

5 Configure the DRC Station [Dialog Box] start a multi step wizard:

Create/Select DRC Station Backup Settings:

Select the DRC Station > Next (from the first DRC dialog box)

FTP Settings:

1 FTP server name: The DRC Server name, the station will download from thisftp server name the backup file.

2 Virtual Folder Name: The virtual directory name you entered in the drc serverwizard, by default it's ("DRC"+Projectname)

3 Anonymous User: The security level you selected on the DRC server sidewizard. Add a User and Password if needed.

4 User Name: The ftp user name you selected on the DRC server side wizard.


13/15

Pulse 2.0 DRC 11

5 Password: The ftp password you selected on the DRC server side wizard.

6 Local Path: The backup file will be downloaded from the ftp server into thislocation.

7 Project Name: Read only- the current project.

8 Password Protected: Password for backup file if needed.

9 Enter Password: Supply the project's password if needed.

10 Modify database connection string: Check and modify the connection string.

11 Oracle Database Administrator Login, User Name: For Oracle database, supplythe administrator User Name.

12 Password: Enter the Administrator Password.

6 Configuring the DRC Station Wizard, finishing the DRC Station Configuration:

Complete the DRC Configuration process and start the DRC operation:


14/15


15/15

Pulse 2.0 DRC 13

8 Workstation Network Disconnection Dialog Box:

DRC Station to DRC Agent network reconnect:

1 Start DRC Station button will perform the following:

Will be visible if the DRC agent is running on this machine and thecorrect project name has the same name.

On activation of DRC station:

Local station server will start.

Local station workstation will start.

The disconnected workstation will be close.

2 Show Services: Will open the Windows Task Manager to the Processes tab.

3 Close Workstation: Closes the workstation.

Pulse DRC Guide

Documents

Transcript of Pulse DRC Guide