Finding the repository to backup into causes staging directory population
Description
Environment
None
Release Notes Description
None
Activity
Show:
Matt Ingenthron
updated the RankAugust 7, 2024 at 9:01 PMNone
Ranked higher
Matt Hall
updated the Linked IssuesApril 30, 2024 at 10:03 AMNone
This issue relates to CBSE-16968
Matt Hall
created the IssueApril 30, 2024 at 10:01 AMPinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Reporter
Matt Hall
Matt HallStory Points
0
Components
Priority
Major
Instabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty Incident
Sentry
Linked Issues
Linked Issues
Zendesk Support
Linked Tickets
Linked Tickets
Created April 30, 2024 at 10:01 AM
Updated August 7, 2024 at 9:01 PM
Instabug
What is the problem?
To find the repo to backup into the backup script calls
cbbackupmgr info
(1, 2). When backing up to a PVC or to the cloud with a persistent staging directory this is fast, if a little indirect. However, when using ephemeral staging this causes a staging directory population for the entire archive, which can take a long time. The backup itself only needs to repo to be staged, which should be much quicker.What is the solution?
The repo to backup should be persisted somehow, or calculated in a more efficient way