-yoption forces GBAR to skip interactive prompt questions by selecting the default answer. There is currently one interactive question:
gadmin config entry system.backup. At each prompt, enter the appropriate values for each config parameter.
<backup_tag>-<timestamp>, which is a subfolder of the backup repository.
System.Backup.Local.Enableis set to
true, the folder is a local folder on every node in a cluster, to avoid massive data moving across nodes in a cluster.
System.Backup.S3.Enableis set to
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.
<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.
gbar restoreon any node will restore the entire cluster.
<backup_tag>-<timestamp>) to be restored. When GBAR restore begins, it first searches for a backup archive exactly matching the archive name supplied in the command line. Then it decompresses the backup files 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 the backup archive is compatible with that current system. It will then shut down 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. Also, GBAR will notify the GST to load backup user data and copy the backup user-defined token/functions to the right location. When these actions are all done, GBAR will restart the TigerGraph servers.
gbar cleanupto delete the temporary files created during backup or restore operations: