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
+12-8Lines changed: 12 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,11 +7,11 @@ For larger databases this can conserve a lot of storage space for backups.
7
7
## Configuring number of backups
8
8
9
9
In your backup.config file you will need to set the variable `GHE_INCREMENTAL_BACKUP_MAX`.
10
-
This variable determines how many cycles of full and incremental backups will be performed before the next full backup is performed with another cycle of incremental backups.
11
-
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.
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.
12
12
13
13
Incremental backups require the previous snapshot backups before them to work.
14
-
Because of this, they do not follow the pruning strategy based on `GHE_NUM_SNAPSHOTS`.
14
+
This means they do not follow the pruning strategy based on `GHE_NUM_SNAPSHOTS`.
15
15
16
16
## Performing incremental backups
17
17
@@ -24,11 +24,15 @@ the program will detect whether it needs to performa full or incremental snapsho
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
26
26
## Performing incremental restores
27
-
to perform incremental restores:
28
-
`bin/ghe-restore --incremental -s <snapshot-id>.
29
-
the program will use the mysql folders from each previous incremental backup and the full backup to restore the database.
30
27
31
-
:warning: Incremental restores require the other snapshots in the cycle to complete a restore. Erasing snapshot directories that are part of a cycle corrupts the restore and makes it impossible to complete for the mySQL database.
28
+
To perform incremental restores:
29
+
30
+
`bin/ghe-restore --incremental -s <snapshot-id>`
31
+
32
+
The program will use the MySQL folders from each previous incremental backup and the full backup to restore the database.
33
+
34
+
:warning: Incremental restores require the other snapshots in the cycle to complete a restore. Erasing snapshot directories that are part of a cycle corrupts the restore and makes it impossible to restore for the MySQL database.
32
35
33
36
### Previous cycles
34
-
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.
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.
0 commit comments