Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Backup files are not deleted from S3 if database is deleted

Description

Tested with Everest 0.11.0 rc1 version.

Create a mysql, mongodb database with 3 nodes and enable scheduled backups, PITR.

After two scheduled backups complete, delete the mysql database

Files in S3 before mysql deletion

Files in S3 after mysql deletion

Issues

  1. PITR binlogs are not deleted.

  2. The mysql-wss dir is not deleted.

After two scheduled backups complete, delete the mongodb database also

Files in S3 before mongodb deletion

Files in S3 after mongodb deletion

Issues

  1. The backup directory(2024-06-10T06:00:21Z/rs0/) contains the *.gz files, the backup files are not deleted.

  2. The 2024-06-10T06:00:21Z.pbm.json in the mongodb-m3r/eff6a5c5-2ef4-413e-9c58-02c6a6ab9e6b dir is not removed.

  3. The pbmPitr dir is not deleted.

  4. The mongodb-m3r dir is not deleted.

Environment

None

Attachments

2

Activity

Show:

Manish Chawla July 31, 2024 at 1:57 PM

Tested with Everest v1.1.0-rc1 version.

Backups deletion in mongodb has been fixed in this issue. Backups deletion in mysql will be fixed in a different issue.

Files in S3 before mongodb database deletion

Files in S3 after mongodb database deletion

PITR logs and .pbm.init file deletion will also be fixed in a different issue.

Closing this issue. Thanks Oksana for fixing this issue.

Manish Chawla July 3, 2024 at 8:33 AM

Testing of this issue is currently blocked by as the mongodb database is not able to come up.

Oksana Grishchenko July 2, 2024 at 11:48 AM

The problem is turned out to be a bunch of different problems, here is the sheet which describes them.

What’s changed in the scope of this ticket:

PSMDB: when the cluster is deleted the backup files are also deleted.

Out of scope:

Unresolved

Details

Assignee

Reporter

Sprint

Fix versions

Priority

Smart Checklist

Created June 10, 2024 at 8:05 AM
Updated August 12, 2024 at 12:28 PM