We try to use `pbm backup -t external` to backup MongoDB on kubernetes.
Everything was going well until we started the restore operation.
First we try Reference documentation
pbm statusstatus value done before restore mongodb
[mongodb@dev-rs-mdb-rs0-1 /]$ pbm describe-backup 2025-10-17T07:23:50Z
name: "2025-10-17T07:23:50Z"
opid: 68f1ef06ec800efad41d2a49
type: external
last_write_time: "2025-10-17T07:23:52Z"
last_transition_time: "2025-10-17T07:31:26Z"
mongodb_version: 6.0.24-19
fcv: "6.0"
pbm_version: 2.9.1
status: done
size_h: 0 B
- Snapshots of backups shows ERROR after we delete and restore pvc from snapshot.
It seems that the snapshots of backups and the mongodb cluster have returned to the state betweem `pbm backup` and `pbm backup-finish`.
[mongodb@dev-rs-mdb-rs0-0 /]$ pbm status
Cluster:
========
rs0:
- dev-rs-mdb-rs0-0.dev-rs-mdb-rs0.default.svc.cluster.local:27017 [S]: pbm-agent [v2.9.1] OK
- dev-rs-mdb-rs0-1.dev-rs-mdb-rs0.default.svc.cluster.local:27017 [P]: pbm-agent [v2.9.1] OK
- dev-rs-mdb-rs0-2.dev-rs-mdb-rs0.default.svc.cluster.local:27017 [S]: pbm-agent [v2.9.1] OK
PITR incremental backup:
========================
Status [ON]
Running members: rs0/dev-rs-mdb-rs0-2.dev-rs-mdb-rs0.default.svc.cluster.local:27017;
Currently running:
==================
Snapshot backup "2025-10-17T07:23:50Z", started at 2025-10-17T07:23:50Z. Status: copyReady. [op id: 68f1ef06ec800efad41d2a49]
Backups:
========
S3 us-east-1 http://10.3.xx.xx:80/test-backup/test-rs-mdb
Snapshots:
2025-10-17T07:23:50Z 0.00B <external> [ERROR: Backup stuck at `copyReady` stage, last beat ts: 1760686009] [2025-10-17T07:23:56Z]
2025-10-15T10:31:58Z 0.00B <external> [restore_to_time: 2025-10-15T10:32:00Z]
2025-10-15T05:45:56Z 0.00B <external> [restore_to_time: 2025-10-15T05:45:58Z]
PITR chunks [53.42MB]:
2025-10-17T07:14:12Z - 2025-10-17T07:24:11Z (no base snapshot)