confidential & proprietary. - iom.invensys.comiom.invensys.com/en/usergrouppresentations... ·...

Confidential & Proprietary.


eDNA Breakout Sessions

Maintaining Your eDNA System Pat Powers Matt Tomich


Pat Powers

- Technical Support Supervisor

- Started in Support at InStep in August 2011

- Background in IT

- Certified Support Manager

- Degree in Technical Management


Matthew Tomich - Technical Solutions Analyst

- eDNA Trainer

- Started with InStep 2011

- Attended last 4 User

Conferences

- Degree in CIS


Overview

●Best Practices ●eDNA Backups ●Monitoring Using Calc Services ●Finding Answers ●Questions


Best Practices


Server Health

●Monitor server health ●Processing power

●CPU usage below 70%

●Memory usage ●Hard Drive space

●below 80% disk consumption

●Disk I/O ●Consistent paging to disk


Server Health

●Scale server for growth ●Processor ●Memory ●Hard Drive space

●Virtual Machines

●Allocate sufficient resources


eDNA Communication

●Firewall open ports ●Services use UDP

●Recommend ports 6321 – 7000 ●SVCDIR uses 6321

●Databridging, Redundancy ●Communicate with TCP


Anti-Virus software

●Exclude Systems folder ●Slows processing ●Can cause caching

●History folders must be excluded ●Can cause data loss!


An Administrator Is Not The Administrator

●Microsoft Windows Security ●Server 2008, Sever 2012 ●Windows 7 +

● "Administrator" and "Administrators" are not the same

●You can be logged on as AN administrator and not have sufficient permission to install software


An Administrator or The Administrator ●Administrator is an account

●Default Administrator account on server ●Usually has FULL permissions

●Administrators is a group

●Member of the Administrators group ●You’ve been granted administrator privileges on that machine ●Administrator privileges can vary

●eDNA installations require Administrator permissions


Windows Patching

●Suggest staying up to date with latest Windows patches

●Patching eDNA Historian ●Stop “DNA Services” in Windows Service Manager ●Patch and restart the Historian server ●Start DNA Services” in Windows Service Manager ●Open eDNA Explorer and verify services are running


Windows Patching

●Patching Redundant eDNA Historian ●Patch Secondary first

●Stop “DNA Services” in Windows Service Manager ●Patch and restart the Secondary Historian server ●Start DNA Services” in Windows Service Manager ●Open eDNA Explorer and select Redundancy

– Verify that Primary services are green (Acting Primary) – Verify that Secondary services are yellow (Ready)


Windows Patching

●Patching Redundant eDNA Historian ●Patch Primary server second

●Stop “DNA Services” in Windows Service Manager ●Patch and restart the Primary Historian server ●Start DNA Services” in Windows Service Manager ●Open eDNA Explorer and verify services are running ●From Redundancy, manually fail services back to Primary


eDNA Releases ●Semi-annual releases

●Announced via e-mail ●Suggest staying within 2 versions of current release ●Version consistency

●New releases contain bug fixes and enhancements ● Improved performance ●New features

●many requested by our customers

●We recommend testing upgrades in QA/Dev environment


Review Release notes ●Release notes posted for each release

InStep Support site/eDNA/Product Release Notes


Review Release notes ●Release notes History available

InStep Support site/eDNA/Product Release Notes


Upgrading Client Tools ●Admin Client and User Client tools

● Install using .MSI from Support site ● Will automatically uninstall previous version ● Install updated required files

●UAC (User Account Control) settings set to minimum ● Prevents features from being available ● Allows installation to write to registry

InStep Support site/eDNA/Current Release/ – Admin Client Install.msi – User Client Install.msi – eDNA Client Tools Installation Guide


Upgrading Services

●Upgrading Services ●Don’t run services msi ●Swap executables ●Restart Service

InStep Support site/eDNA/Software/eDNA Service


Planning an Upgrade ●Support can help plan your upgrade

●Services upgrade ●History Conversion ●Moving to a new server

●Provide high level documentation

●Schedule a call to answer and questions or concerns

●Let us know when the upgrade is scheduled ●Support available to resolve issues


Planning an Upgrade ●Upgrade Service engagement available

●Services include ●Detailed upgrade plan specific to your environment ●Project Manager assigned ●Dedicated Technician ●System Documentation and Testing

●Contact your Business Development representative

●Not sure – contact Support to talk about your options


Licensing

●eDNA installs with a 45 day Demo license ●Recommend contacting support at time of installation

●Licenses are machine specific ●Moving to a new server requires a new license

●Virtual machines ●Adding resources may reset license ●Check license duration


Service screen

●Accessed through eDNA Explorer ●Per service ●Periodically monitor

●Health Check


Service screen

●Detailed messages ●Service errors ●Troubleshoot


Log files

●Two ways to enable ●From service screen (F9) ●From Config file (restart)

●Created daily ●Saved in service directory

●Saved as txt file


Log files

●When to run logging ●Troubleshooting

●Detailed Trace (F8) ●Records more info ● Larger file size

●Takes memory ●Keep eye on resources

●Overwrite each week


eDNA Backups


eDNA Services – Backup

●SVCDIR ●BOSS ●Security ●Point Database


eDNA Backup – SVCDIR

●SVCDIR ●SVCDIR.DB

●Recovery

●Stop eDNA Services ●Rename backup file ●Restart eDNA Services


eDNA Backup – Security ●Security

●EVENT.DB

●Recovery ●Stop eDNA Service ●Rename file backup ●Restart eDNA Service


eDNA Backup – Point Database

●Point Database CmCFG (CM.DB)

●Backup path defined in DBServ. Cfg ●CM.DB CM.DB.BAK


eDNA Backup – AppServ

●Application Database AppServ (BS.DB) ●Backup path defined in DBServ. Cfg ●BS.DB BS.DB.BAK


Manual backup – eDNA explorer

●Manual Import/Export ●SVCDIR ●BOSS ●REDUNDANCY ●SECURITY

●Control Toolbar ●Select specific service ● Import/Export


Manual backup - Point export

●Manual Point Import/Export ● eDNA Explorer ●CmCfg control

●Save point file locally

●Text format ●XML format


System Copy ●Allow users to backup eDNA environment ●Run batch file from command prompt ●Exclude certain file type


System Copy

●Example ●Save backup to desired path ●Backup .exe, .dll, .cfg, etc.


Network Backups ●Define backup working with IT

●Full – complete backup ● Incremental – backs up files that have changes since last backup (full or

incremental) ●Differential – backs up changes since last full backup

●What should be backed up ●Systems folder ●History ● eDNA Web Database backup

●Restoring from backup ●Performed by IT ●Recommend periodic restore testing


Backup History Database

●Three Step Process

1) Halt History Writes

2) Backup History

Segments

3) Resume History Writes


Halt History Writes ●Two Options to Halt History Writes A) LockHistory Utility

●Command Line Executable. ●Can be incorporated with Third Party Backup Solutions. ●READONLY mode: Do not allow History writes. ●LOCKDOWN mode: Do not allow History writes or reads.

B) Shutdown History ●Via Boss ●Trigger through Command Line or eDNA Explorer.


Halt History Writes C:\Systems> LockHistory.exe DEMO.HISTORY LOCKDOWN

History Health Icon L Lockdown Mode R ReadOnly Mode ♥ Normal Operation


Resume History Writes C:\Systems> LockHistory.exe DEMO.HISTORY RELEASE


Backup History Segments ●After History is locked, make a file copy of your modified History

segments.

●History Segment Manager ●Admin Client Tool ●History broken into segments (yearly)

●What segments do I need to backup?

●Mount older segments as READONLY. ●Only need to backup modified READWRITE segments.


Restoring History from backup

●Multiple options available ●Using Redundancy ●Data source/Cache files ● Importing History from different tiers ●Network backup


Monitoring eDNA Services


Monitoring eDNA services with Calc

●Service Status ●Stat = SVC_STAT(<Service Name String>)

STATUS DESCRIPTION -1 Service not defined in SVCDIR 1 Service defined but never started 2 Service is currently out of service 3 Service is currently failed 4 Service is running and OK


E-mail Notification with Calc ●Example Notification data point

static msgsent /* used to prevent multiple e-mail

messages from being sent */

if DNAGetRTValue("demo.calc.0to10") > 5 then /*

condition */

FROM$ = "eDNA"

TO$ = "[email protected]"

SUB$ = "eDNA Notification"

MSG$ = "The value of 0 to 10 is greater than 5"


E-mail Notification with Calc if msgsent = 0 then /* if an e-mail message has not yet been sent... */

ret = MAIL(FROM$,TO$,SUB$,MSG$) /* send e-mail message */

value$ = "SENDING MSG" /* set digital string when condition = true

and message has not yet been sent */

msgsent = 1 /* prevent additional messages from being sent while

condition = true */

else

value$ = "MSG SENT" /* set digital string when condition = true and

message has already been sent */

endif

else /* if condition = false */

msgsent = 0 /* allow e-mail message to be sent */

value$ = "OK" /* set digital string when condition = false */

endif


E-mail Notification with Calc

●Successful Example

●Notification condition successful

●Message sent


Resources for More Information


Documentation


Contacting Support…..

●Available 8:00 am – 5:00 pm Central

●E-mail – [email protected]

●Call – 312.894.7870 ●For urgent issues

mailto:[email protected]


Your Support Team


Support Goals ●Our goal is to resolve issues quickly and efficiently ●Provide best in class support ●Exceed customer expectations ●Constant improvement ●First point of contact

●Support ●Questions or concerns ●Upgrade planning ●Enhancement requests ●Redirect to other resources


Resolve Issues Quickly and Efficiently

●A detailed description of the issue.

●The sequence of events leading up to the issue. What steps were performed when the issue occurred?

●The versions of any components related to the issue. (RTS, History, API, Admin/Client tool, eDNA Web, PRiSM).

●A set of log files, if available.


Escalation Process

●1st level of escalation: Support - Pat Powers [email protected] , 312-894-7845

●2nd level of escalation: Support and Projects – Bob Lacy [email protected] , 312-894-7876

● If other escalation attempts do not adequately address your concerns, the Executive Team can be reached at – [email protected]

mailto:[email protected]?subject=Support Escalation

mailto:[email protected]?subject=Support Escalation

mailto:[email protected]


Summary ●Best practices

●Server health, communications, Windows patching ●eDNA version releases ●Planning an upgrade

●eDNA backups ●eDNA ●Network ●History


Summary

●Monitoring Services with Calc Service ●Example using the Notification service

●Contacting Support ●Information when contacting support ●Escalation process


Questions

confidential & proprietary. - iom.invensys.comiom.invensys.com/en/usergrouppresentations... ·...

Documents