In all the examples I've seen, success and failure were defined by the last backup timestamp.
Nevertheless, metrics similar to borgmatic_last_action_success of type gauge with values 0 and…
Hi @witten, I think the other exporters expose all the necessary information about the backup process. The main problem with their behavior is that they have no idea about the backup process…
Hi @bb, I'm not very experienced with borgmatic, but you can check the prune policy with the following command: borgmatic prune --list --dry-run.
Thanks @witten, I've solved my problem in the following way
/etc/borgmatic.d/includes/defaults.yaml
constants:
application: unknown
re…
--stats output with repository label
pg_dump in directory format can't be done if extracted using docker exec
if there are any clarifications I can make to the docs
I'd say that 7551810e should explicitly mention that mounting the directory should be done when dumping the database in directory…
pg_dump in directory format can't be done if extracted using docker exec
tried mounting the borgmatic runtime directory
In my case this could be achieved by adding -v /tmp/borgmatic:/tmp/borgmatic to the docker run command and setting `user_runtime_directory:…
pg_dump in directory format can't be done if extracted using docker exec
pg_dump and compression
Double compression
compression: auto,zstd
postgresql_databases:
- name: db
format: custom
1st run
Duration: 13.43 seconds
pg_dump and compression
I didn't notice this at first, but they changed the `--compress' option in postgresql 16. Before:
-Z 0..9 --compress=0..9Specify the compression level to use. Zero means…
pg_dump and compression
My instinct says not to double compress, but that's just instinct. I'd actually recommend answering this experimentally.
The behavior may be different for large databases. By the way, my…
pg_dump and compression