[Operator] PG on-demand backups are incremental instead of full

Description

None

Environment

None

Activity

Show:

Manish Chawla February 21, 2024 at 12:04 PM

Tested with Everest vv0.0.0-22f1c72 (0.8.0 release build) version.

Created a pg db and ran a manual backup.

The manual backup spec displays the option --type=full

kubectl get pg-backup/backup-oac -n namespace1 -o yaml apiVersion: pgv2.percona.com/v2 kind: PerconaPGBackup metadata: creationTimestamp: "2024-02-21T10:48:53Z" generation: 1 name: backup-oac namespace: namespace1 ownerReferences: - apiVersion: everest.percona.com/v1alpha1 blockOwnerDeletion: true kind: DatabaseClusterBackup name: backup-oac uid: 71424f12-1117-46b3-82b2-7669cded19d5 resourceVersion: "192278" uid: 487bbee3-7616-460c-9927-a05177f65ebe spec: options: - --type=full pgCluster: postgresql-8dl repoName: repo2 status: backupType: full completed: "2024-02-21T10:50:26Z" destination: s3://bucket/postgresql-8dl/634bf11f-b686-4e5f-afb6-61036c892fff image: percona/percona-postgresql-operator:2.3.1-ppg16-pgbackrest jobName: postgresql-8dl-backup-92tn repo: name: repo2 s3: bucket: bucket endpoint: https://s3.xxxx.com region: xxxxxx state: Succeeded storageType: s3

The pg backup logs also display that the backup command ran for a full backup

time="2024-02-21T10:49:51Z" level=info msg="crunchy-pgbackrest starts" time="2024-02-21T10:49:51Z" level=info msg="debug flag set to false" time="2024-02-21T10:49:51Z" level=info msg="backrest backup command requested" time="2024-02-21T10:49:51Z" level=info msg="command to execute is [pgbackrest backup --stanza=db --repo=2 --type=full]" time="2024-02-21T10:50:23Z" level=info msg="output=[]" time="2024-02-21T10:50:23Z" level=info msg="stderr=[WARN: option 'repo2-retention-full' is not set for 'repo2-retention-full-type=count', the time="2024-02-21T10:50:23Z" level=info msg="crunchy-pgbackrest ends"
Done

Details

Assignee

Reporter

Sprint

Fix versions

Priority

Smart Checklist

Created February 7, 2024 at 8:56 AM
Updated February 21, 2024 at 12:04 PM
Resolved February 21, 2024 at 12:04 PM

Flag notifications