Issues
- If an upload fails, pbm retry mechanism is using the same upload id and fails.PBM-1202Resolved issue: PBM-1202
- Failed to refresh session cache after physical restorePBM-1102Resolved issue: PBM-1102andrew.pogrebnoi
- Filtered (or partial) Backups & RestoresPBM-1081
- Physical Selective Backups & RestoresPBM-1080Resolved issue: PBM-1080
- Update golang.org/x/net module due to CVE-2022-41723PBM-1076Resolved issue: PBM-1076andrew.pogrebnoi
5 of 5
If an upload fails, pbm retry mechanism is using the same upload id and fails.
Cannot Reproduce
General
Escalation
General
Escalation
Description
Environment
None
AFFECTED CS IDs
CS0041577
Attachments
6
Details
Assignee
UnassignedUnassignedReporter
zelmar.michelinizelmar.micheliniNeeds QA
YesAffects versions
Priority
Medium
Details
Details
Assignee
Unassigned
UnassignedReporter
zelmar.michelini
zelmar.michelini
Needs QA
Yes
Affects versions
Priority
MediumSmart Checklist
Smart Checklist
Smart Checklist
Created November 2, 2023 at 4:58 PM
Updated March 28, 2024 at 1:03 PM
Resolved March 28, 2024 at 1:03 PM
Activity
Jan MynarMarch 28, 2024 at 1:03 PM
see the comment
Oleksandr HavryliakNovember 8, 2023 at 9:20 AM
Hi !
Unfortunately we can not reproduce this issue, but I can suggest to upgrade PBM to the latest version. The reason is simple - newer version of PBM contains newer version of aws-sdk which can contain fixes like https://github.com/aws/aws-sdk-go/blob/main/CHANGELOG.md#sdk-bugs-7
PBM version 2.0.5 contains aws-sdk v1.44.159
PBM version 2.3.0 contains aws-sdk v1.44.312
IMO we should include sdk updates to our release notes, what do you think?
When a chunk is getting uploaded and if it fails in the middle, the retry mechanism from pbm with same upload id is not accepting in the next retry causing backup failure.
For example - Chunk with 50 gb data with upload id 1234 is getting uploaded and in the middle like if 25 gb gets uploaded and then failed. PBM retries with sample upload id 1234 an current S3 storage is not accepting the same upload id as part of incomplete chunk that is with 25 gb data is already available in the current storage.