restic issueshttps://gitlab.adullact.net/fcombernous/restic/-/issues2023-06-19T16:24:34+02:00https://gitlab.adullact.net/fcombernous/restic/-/issues/110search into known_hosts for copy targer server2023-06-19T16:24:34+02:00Fabien Combernoussearch into known_hosts for copy targer server7.3.0Fabien CombernousFabien Combernoushttps://gitlab.adullact.net/fcombernous/restic/-/issues/91use 2 SUT during acceptance tests2022-12-22T17:30:36+01:00Fabien Combernoususe 2 SUT during acceptance testsFor the moment acceptance tests are using 2 repositories on same SUT.
This issue is for being able to test copy with 2 differents nodes (One hosting a repository and one other hosting the copy).For the moment acceptance tests are using 2 repositories on same SUT.
This issue is for being able to test copy with 2 differents nodes (One hosting a repository and one other hosting the copy).not-yet-planed-releaseFabien CombernousFabien Combernoushttps://gitlab.adullact.net/fcombernous/restic/-/issues/66fix idempotency issue when wrapper_path and binary_path are same2019-09-12T09:51:16+02:00Fabien Combernousfix idempotency issue when wrapper_path and binary_path are samewhen `wrapper_path` and `binary_path` are same, the module is not idempotent.
The downloaded file is not controled by `file` type, and so the file is removed and downloaed again.when `wrapper_path` and `binary_path` are same, the module is not idempotent.
The downloaded file is not controled by `file` type, and so the file is removed and downloaed again.feature-paradiseFabien CombernousFabien Combernoushttps://gitlab.adullact.net/fcombernous/restic/-/issues/32Permit to add a high limit on memory usage of the restic executed processes2019-05-08T19:31:26+02:00Fabien CombernousPermit to add a high limit on memory usage of the restic executed processesWhen the backup is done, `restic` can be greedy in memory usage.
https://github.com/restic/restic/issues/979
It should be possible to add a parameter to limit on memory usage. Le restic backup command is launched by cron. And so it is ...When the backup is done, `restic` can be greedy in memory usage.
https://github.com/restic/restic/issues/979
It should be possible to add a parameter to limit on memory usage. Le restic backup command is launched by cron. And so it is possible to use this command :
`systemd-run -p MemoryHigh="2M" /opt/restic/bin/backupwrapper-<label> >> /var/log/restic/<label>.log 2>&1`
https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#MemoryHigh=
Perhaps a goland method exists to limit memory usage.not-yet-planed-release