This article describes best practice for upgrading a production server. 

We recommend installing ROCK (rather than DAILY) builds on production servers, depending on your appetite for new features vs stability.

For example let's say you're updating from an older ROCK build such as 2018.2 b20296 to the latest ROCK build (2019.1 b20430 at time of writing). 

The installation process itself is simply a case of installing "on top" of the previous installation. However, while we take great care to ensure upgrades are backwards-compatible (i.e. files created by the older app should be unaffected by the upgrade), for production systems you should take precautions of backing up Omniscope's managed data folders and configurations first. 

Note if you are downgrading your Omniscope installation, you must always take backups, and may need to restore previously created backups from the older version (which you should retain for some time); we do not aim for 'forwards compatibility'; it is quite possible that files created by newer versions will not be compatible with older versions, and problems may not be immediately apparent.

Upgrade process summary

  1. Quit Omniscope (stop the process or service); e.g. on Windows, right-click the blue system tray icon and choose "Exit"
  2. Backup files and configuration (see below)
  3. Install new version "on top"
  4. Start Omniscope
  5. Test your workflows execute and dashboards are displayed correctly
  6. Occasionally, report data must rebuild from execution data. This is only necessary in rare cases and typically only when downgrading Omniscope. See below.
  7. Keep the backup until the next upgrade, should you need to rollback at a later date.

What to back up

  • Your sharing folder, typically "<USER_HOME>/omniscope-server/files/".
    This contains all your project ".iox" files, and corresponding ".data" folders adjacent to each one, containing file-specific data (execution data, for example) that Omniscope manages.

  • The rest of the "<USER_HOME>/omniscope-server/" folder,
    e.g. config.xml containing the server global configuration.

  • Other internal Omniscope data in your user profile:
    Windows: <USER_HOME>\App Data\Local\Visokio
    Mac: /users/<username>/Library/Application Support/Visokio
    Linux: /home/<username>/.visokioappdata
    (this includes the report data that can be rebuilt from execution data as per below)

Fixing report data

If there has been a major update of 'monetdb', the columnar database used by default for reports, Omniscope should automatically handle the update. If there are problems, the report data can be rebuilt from scratch (this will take some time) from the execution data that will also be kept within the sharing folder ".data" folders. 

See this article for advice on data engine problems; in particular follow Section D for advice on how to let Omniscope fix your tables.