Upgrading an Existing Installation
This page describes the steps to upgrade an existing installation of TigerGraph to TigerGraph 3.5.
If you are upgrading from a version older than 3.2:
First perform a backup and a restore using GBAR (Graph Backup and Restore) on your existing installation. This step is necessary because TigerGraph 3.2 made major changes to the Graph Storage Engine and a restore is needed to remove certain files that would make the upgrade operation fail.
After restoring the backup, ensure that there are no vertex inserts or deletions before starting the upgrade.
Any 3.x version of TigerGraph can be upgraded to another v3.x version by
running the installation script with the upgrade(
Download the latest version of TigerGraph to your system.
Extract the tar file.
Run the installation script under the Linux user created during installation with the upgrade flag (
-U) that was extracted from the tar file:
$ ./install.sh -U
|Please upgrade from the most recent patch version in any minor release. If you are upgrading from a version that does not have the most recent patches applied to its minor version, upgrade to the most recent patches first before upgrading to another minor or major version. For example, if you are upgrading from 3.1.3 to 3.5, upgrade to 3.1.6 first using the installation script and then upgrade to 3.5.
Please contact TigerGraph Support to coordinate upgrading to TigerGraph version 3.5 if you are currently using a 2.x version of TigerGraph. Even though all the steps are documented, it is strongly recommended that you review the process with the TigerGraph Support team.
Upgrading the Developer Edition or migrating to another edition are not supported.
For detailed upgrade procedures, see our support article on the 2.6.x to 3.x upgrade flow
If you want to upgrade your Cloud Marketplace image from v2.x on any cloud platform, please open a support ticket for instructions and assistance.
TigerGraph supports downgrading within the same minor version. For example, going from 3.5.3 to 3.5.0 is supported, while downgrading from 3.5.3 to 3.4.0 is not.
The downgrade process involves using the
gadmin config command to change the AppRoot directory as described here: Change tmp/app/data root directory.