# PBM 2.12 list command omits PITR in JSON output

**URL:** https://forums.percona.com/t/pbm-2-12-list-command-omits-pitr-in-json-output/40226
**Category:** Percona Backup for MongoDB
**Created:** [February 17, 2026, 11:10am UTC](https://forums.percona.com/t/pbm-2-12-list-command-omits-pitr-in-json-output/40226 "2026-02-17T11:10:50Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![richardl](https://avatars.discourse-cdn.com/v4/letter/r/9de0a6/32.png) [@richardl](https://forums.percona.com/u/richardl)
#### Post date: [February 17, 2026, 11:10am UTC](https://forums.percona.com/t/pbm-2-12-list-command-omits-pitr-in-json-output/40226/1 "2026-02-17T11:10:50Z")

</div>

I run a weekly “test backups” workflow. I’ve just updated from PBM 2.10 to 2.12 on my k8s cluster. The workflow uses the `pbm list –out json` command to extract the latest PITR timestamp. With 2.12 this is now returning an empty array.

i.e. `pbm list` shows

```auto
    2026-02-17T04:00:00Z 151.04MB <logical> success [restore_to_time: 2026-02-17T04:00:53]
	
  PITR chunks [64.50MB]:
    2026-02-10T04:00:52 - 2026-02-17T09:11:24

```

But `pbm list –out json` returns `{“pitr”:{“on”:false,“ranges”:[]}}` (snapshots not shown for brevity)

Luckily `pbm status –out json` does include the PITR range data so I’ve changed to that.

NB: I’ve tried to create a Jira issue for this but the “create” button does nothing.

---

<div class="post-metadata">

### Author: ![radoslaw.szulgo](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/radoslaw.szulgo/32/17315_2.png) [@radoslaw.szulgo](https://forums.percona.com/u/radoslaw.szulgo)
#### Post date: [February 18, 2026, 12:37pm UTC](https://forums.percona.com/t/pbm-2-12-list-command-omits-pitr-in-json-output/40226/2 "2026-02-18T12:37:57Z")

</div>

I’ve created one on your behalf: [PBM-1705](https://perconadev.atlassian.net/browse/PBM-1705)

---

<div class="post-metadata">

### Author: ![radoslaw.szulgo](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/radoslaw.szulgo/32/17315_2.png) [@radoslaw.szulgo](https://forums.percona.com/u/radoslaw.szulgo)
#### Post date: [February 18, 2026, 7:19pm UTC](https://forums.percona.com/t/pbm-2-12-list-command-omits-pitr-in-json-output/40226/3 "2026-02-18T19:19:02Z")

</div>

We’ve tried to reproduce it and we are unable to. Can you share more details? What’s the MongoDB version do you use? Anything in logs?

---

<div class="post-metadata">

### Author: ![richardl](https://avatars.discourse-cdn.com/v4/letter/r/9de0a6/32.png) [@richardl](https://forums.percona.com/u/richardl)
#### Post date: [February 20, 2026, 11:44am UTC](https://forums.percona.com/t/pbm-2-12-list-command-omits-pitr-in-json-output/40226/4 "2026-02-20T11:44:22Z")

</div>

I’m using MongoDB 7.0.28-15. We’ve just updated to v7 from v6 and some clusters are running in FCV 6 and some are 7.

On my dev cluster (FCV 7) I get this:

```bash
pbm list

PITR :

```

```auto
pbm list --full

PITR :

rs0: [{ 2026-01-16T04:11:18 - 2026-02-20T11:21:25 }]

```

The `--out json` setting is consistent with the text output

On prod (FCV 6) I get PITR data without `--full` for both commands.

The test workflow is creating a clean instance so I assume would be FCV 7. One notable difference is that this instance has PITR disabled whereas these clusters have it enabled.
