-
Notifications
You must be signed in to change notification settings - Fork 75
Use tmpdir within /data for barman-cloud-backup/-restore #300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Use tmpdir within /data for barman-cloud-backup/-restore #300
Conversation
|
hey @immerrr, I am fine with the wrapper script. The PR needs a rebase, thanks for the pg17 and haproxy fixes btw. |
|
different situation but having same trouble: since the root disk is only 8GB and here's the entire logs of barman-cloud-backup the annoying thing is, postgres user tried to re-run so we needed to run barman-cloud-backup with different user like this: and kill tmp file periodically, to avoid disk full ps. I found we can change rootfs size; will try this when I encounter this issue again |
We are having an issue with postgres backups created by barman: they are failing, because barman creates a tar archive in
/tmpdirectory, which only has ~7.5G to work with, so it runs out of space.I've checked barman sources, and it didn't seem to have a way to configure its temp. directories, so I ended up making a wrapper script that creates a temporary directory in a place of your choice, and configured
barman-cloud-backupandbarman-cloud-restorecommands to run through that script.There should be a better way to handle this, but I wanted to get some early opinions on this.
Also, had to fix the haproxy configs, it seemed to complain about having two
server-templateclauses with the same namepg