Customers
User information
 Loading ...
Show article in Knowledge Base

 Maintenance work Export knowledge base Export     SubscribeSubscribe      Show article info

The following actions are the required maintenance actions that your Operations Technician have to perform regularly if you have purchased an installed server version of VisionFlow:

 

  • Document your system setup, the different servers and components used, as well as their dependencies
  • You need have processes and procedures in place to guarantee system stability and manage your system efficiently
  • Backup your server, files and database regularly so that nothing is lost in case of a crash. We recommend nightly full database backups and transaction log backups every 5-10 minutes
  • Execute nightly database jobs:
    • Check db
    • Re-index nightly or weekly
    • Execute other maintenance jobs such as Update Statistics (on MS SQL Server) regularly (nightly if you can)
    • For MySQL : See mysqlcheck (analyze + optimize) https://dev.mysql.com/doc/refman/5.7/en/mysqlcheck.html
  • Continually check the VisionFlow log files for any serious errors and contact support@visionflow.com if you find any
  • Make sure that the Recent Activity portlet is visible on your dashboard and that you check and follow up any System event messages
  • Continually check so that the log-files don't get too big, if so then stop VisionFlow, remove the files, and then start VisionFlow again
  • Continually check so that the capacity of the server is sufficient (Memory, CPU, disks, network IO) and don't negatively affect performance
  • Restart the VisionFlow Application Server (Apache Tomcat) from time to time, at least once a month is recommended
  • Also make sure that you set up Monitoring for VisionFlow and dependent components, for example by using Nagios, OP5, SCCM or similar tools. We strongly recommend that you at least monitor:
    • Network access between server TCP/Ping and all components
    • DNS lookups for involved hostnames
    • Protocols and ports for example HTTP/HTTPS access to VisionFlow, and SMTP/IMAP access to email servers
    • Available and used memory, including RAM memory and tomcat heap memory
    • Available and used CPU, including total number of processes
    • Available and used disk space on all disks
    • Disk IO on all disks used. Check available vs consumed IO. It is also important to monitor disk swapping 
    • Network IO between components and between user and VisionFlow
    • Deadlocks in database
    • Long-running/expensive queries in the database
    • Database maintenance tasks, e.g. to make sure CheckDB, Reindex and Update Statistics jobs are functioning
    • Full and transaction log backups, e.g. last run status and estimated time to run
    • Test that service components are up/down, such as Tigase, ElasticSearch and Centrifugo if they are used.
  • Use Java Mission Control if you want to get detailed knowledge of the Java/tomcat server performance. See https://www.oracle.com/java/technologies/jdk-mission-control.html
  • Upgrade VisionFlow when new versions are released to make sure you do not run a too old version.
    A minimum of upgrading 1 time every year is required to be able to receive support, but we strongly recommend that you upgrade at least 2 times or more every year.
  • Upgrade all components required by VisionFlow to the latest version, such as Apache Tomcat 8.5, Java 11, ElasticSearch 7.4 and Nginx 

User comments
 Loading ...