Skip to content
Percona Software for MongoDB Documentation

Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Backup for MongoDB status

Version added: 1.4.0

You can check the status of Percona Backup for MongoDB running in your MongoDB environment using the pbm status command.

pbm status

The output provides the information about:

  • Your MongoDB deployment and pbm-agents running in it: to what mongod node each agent is connected, the Percona Backup for MongoDB version it runs and the agent’s state

  • The currently running backups / restores, if any

  • Backups stored in the remote backup storage: backup name, type, completion time, size and status (success, ongoing, failed)

  • Point-in-time recovery status (enabled or disabled)

  • Valid time ranges for point-in-time recovery and the data size

This simplifies troubleshooting since the whole information is provided in one place.

Sample output 
pbm status    

Cluster:
========
config:
  - config/localhost:27027 [P]: pbm-agent [v2.10.0] OK
  - config/localhost:27028 [S]: pbm-agent [v2.10.0] OK
  - config/localhost:27029 [S]: pbm-agent [v2.10.0] OK
rs1:
  - rs1/localhost:27018 [P]: pbm-agent [v2.10.0] OK
  - rs1/localhost:27019 [S]: pbm-agent [v2.10.0] OK
  - rs1/localhost:27020 [S]: pbm-agent [v2.10.0] OK
rs2:
  - rs2/localhost:28018 [P]: pbm-agent [v2.10.0] OK
  - rs2/localhost:28019 [S]: pbm-agent [v2.10.0] OK
  - rs2/localhost:28020 [S]: pbm-agent [v2.10.0] OK    

PITR incremental backup:
========================
Status [OFF]    

Currently running:
==================
(none)    

Backups:
========
S3 us-east-1 https://storage.googleapis.com/backup-test
   Snapshots:
    2025-06-03T09:55:47Z 0.00B <physical> ongoing [running: running / 2025-06-03T09:55:50]
    2025-03-16T10:36:52Z 491.98KB <physical> success [restore_to_time: 2025-03-16T10:37:13]
    2025-03-15T12:59:47Z 284.06KB <physical> success [restore_to_time: 2025-03-15T13:00:08]
    2025-03-11T16:23:55Z 284.82KB <physical> success [restore_to_time: 2025-03-11T16:24:16]
    2025-03-11T16:22:35Z 284.04KB <physical> success [restore_to_time: 2025-03-11T16:22:56]
    2025-03-11T16:21:15Z 283.36KB <physical> success [restore_to_time: 2025-03-11T16:21:36]
    2025-03-11T16:19:54Z 281.73KB <physical> success [restore_to_time: 2025-03-11T16:20:15]
    2025-03-11T16:19:00Z 281.73KB <physical> success [restore_to_time: 2025-03-11T16:19:21]
    2025-03-11T15:30:38Z 287.07KB <physical> success [restore_to_time: 2025-03-11T15:30:59]
  PITR chunks [1.10MB]:
    2025-03-16T10:37:13 - 2025-03-16T10:43:26 44.17KB

pbm-agent logs

Version added: 1.4.0

To troubleshoot issues with specific events or node(s), use the pbm logs command. It provides logs of all pbm-agent processes in your environment.

pbm logs has the set of filters to refine logs for specific events like backup, restore, pitr or for a specific node, and to manage log verbosity level. For example, to view logs about a specific backup with the Debug verbosity level, run the pbm logs command as follows:

pbm logs --severity=D --event=backup/2020-10-15T17:42:54Z

To learn more about available filters and usage examples, refer to Viewing backup logs.

Backup progress tracking

If you have a large logical backup, you can track the backup progress in the logs of the pbm-agent that makes it. A line is appended every minute showing bytes copied vs. total size for the current collection.

Start a backup:

pbm backup

Check backup progress:

  1. Check what pbm-agent makes the backup:

    pbm logs

  2. Connect to the mongod server where the pbm-agent is running and check its logs

    journalctl -u pbm-agent.service
    Sample output 
    2020/05/06 21:31:12 Backup 2020-05-06T18:31:12Z started on node rs2/localhost:28018
2020-05-06T21:31:14.797+0300 writing admin.system.users to archive on stdout
2020-05-06T21:31:14.799+0300 done dumping admin.system.users (2 documents)
2020-05-06T21:31:14.800+0300 writing admin.system.roles to archive on stdout
2020-05-06T21:31:14.807+0300 done dumping admin.system.roles (1 document)
2020-05-06T21:31:14.807+0300 writing admin.system.version to archive on stdout
2020-05-06T21:31:14.815+0300 done dumping admin.system.version (3 documents)
2020-05-06T21:31:14.816+0300 writing test.testt to archive on stdout
2020-05-06T21:31:14.829+0300 writing test.testt2 to archive on stdout
2020-05-06T21:31:14.829+0300 writing config.cache.chunks.config.system.sessions to archive on stdout
2020-05-06T21:31:14.832+0300 done dumping config.cache.chunks.config.system.sessions (1 document)
2020-05-06T21:31:14.834+0300 writing config.cache.collections to archive on stdout
2020-05-06T21:31:14.835+0300 done dumping config.cache.collections (1 document)
2020/05/06 21:31:24 [##......................]   test.testt  130841/1073901  (12.2%)
2020/05/06 21:31:24 [##########..............]  test.testt2   131370/300000  (43.8%)
2020/05/06 21:31:24
2020/05/06 21:31:34 [#####...................]   test.testt  249603/1073901  (23.2%)
2020/05/06 21:31:34 [###################.....]  test.testt2   249603/300000  (83.2%)
2020/05/06 21:31:34
2020/05/06 21:31:37 [########################]  test.testt2  300000/300000  (100.0%)
Last update: November 21, 2025
Created: November 21, 2025