Large data is failed to take backup with duplicty
Bug #1854351 reported by
Gangadhar
This bug report is a duplicate of:
Bug #385495: Large backup signature and manifest files should be split with --volsize too.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Duplicity |
In Progress
|
Medium
|
Kenneth Loafman | ||
Bug Description
We have the 103 GB data in volume and trying to take the backup, but it is taking too much time and failed to take the backup of entire data.
duplicity 0.8.03
Data size 103 GB
endpoint is s3.us-south.
python version 3.7.3
cat /etc/os-release
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.10.1
Note : one of our customer failed to take the backup of 130GB size.
Revision history for this message
| Kenneth Loafman (kenneth-loafman) wrote | #1 |
| Changed in duplicity: | |
| assignee: | nobody → Kenneth Loafman (kenneth-loafman) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
To post a comment you must log in.
How large is the sigtar file? Do you have any logs?
Most likely you hit this bug: https:/
It's an old one. A couple of workarounds may help:
- split the backup along directories
- use --max-blocksize