# MongoDB Remote Backup

**URL:** <https://forums.percona.com/t/mongodb-remote-backup/36495>\
**Category:** Percona Backup for MongoDB\
**Tags:** percona, mongodb\
**Created:** [February 3, 2025, 12:26pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495 "2025-02-03T12:26:19Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![berkan](https://avatars.discourse-cdn.com/v4/letter/b/d6d6ee/32.png) [@berkan](https://forums.percona.com/u/berkan)\
**Post date:** [February 3, 2025, 12:26pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/1 "2025-02-03T12:26:19Z")

</div>

Hi guys,

I am experiencing an issue while taking backups on a remote server. Below are the details of the setup and the problem:

[PbmBackup] → Server One  
[MongoDBServer] → Server Two

From **PbmBackup** to **MongoDBServer** , the connection has been successfully established. When I run `pbm status`, it correctly detects the MongoDB cluster. However, when I initiate a backup, no data is being written, and the process remains stuck at **0 bytes**.

On the Linux side, all necessary permissions have been correctly assigned to the **pbm** user. The backup path is located on **PbmBackup**. Despite this, the backup does not progress.

Is there any configuration or step that I might be missing? Any insights or suggestions would be greatly appreciated.

Here are some images to make the issue more understandable.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/5/5/55e8ee838d124562197f3ce65c8a828e3a02c998.png)

---

<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 3, 2025, 12:30pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/2 "2025-02-03T12:30:22Z")

</div>

Hi @berkan  
as the error suggests - have you checked other PBM agents logs? Maybe they crashed, or just they were not able to connect to PSMDB?

When troubleshooting issues with backups and restores, viewing logs and PBM status may sometimes not be enough to identify the issue’s root. Starting with version 2.8.0 you can generate a diagnostics report about a specific backup, restore, or other commands:

> **[Percona Backup for MongoDB - Diagnostics report](https://docs.percona.com/percona-backup-mongodb/troubleshoot/pbm-report.html)**
>
> When troubleshooting issues with backups and restores, viewing logs and PBM status may sometimes not be enough to identify the root of the issue.

The report definitely can help us to understand what’s happening.

---

<div class="post-metadata">

**Author:** ![berkan](https://avatars.discourse-cdn.com/v4/letter/b/d6d6ee/32.png) [@berkan](https://forums.percona.com/u/berkan)\
**Post date:** [February 3, 2025, 12:34pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/3 "2025-02-03T12:34:16Z")

</div>

Hi Rado,

Thanks for replying. Here is the result of diagnostics report.

 ![image](https://us1.discourse-cdn.com/flex019/uploads/percona1/original/3X/a/b/ab912583c7f07ff5d9114f000a8a0ff30eca5ab4.png)

---

<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 3, 2025, 12:38pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/4 "2025-02-03T12:38:19Z")

</div>

How many CPU cores you have on that instance?  
I can see a message “dumping 0 collections in parallel” … there’s a known issue in version 2.8.0 that doesn’t work on single CPU machines. To solve that you need to manually set “numParallelCollections” to 1.

---

<div class="post-metadata">

**Author:** ![berkan](https://avatars.discourse-cdn.com/v4/letter/b/d6d6ee/32.png) [@berkan](https://forums.percona.com/u/berkan)\
**Post date:** [February 3, 2025, 12:48pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/5 "2025-02-03T12:48:12Z")

</div>

Hi Rado,

Your solution resolved the issue perfectly. I really appreciate your help, thanks a lot!

---

<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 3, 2025, 12:50pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/6 "2025-02-03T12:50:57Z")

</div>

BTW We we’ll fix it in the upcoming PBM 2.9.0 version. This should be available in about in 2 weeks.

---

<div class="post-metadata">

**Author:** ![berkan](https://avatars.discourse-cdn.com/v4/letter/b/d6d6ee/32.png) [@berkan](https://forums.percona.com/u/berkan)\
**Post date:** [February 3, 2025, 1:00pm UTC](https://forums.percona.com/t/mongodb-remote-backup/36495/7 "2025-02-03T13:00:59Z")

</div>

Perfect,

I’m looking forward to it with great anticipation.