Upload to S3 not finished during one backup time window creates large amount of traffic
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hey there.
I am experimenting with the backup app since a couple of weeks now. I want to use it in combination with a S3 external storage.
In the last weeks I have experienced quite the amount of data traffic generated by the backup app, which corresponds to #162.
It's not perfect for a private internet connection, but it's understandable why it's done this way.
Another behavior I have experienced is occurring when the upload of a backup point isn't finished during the maintenance time window.
It seems like all already uploaded backup data is downloaded during the next maintenance time window just before uploading to S3 continues.
As the backup on the external storage gets larger during every maintenance time window, the data getting downloaded during the next maintenance time window gets larger as well. As a consequence the time left to upload new data gets shorter every time and a large amount of traffic is generated. Is this an expected behavior or a misconfiguration/bug issue?
In the image below you can see ~40gb of backup-data getting downloaded just before uploading continues:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Reproduce a backup upload that spans maintenance windows and inspect whether previously uploaded S3 data is downloaded before resuming; done means the behavior is explained and, if unintended, covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, php
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100