You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/incremental-mysql-backups-and-restores.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
# Incremental MySQL Backups and Restores
2
2
3
3
Customers who have large MySQL databases who wish to save storage space can use the `--incremental` flag with `ghe-backup` and `ghe-restore`.
4
-
Using this flag performs backups for other parts of GHES as normal, but only performs a MySQL backup of the changes to the database from the previous snapshot.
4
+
Using this flag performs backups for other parts of GHES as normal, but only performs a MySQL backup of the changes to the database from the previous snapshot.
5
5
For larger databases this can conserve a lot of storage space for backups.
6
6
7
7
## Configuring number of backups
8
8
9
-
In your backup.config file you will need to set the variable `GHE_INCREMENTAL_BACKUP_MAX`.
9
+
In your backup.config file you will need to set the variable `GHE_INCREMENTAL_MAX_BACKUPS`.
10
10
This variable determines how many cycles of full and incremental backups will be performed before the next full backup is created.
11
-
For example, if `GHE_INCREMENTAL_BACKUP_MAX` is set to 14, backup-utils will run 1 full backup and then 13 incremental backups before performing another full backup on the next cycle.
11
+
For example, if `GHE_INCREMENTAL_MAX_BACKUPS` is set to 14, backup-utils will run 1 full backup and then 13 incremental backups before performing another full backup on the next cycle.
12
12
13
13
Incremental backups require the previous snapshot backups before them to work.
14
14
This means they do not follow the pruning strategy based on `GHE_NUM_SNAPSHOTS`.
@@ -19,7 +19,7 @@ To perform incremental backups:
19
19
20
20
`bin/ghe-backup --incremental`
21
21
22
-
the program will detect whether it needs to performa full or incremental snapshot based on what is currently in `GHE_DATA_DIR`.
22
+
the program will detect whether it needs to performa full or incremental snapshot based on what is currently in `GHE_DATA_DIR`.
23
23
24
24
To see what snapshots are part of your full and incremental backups, you can reference `GHE_DATA_DIR/inc_full_backup` and `GHE_DATA_DIR/inc_snapshot_data`, respectively.
25
25
@@ -35,4 +35,4 @@ The program will use the MySQL folders from each previous incremental backup and
35
35
36
36
### Previous cycles
37
37
38
-
To ensure there is a rolling window of mySQL backups, incremental MySQL backups from the cycle before the current one are kept. Those snapshots are pre-pended with `inc_previous`. To perform a restore from there, just use the full directory name for the snapshot id.
38
+
To ensure there is a rolling window of mySQL backups, incremental MySQL backups from the cycle before the current one are kept. Those snapshots are pre-pended with `inc_previous`. To perform a restore from there, just use the full directory name for the snapshot ID.
0 commit comments