# Option to exclude in-memory nodes from backups in a sharded cluster

**URL:** https://forums.percona.com/t/option-to-exclude-in-memory-nodes-from-backups-in-a-sharded-cluster/37580
**Category:** Percona Backup for MongoDB
**Created:** [April 11, 2025, 10:33am UTC](https://forums.percona.com/t/option-to-exclude-in-memory-nodes-from-backups-in-a-sharded-cluster/37580 "2025-04-11T10:33:36Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Behzad](https://avatars.discourse-cdn.com/v4/letter/b/c4cdca/32.png) [@Behzad](https://forums.percona.com/u/Behzad)
#### Post date: [April 11, 2025, 10:33am UTC](https://forums.percona.com/t/option-to-exclude-in-memory-nodes-from-backups-in-a-sharded-cluster/37580/1 "2025-04-11T10:33:36Z")

</div>

Hi,  
I’m not familiar with the internals, but my understanding is that the cluster can rebuild in-memory nodes on its own, as long as there’s a consistent backup of the persistent WiredTiger nodes.

Is there any workaround to exclude in-memory nodes in a sharded cluster? Is it even technically possible to implement this with PBM?

If not, do you have any suggestions? Just to add some context. I don’t mind doing some manual configuration during the restore process, as long as physical incremental backup is supported.

Thank you

---

<div class="post-metadata">

### Author: ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)
#### Post date: [April 11, 2025, 11:04am UTC](https://forums.percona.com/t/option-to-exclude-in-memory-nodes-from-backups-in-a-sharded-cluster/37580/2 "2025-04-11T11:04:14Z")

</div>

Hi, at the moment physical backup/restore doesn’t support inMemory nodes. Feel free to create a feature request in [jira.percona.com](http://jira.percona.com) with the behavior you think would make sense in this regard.