1 / 34

Comprehensive Troubleshooting and Backup Guide for OSIsoft PI System

This guide provides essential tips and best practices for troubleshooting the OSIsoft PI System, focusing on holistic strategies and resource utilization. It explores key troubleshooting techniques, including log file analysis, backups, and buffering systems to prevent data loss. Additionally, it emphasizes the importance of archive sizing and maintaining an efficient network. Users are encouraged to understand their systems' connections, utilities, and resources to enhance performance. This is a vital resource for anyone looking to optimize their PI System setup.

soleil
Download Presentation

Comprehensive Troubleshooting and Backup Guide for OSIsoft PI System

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Tips from the Trenches Rebekah Atkinson Steve Nye, Kathy Kennedy

  2. Overview • OSI Resources • Troubleshooting – The Big Picture • Backups • Buffering • Archive Sizing • Q&A

  3. OSI Resources

  4. OSI Resources • Log Files • PIPC.Log (client & server) • NT only, usually located in \PIPC\Dat • PIMessLogFile • Unix only, located in $PIHOME/log • PI Server Log • PI - Healthcheck • PIGetMsg (PI3) • PISysMgr:PIMessLog.Txt (PI2)

  5. OSI Resources • Documentation • Interface Manuals (interfaces.osisoft.com) • Point attribute section • Startup file flags section • Troubleshooting section • Client Manuals • Server Manuals

  6. OSI Resources • Support Web Site (support.osisoft.com) • Online Call Center • Tracking of calls • New call entry • Searchable knowledge base • Bug reports • Engineering Plan • New Release Announcements • Feel Free to call us at Tech Support

  7. OSI Resources • Support Web Site (support.osisoft.com) • Online Call Center • Tracking of calls • New call entry • Searchable knowledge base • Bug reports • Engineering Plan • New Release Announcements • Feel Free to call us at Tech Support

  8. Troubleshooting The Big Picture

  9. Consider Big Picture • Ask yourself… • Did it ever work? • If so, what changed? • New software? New hardware? Etc… • Use Log Files to help isolate problem • No errors in client logs - Server problem • Always an error message somewhere! • Know your utilities

  10. Know Your Nodes

  11. Connection Troubleshooting

  12. Common Network Issues • DNS • If DNS is slow, connection may time out • Check HOSTS file • Multiple NIC cards • WAN traffic • Know your routers! • Port 5450 not initialized

  13. Backups

  14. Backups • Archives • Nightly & After Shift • Pi\dat Directory • Nightly & when server is shutdown • Site specific files & log files • Nightly • Recommend Test Recovery

  15. Backups • Known problems with PI 3.2 SR1 Script • Piartool –be ignored if system is busy • One Subsystem would stop while another was starting • New Beta Script • Verify that the subsystem is responsive • Schedule piartool -be to run 30 minutes after backup

  16. Example Script Change Rem Backup files owned by pibasess %BinPath%\pibasess -stop set BaseFiles=pipoints.dat piptattr.dat piptclss.dat pidigst.dat pidignam.dat piusr.dat piusrgrp.dat piusrctx.dat piptunit.dat piptalia.dat for %%i in (%BaseFiles%) do ( copy %DatPath%\%%i %BackupPath% ) Rem Restart pibasess and wait for it to become responsive Rem Record timestamps before and after to document the time this requires %BinPath%\pibasess -start %BinPath%\pidiag -t "*" %AdmPath%\piartool -block pibasess -verbose %BinPath%\pidiag -t "*"

  17. Buffering

  18. Buffering Basics • Why Buffer? • Avoid data loss during PI server shutdowns • Optimize your PI network transactions • Faster throughput • Set up a PI-API node • Data collection is not affected by the PI server

  19. Configuring Buffering • Must configure PICLIENT.INI • Turn Buffering ON • Define Maximum Buffer Size Size for down time and recovery time (size in KB) • Define how frequently it will attempt to reconnect (time in seconds)

  20. Example PICLIENT.INI [APIBUFFER] BUFFERING=1 MAXFILESIZE=500000 RETRYRATE=120

  21. Buffering Issues • Remember Configuration required, NT/Unix • Have plenty of disk space available • Buffering isn’t working? • Check BufServ Service Login • Make sure /host entry matches Default PI Server in PILOGIN.INI • All API programs must be stopped before bufserv can be restarted • Use bufutil program

  22. BUFUTIL Example

  23. Archives

  24. Archive Sizing • Why Change Sizes? • Added a new interface • Added more tags to an existing interface • Changed exception & compression on many tags • Added Performance Equations, Totalizers, Alarm tags, and/or Manual Entry tags

  25. Archive Sizing • Rules of Thumb… • 10-20 MB per 1000 tags • Smaller than the system RAM • Smaller than the backup media

  26. Example Bat File REM Create New Archives REM Specify path and size. d:\pi\adm\piarcreate d:\pi\archives\piarch.004 50 d:\pi\adm\piarcreate d:\pi\archives\piarch.005 50 d:\pi\adm\piarcreate d:\pi\archives\piarch.006 50 REM Register the new archives d:\pi\adm\piartool -ar d:\pi\archives\piarch.004 d:\pi\adm\piartool -ar d:\pi\archives\piarch.005 d:\pi\adm\piartool -ar d:\pi\archives\piarch.006

  27. Conclusion • Know Your Resources • Consider the Big Picture • Develop Your Backup Strategy • Buffer Your Data • Optimize Your Archive Size

  28. Questions??? • Ready for lunch? • (if you applaud, we will let you go to lunch)

More Related