-
-
Notifications
You must be signed in to change notification settings - Fork 448
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
destination out of space #265
Comments
Also for me standard backup, with all default and no special parameters, start
to fail when destination fills up.
The software looks unable to delete old stuff to make space for the new.
HTH. Marco
…On dom, 2024-01-07 at 07:12 -0800, Giancarlo Bellante wrote:
Hi,
I use it to backup whole server to another, script launched by cron every day
at 2am.
I m forcing ipv4 and also using an exclude list.
rsync_tmbackup.sh --rsync-append-flags "-4" //
***@***.***:/backup-dir exclude.list
Everything works great for a few days, but when I'm using up all the space on
the partition where the destination directory is, it fills up to 100% and in
the logs I only find an rsync I/O error.
I would expect some old backups to be automatically deleted instead, but this
doesn't happen.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID:
***@***.***>
|
I believe I have the same issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I use it to backup whole server to another, script launched by cron every day at 2am.
I m forcing ipv4 and also using an exclude list.
rsync_tmbackup.sh --rsync-append-flags "-4" // [email protected]:/backup-dir exclude.list
Everything works great for a few days, but when I'm using up all the space on the partition where the destination directory is, it fills up to 100% and in the logs I only find an rsync I/O error.
I would expect some old backups to be automatically deleted instead, but this doesn't happen.
The text was updated successfully, but these errors were encountered: