sudo
access.jq
conda package is installed in your base environment.ae5-conda
environment mentioned in the prerequisites already contains
the backup script. If you choose to install the environment, skip ahead to
verify your installation.ae5_backup_restore
package into your base conda environment:
ae5_conda
installer file and move it to your master node.
Set the installer file to be executable, then run the script to install the ae5_conda
environment:
ae_backup.sh
script to create backup files of your cluster in the current directory:
ae5_config_db
file stores your Kubernetes resources and Postgres data.
The ae5_data
file stores your /opt/anaconda/storage
data.
-h|--help
: Prints help and exits.
-d <DIR>, --ae-data <DIR>
: Changes the location of the AE5 storage. The default location is /opt/anaconda/storage, and should not be changed when used on a Gravity cluster.
-b <DIR>, --backup-dir <DIR>
: Changes the location where the backup files are saved. The default location is the current directory. Use when the space available in the current directory is insufficient to hold the backup.
-s, --skip-clean
: If supplied, the script will not remove the intermediate files it generates during the backup process. This is useful for informational or debugging purposes.
-c, --config-db
: If supplied, the script will not create a data tarball, only the config/postgres tarball. This is useful if the script is combined with an alternate mechanism for taking snapshots/backups of the data.
-r, --repository
: If supplied, the script will include the full package repository in the data tarball. It doesn’t do this by default because the repository is likely to be large and incompressible.
-h, --help
: Prints help and exits.
-d <DIR>, --ae-data <DIR>
: Changes the location of the AE5 storage. The default location is /opt/anaconda/storage, and should not be changed when used on a Gravity cluster.
-b <DIR>, --backup-dir <DIR>
: Changes the location where the backup files are found. The default location is the current directory. Use when the space available in the current directory is insufficient to hold the backup.
-s, --skip-clean
: If supplied, the script will not remove the intermediate files it generates during the backup process. This is useful for informational or debugging purposes.
-u, --update-hostname
: If supplied and necessary, the script modifies the local hostname to match the backup content. Otherwise, the script preserves the local hostname.
-c, --config-only
: If supplied, the script only restores the configuration data (SSL, secrets, configmaps, and so on) It does not modify the Postgres database and the data.
-w, --wait
: When the system pods are restarted, wait for them to stabilize for exiting the script.
-p, --pause
: Leaves the cluster in a paused state upon completion of the restore process.
-y, --yes
: Restore function will not ask for confirmation before proceeding. Should be used with care.