# Backup files not deleted for Postgres after removing the instance **URL:** \ **Category:** Percona Everest\ **Tags:** new-release\ **Created:** [August 20, 2024, 5:37pm UTC](https://forums.percona.com/t/backup-files-not-deleted-for-postgres-after-removing-the-instance/32467 "2024-08-20T17:37:29Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jbolin](https://avatars.discourse-cdn.com/v4/letter/j/e56c9b/32.png) [@jbolin](https://forums.percona.com/u/jbolin)\ **Post date:** [August 20, 2024, 5:37pm UTC](https://forums.percona.com/t/backup-files-not-deleted-for-postgres-after-removing-the-instance/32467/1 "2024-08-20T17:37:29Z")
When deleting an instance in Everest v1.1.0 (not checking the keep the backup files box), the backups for MySQL are removed. MongoDB backups are not fully removed but it is documented in EVEREST-1141 on what remains and it appears correct. However Postgres does not appear to remove anything and I do not see anything on this in EVEREST-1141 or with the Postgres limitations for Everest. I may be overlooking something. Please advise. ---
**Author:** ![Oksana\_Grishchenko](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/oksana_grishchenko/32/5608_2.png) [@Oksana\_Grishchenko](https://forums.percona.com/u/Oksana_Grishchenko)\ **Post date:** [August 23, 2024, 10:20am UTC](https://forums.percona.com/t/backup-files-not-deleted-for-postgres-after-removing-the-instance/32467/2 "2024-08-23T10:20:48Z")
Hi @jbolin! Currently, PG operator doesn’t have an option to clean up the storage, that’s why Everest doesn’t have this checkbox about keeping the backup files in case of PG. There are two tickets regarding this in Percona Postgres operator: - [[K8SPG-586] - Percona JIRA](https://perconadev.atlassian.net/browse/K8SPG-586) - [[K8SPG-538] - Percona JIRA](https://perconadev.atlassian.net/browse/K8SPG-538) The features are planned to the next PG operator releases. We need to add this PG limitation to the Everest docs since it’s confusing. Thank you for reporting!