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/how-tos/encrypt-backup.md
+44-7Lines changed: 44 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -1,30 +1,39 @@
1
1
---
2
-
title: Encrypt backups using GPG
2
+
title: Encrypt backups
3
3
layout: default
4
4
parent: How Tos
5
5
nav_order: 8
6
6
---
7
7
# Encrypt backup
8
8
9
-
The image supports encrypting backups using GPG out of the box. In case a `GPG_PASSPHRASE` environment variable is set, the backup archive will be encrypted using the given key and saved as a sql.gpg file instead or sql.gz.gpg.
9
+
The image supports encrypting backups using one of two available methods: GPG with passphrase or GPG with a public key.
10
+
11
+
12
+
The image supports encrypting backups using GPG out of the box. In case a `GPG_PASSPHRASE` or `GPG_PUBLIC_KEY` environment variable is set, the backup archive will be encrypted using the given key and saved as a sql.gpg file instead or sql.gz.gpg.
10
13
11
14
{: .warning }
12
-
To restore an encrypted backup, you need to provide the same GPG passphrase or key used during backup process.
15
+
To restore an encrypted backup, you need to provide the same GPG passphrase used during backup process.
13
16
14
17
- GPG home directory `/config/gnupg`
15
18
- Cipher algorithm `aes256`
16
-
-
17
-
To decrypt manually, you need to install `gnupg`
18
19
19
-
### Decrypt backup
20
+
{: .note }
21
+
The backup encrypted using `GPG passphrase` method can be restored automatically, no need to decrypt it before restoration.
22
+
Suppose you used a GPG public key during the backup process. In that case, you need to decrypt your backup before restoration because decryption using a `GPG private` key is not fully supported.
title: Run multiple backup schedules in the same container
3
+
layout: default
4
+
parent: How Tos
5
+
nav_order: 11
6
+
---
7
+
8
+
Multiple backup schedules with different configuration can be configured by mounting a configuration file into `/config/config.yaml``/config/config.yml` or by defining an environment variable `BACKUP_CONFIG_FILE=/backup/config.yaml`.
9
+
10
+
## Configuration file
11
+
12
+
```yaml
13
+
#cronExpression: "@every 20m" //Optional for scheduled backups
14
+
cronExpression: ""
15
+
databases:
16
+
- host: mysql1
17
+
port: 3306
18
+
name: database1
19
+
user: database1
20
+
password: password
21
+
path: /s3-path/database1 #For SSH or FTP you need to define the full path (/home/toto/backup/)
22
+
- host: mysql2
23
+
port: 3306
24
+
name: lldap
25
+
user: lldap
26
+
password: password
27
+
path: /s3-path/lldap #For SSH or FTP you need to define the full path (/home/toto/backup/)
28
+
- host: mysql3
29
+
port: 3306
30
+
name: keycloak
31
+
user: keycloak
32
+
password: password
33
+
path: /s3-path/keycloak #For SSH or FTP you need to define the full path (/home/toto/backup/)
34
+
- host: mysql4
35
+
port: 3306
36
+
name: joplin
37
+
user: joplin
38
+
password: password
39
+
path: /s3-path/joplin #For SSH or FTP you need to define the full path (/home/toto/backup/)
40
+
```
41
+
## Docker compose file
42
+
43
+
```yaml
44
+
services:
45
+
mysql-bkup:
46
+
# In production, it is advised to lock your image tag to a proper
0 commit comments