-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
blobxfer not uploading the backup files correctly #307
Comments
This is a troublesome report. My apologies if you have experienced some sort of data loss. I'm not entirely familiar with blobxfer as it's outside of my actual use cases, but I can break down what happens. After the backup occurs locally on the system in a folder called
Then, after completion db-backup moves the newly made backup from Then, we run blobxfer again, and synchronize the changes from
Then the backup is complete. Then, there is a cleanup phase: We look for files that are older than
and then following that perform a synchronize with the filesystems again with blobxfer this time including the delete commands to delete only whats changed:
Maybe you can see with these steps where this could be going sideways?
|
Summary
I am trying to backup a postgres database to azure using blobxfer. On the first run everything works fine and the backup files are uploaded. On subsequent runs the uploaded backup files have the correct file size but do not contain any useful data. They are filled with
null
s. The checksum files contain some readable checkusum data.The checksum of one broken data file:
2a1a8a40495c8f95bb6cc64fb4db71274d83cc3c pgsql_hhzb_auth_db_20231209-143122.sql.gz
The checksum stored in the related checksum file:
730d0bba4d54f9725b6bc930a0f99aab4dce5bdd pgsql_hhzb_auth_db_20231209-143122.sql.gz
The backup is stuck at
Moving backup to external storage with blobxfer
.Steps to reproduce
What is the expected correct behavior?
Expected behavior is that the files are getting uploaded correctly.
Relevant logs and/or screenshots
Environment
c59afd3e3bf8
docker-compose.yaml:
Possible fixes
The root cause could be that blobxfer does not upload the files correctly. I conclude this because the checksum of the uploaded file does not match the checksum in the .sha1 file.
The text was updated successfully, but these errors were encountered: