Skip to:

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

PBM delete-backup does not remove file in storage

Description

Hello, 

 

I Use PBM 1.6.1 on mongoDB 4.2 and I have a script schedule in a cron to delete backup with a timestamp.

 

PBM list shows that the backup doesn't exist anymore but the file are still on the storage, this case is a local storage.

For example this morning, before cron : 

```

  1. pbm list
    Backup snapshots:
      2022-06-16T09:00:08Z [complete: 2022-06-16T12:22:30]
      2022-06-17T09:00:03Z [complete: 2022-06-17T11:34:47]
      2022-06-20T09:00:02Z [complete: 2022-06-20T11:53:25]
    ```

local storage : 

```
rw-rw-r- 1 mongodb mongodb  89K Jun 16 09:00 2022-06-16T09:00:08Z_shardConfigA.dump.gz
rw-rw-r- 1 mongodb mongodb  16G Jun 16 12:22 2022-06-16T09:00:08Z_shardDataA.dump.gz
rw-rw-r- 1 mongodb mongodb 525K Jun 16 12:22 2022-06-16T09:00:08Z_shardConfigA.oplog.gz
rw-rw-r- 1 mongodb mongodb  75M Jun 16 12:31 2022-06-16T09:00:08Z_shardDataA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.2K Jun 16 12:31 2022-06-16T09:00:08Z.pbm.json
rw-rw-r- 1 mongodb mongodb  91K Jun 17 09:00 2022-06-17T09:00:03Z_shardConfigA.dump.gz
rw-rw-r- 1 mongodb mongodb  15G Jun 17 11:34 2022-06-17T09:00:03Z_shardDataA.dump.gz
rw-rw-r- 1 mongodb mongodb 356K Jun 17 11:35 2022-06-17T09:00:03Z_shardConfigA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.3M Jun 17 11:37 2022-06-17T09:00:03Z_shardDataA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.2K Jun 17 11:37 2022-06-17T09:00:03Z.pbm.json
rw-rw-r- 1 mongodb mongodb 298K Jun 20 09:00 2022-06-20T09:00:02Z_shardConfigA.dump.gz
rw-rw-r- 1 mongodb mongodb  15G Jun 20 11:53 2022-06-20T09:00:02Z_shardDataA.dump.gz
rw-rw-r- 1 mongodb mongodb 436K Jun 20 11:53 2022-06-20T09:00:02Z_shardConfigA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.6M Jun 20 11:57 2022-06-20T09:00:02Z_shardDataA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.2K Jun 20 11:57 2022-06-20T09:00:02Z.pbm.json
```

After cron : 
```

  1. pbm list
    Backup snapshots:
      2022-06-20T09:00:02Z [complete: 2022-06-20T11:53:25]
    ```

local storage : 

```
rw-rw-r- 1 mongodb mongodb  89K Jun 16 09:00 2022-06-16T09:00:08Z_shardConfigA.dump.gz
rw-rw-r- 1 mongodb mongodb  16G Jun 16 12:22 2022-06-16T09:00:08Z_shardDataA.dump.gz
rw-rw-r- 1 mongodb mongodb 525K Jun 16 12:22 2022-06-16T09:00:08Z_shardConfigA.oplog.gz
rw-rw-r- 1 mongodb mongodb  75M Jun 16 12:31 2022-06-16T09:00:08Z_shardDataA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.2K Jun 16 12:31 2022-06-16T09:00:08Z.pbm.json
rw-rw-r- 1 mongodb mongodb  91K Jun 17 09:00 2022-06-17T09:00:03Z_shardConfigA.dump.gz
rw-rw-r- 1 mongodb mongodb  15G Jun 17 11:34 2022-06-17T09:00:03Z_shardDataA.dump.gz
rw-rw-r- 1 mongodb mongodb 356K Jun 17 11:35 2022-06-17T09:00:03Z_shardConfigA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.3M Jun 17 11:37 2022-06-17T09:00:03Z_shardDataA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.2K Jun 17 11:37 2022-06-17T09:00:03Z.pbm.json
rw-rw-r- 1 mongodb mongodb 298K Jun 20 09:00 2022-06-20T09:00:02Z_shardConfigA.dump.gz
rw-rw-r- 1 mongodb mongodb  15G Jun 20 11:53 2022-06-20T09:00:02Z_shardDataA.dump.gz
rw-rw-r- 1 mongodb mongodb 436K Jun 20 11:53 2022-06-20T09:00:02Z_shardConfigA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.6M Jun 20 11:57 2022-06-20T09:00:02Z_shardDataA.oplog.gz
rw-rw-r- 1 mongodb mongodb 2.2K Jun 20 11:57 2022-06-20T09:00:02Z.pbm.json
```

I don't know if this issue is only regarding local storage or can also happen if the backup is save in S3

Thank you 

Environment

DEV/QA

Attachments

1

Smart Checklist

Activity

Aaditya Dubey June 27, 2024 at 3:55 PM

Hi

We still haven't heard any news from you. So, I assume the issue no longer persists and will close the ticket. If you disagree, reply and create a follow-up with a new Jira report.

Aaditya Dubey February 6, 2024 at 5:20 PM

Hi

Please use the latest PBM 2.3.1 and check if it fixes your issue or not.

CrKontrol February 1, 2023 at 9:40 AM

On the version that we use which PBM 1.6.1, the problem remains

Aaditya Dubey January 30, 2023 at 8:02 AM

Hi ,

Glad to know your issue is resolved, Thank You for the updates.

Hi , Please let us if your issue is fixed as well.

Kalle Fagerberg January 24, 2023 at 11:20 AM

Small update from my end: pbm seems to successfully be able to clean up after itself now.

The issue we had was probably due to incompatability where we used pbm-agent v2.0.1 and talked to it remotely via pbm v1.8.1. Now that everything is running v2.0.3 it seems to work just fine.

Can't speak for Cam RC though. No clue if their problem is resolved.

Incomplete

Details

Assignee

Reporter

Found by Automation

Yes

Needs Review

Yes

Affects versions

Priority

Smart Checklist

Created June 21, 2022 at 9:35 AM
Updated June 27, 2024 at 3:56 PM
Resolved June 27, 2024 at 3:55 PM