Backup and PITR Chunk Deletion Behavior
General
Escalation
General
Escalation
Description
Environment
None
AFFECTED CS IDs
PS0002142
Activity
Show:
Details
Details
Assignee
Unassigned
UnassignedReporter
daniel.almeidaNeeds QA
Yes
Priority
MediumSmart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created 4 days ago
Updated 4 days ago
Customer deleted all backups and PITR chunks using the pbm cleanup and pbm delete-pitr commands. The cluster was initially set with
oplogOnly: true, but the user subsequently switched it tooplogOnly: falseand applied the changes to Kubernetes. Following these changes, the operator began reporting the error message"no base backup found,"although PBM continued its oplog collection. Is this expected behavior?