Zoomdata Version

Upgrading the Zoomdata Server

You can upgrade your Zoomdata Server v2.3 or v2.4 to the current v2.5 release.

Starting with Zoomdata v2.5.3, the SQL connectors requires a JDBC driver to be configured before you can connect to your data source. You can download the driver from the vendor’s site. Be aware that you need to download and configure JDBC drivers for the following Zoomdata connectors:

If you are using one of the above data sources, you need to download and configure a JDBC driver as soon as your Zoomdata server has finished upgrading. For steps, see Add a JDBC Driver.

If you need to upgrade from Zoomdata v2.2, see Upgrading from Zoomdata v2.2 .


Prior to starting any upgrade, Zoomdata strongly recommends that you back up your metadata store first. Otherwise, you risk losing data during the upgrade process. For more information, see Backing Up and Restoring your Metadata.

The installer script works for the following environments:

  • Centos v6 and v7
  • Ubuntu v14.04 and 16.04

See System Requirements for recommended settings for deploying Zoomdata on-premise.

If you if have any of the above mentioned data sources that require a JDBC driver, you need to download and install the driver from the vendor's website.

The target server for the Zoomdata program should meet the following conditions:

  • Server is connected to the Internet
  • The user installing Zoomdata is able to use the 'sudo' command in the server

UPGRADE Instructions

In order to begin the upgrade process, you first need to receive the installation instructions from Zoomdata Support. This email contains the installation script that you use to run in the server where the Zoomdata environment will reside.

If you have not received the installation instructions, select the Support button on this page to open a ticket with Zoomdata Support.

Run the installation script.

You will receive an email from Zoomdata support with installation instructions and the command line that needs to be run. Enter the installation command into your target server to start the automated installation process. The following Zoomdata components are downloaded to your target server:

  • The Zoomdata Server
  • Scheduler service
  • Spark proxy service
  • Connector services
  • The Zoomdata Scheduler is a component within the Server used to run jobs that will refresh Zoomdata’s connection to the data source in asynchronous mode. For more information, see Using the Zoomdata Scheduler .
  • Zoomdata employs a 'Spark Proxy' component (or service) which runs as a separate process in one of the nodes in Zoomdata. For more information, see How Zoomdata Uses Apache Spark .

After the installation script has completed, it takes a few minutes for Zoomdata to complete its update of the metadata store. It is recommended to wait a few minutes before accessing Zoomdata from your web browser.

If you receive a message indicating that Zoomdata is not accessible yet, it may not have completed its setup yet. Please wait a few more minutes before trying again or opening a Support ticket. If you continue to have issues accessing Zoomdata from your browser, select the Support button on this page to open a ticket with Zoomdata Technical Support. For guidance on accessing Zoomdata, refer to the article Access Zoomdata from Your Web Browser .

The firewall setup should have been retained and the IP address remain the same, but see the following for more information:

If you are upgrading from v2.3 to v2.5, a health check report related to charts and dashboards is created. This report is provided in a dedicated file zoomdata-upgrade.log- which is located in the /opt/zoomdata/logs directory. If after upgrading from Zoomdata v2.3, you find there are issues with your charts and dashboards, then access this log file to determine the issues. If needed, open a ticket with Zoomdata Technical Support to help you troubleshoot these issues. This log file is not needed when upgrading from v2.4 to v2.5 since JSON schema is the same in both versions.