Docs: clarification of description of get latest command in backup (#601)
This commit is contained in:
parent
7ce9d1f077
commit
463cad3b07
|
|
@ -81,7 +81,7 @@ spec:
|
||||||
getLatestAction:
|
getLatestAction:
|
||||||
exec:
|
exec:
|
||||||
command:
|
command:
|
||||||
- /home/user/bin/get-latest.sh # this command is invoked on "backup" container to get last backup number before pod deletion. If you don't omit it in CR, you can lose data
|
- /home/user/bin/get-latest.sh # this command is invoked on "backup" container to get last backup number before pod deletion; not having it in the CR may cause loss of data
|
||||||
interval: 30 # how often make backup in seconds
|
interval: 30 # how often make backup in seconds
|
||||||
makeBackupBeforePodDeletion: true # make a backup before pod deletion
|
makeBackupBeforePodDeletion: true # make a backup before pod deletion
|
||||||
restore:
|
restore:
|
||||||
|
|
|
||||||
|
|
@ -85,6 +85,6 @@ spec:
|
||||||
getLatestAction:
|
getLatestAction:
|
||||||
exec:
|
exec:
|
||||||
command:
|
command:
|
||||||
- /home/user/bin/get-latest.sh # this command is invoked on "backup" container to get last backup number before pod deletion. If you don't omit it in CR, you can lose data
|
- /home/user/bin/get-latest.sh # this command is invoked on "backup" container to get last backup number before pod deletion; not having it in the CR may cause loss of data
|
||||||
#recoveryOnce: <backup_number> # if want to restore specific backup configure this field and then Jenkins will be restarted and desired backup will be restored
|
#recoveryOnce: <backup_number> # if want to restore specific backup configure this field and then Jenkins will be restarted and desired backup will be restored
|
||||||
```
|
```
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue