Backup and Restore
Introduction and Syntax
GBAR (Graph Backup And Restore), is an integrated tool for backing up and restoring the data and data dictionary (schema, loading jobs, and queries) of a single TigerGraph node. In Backup mode, it packs TigerGraph data and configuration information in a single file onto disk or a remote AWS S3 bucket. Multiple backup files can be archived. Later, you can use the Restore mode to rollback the system to any backup point. This tool can also be integrated easily with Linux cron to perform periodic backup jobs.
The current version of GBAR is intended for restoring the same machine that was backed up. For help with cloning a database (i.e., backing up machine A and restoring the database to machine B), please contact
The -y option forces GBAR to skip interactive prompt questions by selecting the default answer. There is currently one interactive question:
- At the start of restore, GBAR will always ask if it is okay to stop and reset the TigerGraph services: (y/N)? The default answer is yes.
Changes between v2.0 and v2.1
- For S3 configuration, the AWS access key and secret are not provided, then GBAR will use the attached IAM role.
- You can specify the number of parallel processes for backup and restore.
- If GSQL authentication is enabled, you must provide a username and password.
- A backup archive is stored as several files in a folder, rather than as a single file.
- Distributed backup performance is improved.
- To select a backup archive to restore, the full backup name must be specified.
Restore asks fewer interactive questions than before:
- The user must provide a full archive name; there is no option to select the latest from a set of archives.
- GBAR restore does not estimate the the uncompressed data size and check whether there is sufficient disk space.
GBAR Config must be run before using GBAR backup/restore functionality. GBAR Config will open the following configuration template interactively in a text editor. Using the comments as a guide, edit the configuration file to set the configuration parameters according to your own needs.
The backup_tag acts like a filename prefix for the archive filename. The full name of the backup archive will be <backup_tag>-<timestamp>, which is a subfolder of the backup repository. If
is true, the folder is a local folder on every node in a cluster, to avoid massive data moving across nodes in a cluster. If
is true, every node will upload data located on the node to the s3 repository. Therefore, every node in a cluster needs access to Amazon S3. If IAM policy is used for authentication, every node in the cluster needs to be attached with the IAM policy.
GBAR Backup performs a live backup, meaning that normal operations may continue while backup is in progress. When GBAR backup starts, it
sends a request to gadmin
, which then requests the GPE and GSE to create snapshots of their data. Per the request, the GPE and GSE store their data under GBARâ€™s own working directory. GBAR also directly contacts the Dictionary and obtains a dump of its system configuration information. In addition, GBAR records TigerGraph system version. Then, GBAR compresses each of these data and configuration information files in tgz format and stores them in the <backup_tag>-<timestamp> subfolder on each node. As the last step, GBAR copies that file to local storage or AWS S3, according to the Config settings, and removes all temporary files generated during backup.
The current version of GBAR Backup takes snapshots quickly to make it very likely that all the components (GPE, GSE, and Dictionary) are in a consistent state,
but it does not fully guarantee consistency.
Itâ€™s highly recommended when issuing the backup command, no active data update is in progress. A no-write time period of about 5 seconds is sufficient.
Backup does not save input message queues for REST++ or Kafka.
List Backup Files
This command lists all generated backup files in the storage place configured by the user. For each file, it shows the fileâ€™s full tag, fileâ€™s size in human readable format, and its creation time.
Restore is an offline operation, requiring the data services to be temporarily shut down. The user must specific the full archive name ( <backup_tag>-<timestamp> ) to be restored. When GBAR restore begins, it first searches for a backup archive exactly matching the
supplied in the command line. Then it decompresses the
to a working directory. Next, GBAR will compare the TigerGraph system version in the backup archive with the current system’s version, to make sure that backup archive is compatible with that current system. It will then
the TigerGraph servers (GSE, RESTPP, etc.) temporarily. Then, GBAR makes a copy of the current graph data, as a precaution. Next, GBAR copies the backup graph data into the GPE and GSE and notifies the Dictionary to load the configuration data. When these actions are all done, GBAR will restart the TigerGraph servers.
The primary purpose of GBAR is to save snapshots of the data configuraton of a TigerGraph system, so that in the future the same system can be rolled back (restored) to one of the saved states. A key assumption is that Backup and Restore are performed on the same machine, and that the file structure of the TigerGraph software has not changed. Specific requirements are listed below.
Restore Requirements and Limitations
Restore is supported if the TigerGraph system has had only minor version updates since the backup.
- TigerGraph version numbers have the format X.Y[.Z], where X is the major version number and Y is the minor version number.
- Restore is supported if the backup archive and the current system have the same major version number AND the current system has a minor version number that is greater than or equal to the backup archive minor version number.
- Backup archives from a 0.8.x system cannot be Restored to a 1.x system.
Backup archive’s system version current system version Restore is allowed? 0.8 1.0 NO – Major versions differ 1.1 1.1 YES – Major and minor versions are the same 1.1 1.2 YES – Major versions are the same; current minor version > archived minor version 1.1 1.0 NO – Major versions are the same; current minor version < archived minor version
Restore needs enough free space to accommodate both the old gstore and the gstore to be restored.
GBAR Detailed Example
The following example describes a real example, to show the actual commands, the expected output, and the amount of time and disk space used, for a given set of graph data. For this example, and Amazon EC2 instance was used, with the follwing specifications:
Single instance with 32 vCPU + 244GB memory + 2TB HDD.
Naturally, backup and restore time will vary depending on the hardware used.
GBAR Backup Operational Details
To run a daily backup, we tell GBAR to backup with the tag name
The total backup process took about 31 minutes, and the generated archive is about 49 GB. Dumping the GPE + GSE data to disk took 12 minutes. Compressing the files took another 20 minutes.
GBAR Restore Operational Details
To restore from a backup archive, a full archive name needs to be provided, such as
. By default, restore will ask the user to approve to continue. If you want to pre-approve these actions, use the “-y” option. GBAR will make the default choice for you.
For our test, GBAR restore took about 23 minutes. Most of the time (20 minutes) was spent decompressing the backup archive.
Note that after the restore is done, GBAR informs you were the pre-restore graph data (gstore) has been saved. After you have verified that the restore was successful, you may want to delete the old gstore files to free up disk space.
Performance Summary of Example
|GStore size||Backup file size||Backup time||Restore time|
|219GB||49GB||31 mins||23 mins|