... | ... | @@ -1732,12 +1732,9 @@ will pick up those files, but also the actual backup files in |
|
|
|
|
|
This implies that the files covered by the `gitlab-backup` job are
|
|
|
*also* already backed up by Bacula and are therefore duplicated on the
|
|
|
backup storage server. See [issue 40518][] to review that strategy.
|
|
|
|
|
|
Ideally, this rather exotic backup system would be harmonized with our
|
|
|
existing backup system, but this would require (for example) using our
|
|
|
existing PostgreSQL infrastructure ([issue 20][]). Other ideas
|
|
|
(including filesystem snapshots) are also in [issue 40518][].
|
|
|
backup storage server. Ultimately, we need to make sure everything is
|
|
|
covered by our normal backup system and retire the rake task, see
|
|
|
[issue 40518][] to track that work.
|
|
|
|
|
|
[issue 40518]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40518
|
|
|
|
... | ... | |