-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Need 2x more space for backup #39
Comments
Hm, I don't know why it needs more space, maybe it has something to do I with Docker, will try to investigate it further later. However, one thing that drew my attention is that you are adding a timestamp to volume backup file name via |
Old backup archives are deleted by cron after 2d. There is no problem. Problem is when i run volume-backup, probably need something like temp ? When i run
|
Hey, sorry for delay, unfortunately I won't be able to help you much with this as there's nothing specific in the script that uses temporary storage and tar and compression commands shouldn't use it either. You can try to:
Could you also clarify how do you know that additional space is used during backup? |
It looks normal that the backup file is taking more and more space while archiving, what is weird that the usage suddenly decreases after backup is complete (at 00:35 - 00:36). Is the |
Before i start i want to notice when i see logs for docker container running i see probably stdout. Final disk usage drop is when backup job is finished. ??? SOME TEMPS/LOGS are deleted ???
|
Interesting find. Yes, what you see in docker logs is the content of the stdout, so the zipped file. It's possible that Docker stores it on disk somewhere while the container is running (we should research that). My suggestion for next step: Please try executing volume-backup without using stdout/redirection with the command I mentioned above and see if the same storage usage spike occurs. |
From a very fast research (first hit on Google, I am on mobile now): https://sematext.com/blog/docker-logs-location/ Could you monitor whether the file |
Better resource: Alternatively to changing the command you can also disable logging driver when starting volume backup by adding
|
Seems promising. Ill check that in next night run |
Hi @pschonmann, did you see an improvement after making the change? |
Logging option to none fixed my problem. Thanks. |
That's great! Thank you for taking the time to investigate this, I will update the documentation for the others. |
Hello, im using docker volume-backup for backup some volumes from sentry-on-premise.
I stop all containers and then backup containers with that loop
Backup running ok, but needs 2x space to make backup. Expecting when im packing to stdout not using too much space :( Is that bug or i need 2x space when doing backup ?
The text was updated successfully, but these errors were encountered: