Backup Configuration Parameters¶
Customer Managed Applies to customer-managed instances of Alation
The information on this page is given for reference only. Do not modify the parameters listed in this table unless you follow specific instructions, for example:
Define the Number of Backups to Retain (Backup V1, Backup V2)
Note
Modifying alation_conf parameters without specific instructions is not a safe action. For more information about alation_conf, see Using alation_conf.
Jump to the table for your current backup tool:
Backup V2 Configuration Parameters¶
Parameter |
Value |
Description |
---|---|---|
|
|
Enables incremental backups. No restart is required when the value is changed. |
|
Number |
Sets the number of incremental backups per full backup. No restart is required when the value is changed. Default = 0, which means full backups |
|
Path inside the Alation shell |
Default: /data2/tmp/ Sets the working directory for the backup process. No restart is required when the value is changed. |
|
Path inside the Alation shell |
Default: /data2/backup/ Sets the backup storage directory on the Alation host. Compressed backup files are created in this directory. No restart is required when the value is changed. |
|
Number |
Defines the number of backups to keep on the backup disk. Default: 5. No restart is required when the value is changed. |
|
Path inside the Alation shell |
Example: /data2/backup/<file_name.tar> Path to the backup file to be used during the restore. |
|
Number 0-60 for minutes of of an hour |
Default: |
|
Number 0-23 for hours in a day |
Defines hour for the backup schedule
Default: |
|
Comma separated values for days of week |
Defines days for the backup schedule.
Default: |
|
True |
Do not modify manually. Stores the status of the backup process on an instance. If set to False, the Alation instance is not backed up, which is an unsafe practice. |
|
False |
Do not modify manually. Stores the status of the Backup V2 feature on an instance. True means enabled. False means disabled. |
|
True |
Enables the backup for the PostgreSQL component |
|
True |
Defines whether or not to launch the post script after the backup creation |
|
Path to the script |
/data1/site_data/s3_backup_sync.sh %f The post script is used to upload the backup .tar file to Amazon S3. It is possible to use another cloud storage. Add a custom script and provide the path to this script. |
|
|
Time in seconds. Defines how long Chef waits to run commands. Backups might fail if this is too short. |
|
|
Defines what ionic value to use to not overload the disk. |
|
|
Defines what content to exclude from the backup of the site_data folder. |
|
|
Uncompressed file space of backup file verified during restore. Set automatically and should not be modified manually. |
|
Number |
Number of incremental backups completed including the initial full backup. Should not be set manually. |
Backup V1 Configuration Parameters¶
Attribute |
Value |
Description |
---|---|---|
|
|
Defines whether the backup will be compressed. |
|
Number |
Defines the number of backups to keep on the backup disk. |
|
|
Defines what not to backup in the site_data folder. |
|
/path/to/backup |
Defines what backup file to use for restoring. |
|
|
Defines what ionic value is used. |
|
|
Defines the compression level for the pg_backup tool. |
|
Time in seconds. |
Defines how long chef waits to run commands. Backups may fail if this time is too short. |
|
/path/to/dir |
Defines which directory the backups are saved too. |
|
/path/to/dir |
Defines the staging directory where backups are extracted. |
|
|
Defines if backups are enabled. |
|
3000 (48GB) |
Defines the number of WAL segments to retain. This is useful if Postgres compression is enabled. |
|
|
Defines minutes of the backup schedule. |
|
|
Defines the hour for the backup schedule. |
|
Comma-separated values for Sunday to Saturday |
Defines the days for the backup schedule.
Default: |
|
|
Defines wether or not to launch the post backup script. |
|
Path with |
Defines the path to the post backup script. |