# Why should we have automatic backups via jobs in postgres? #1690
**URL:** https://forums.percona.com/t/why-should-we-have-automatic-backups-via-jobs-in-postgres-1690/39535
**Category:** Percona Everest
**Created:** [October 12, 2025, 7:43am UTC](https://forums.percona.com/t/why-should-we-have-automatic-backups-via-jobs-in-postgres-1690/39535 "2025-10-12T07:43:12Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@ahmad\_taknet](https://forums.percona.com/u/ahmad_taknet)
#### Post date: [October 12, 2025, 7:43am UTC](https://forums.percona.com/t/why-should-we-have-automatic-backups-via-jobs-in-postgres-1690/39535/1 "2025-10-12T07:43:12Z")
Why does Postgres create a backup job for me in a pvc of the same size as the space I used when creating the database in Kuber when creating the database? I really don’t need this repo1 that was created when i started the postgresSQL cluster in UI
postgresql-qii-repo1 Bound pvc-74ebed1a-5ce8-43b2-b3fb-3ed89adfe231 1Gi RWO
And also we don’t have any mechanism to delete this job that has been completed?
---
### Author:  [@Chetan\_Shivashankar](https://forums.percona.com/u/Chetan_Shivashankar)
#### Post date: [October 15, 2025, 5:46pm UTC](https://forums.percona.com/t/why-should-we-have-automatic-backups-via-jobs-in-postgres-1690/39535/2 "2025-10-15T17:46:15Z")
Hi @ahmad_taknet
Thank you for reaching out.
If I understand correctly, Do you want to disable the creation of repo host while creating Postgres cluster with Everest ?
`And also we don’t have any mechanism to delete this job that has been completed?`
Can you please confirm which job are you referring to ?
---
### Author:  [@ahmad\_taknet](https://forums.percona.com/u/ahmad_taknet)
#### Post date: [October 15, 2025, 7:16pm UTC](https://forums.percona.com/t/why-should-we-have-automatic-backups-via-jobs-in-postgres-1690/39535/3 "2025-10-15T19:16:00Z")
```auto
Yes. As soon as the postgres cluster is created, a perconapgbackups named repo1 and a job named postgresql-mwd-backup-xfcq and consequently a pod named postgresql-mwd-backup-xfcq-xdjp9 are created. This repo1 creates a pvc named postgresql-mwd-repo1 and has a volume of the size of my database, which is not what I want. All this happens automatically for backup. I want this to happen only by creating a dedicated backupstorage. And the mentioned job contains the following command:
value: --stanza=db --repo=1 --annotation="percona.com/backup-job-type"="replica-create"
```
---
### Author:  [@Diogo\_Recharte](https://forums.percona.com/u/Diogo_Recharte)
#### Post date: [October 16, 2025, 2:22pm UTC](https://forums.percona.com/t/why-should-we-have-automatic-backups-via-jobs-in-postgres-1690/39535/4 "2025-10-16T14:22:04Z")
Hi @ahmad_taknet, until Percona Operator for PostgreSQL v2.7.0 we were not allowed to create a DB cluster with backups disabled. This was because a backup was required in order to get replication going between nodes. Because of this limitation, we had to resort to creating a PVC repo that could be used for the initial deployment.
Now that the Percona Operator for PostgreSQL allows us to disable backups entirely, we will soon [remove this unnecessary PVC repo](https://perconadev.atlassian.net/browse/EVEREST-1319). However, we are currently blocked by a [bug in the operator](https://perconadev.atlassian.net/browse/K8SPG-869). As soon as that bug is fixed we will remove the PVC and backup job.