Point-in-time Recovery Data Recovery from oplog replay

MongoDB Percona Backup for MongoDB
1

Based on point-in-time Recovery oplog Replay Recovery data after PBM physical backup, orphan documents exist for a certain shard, and as a result, the information cannot be deleted by the CleanuPorphedcommand

1 Like
2

Sorry but I don’t understand exactly what is the question? if you think there is a bug you can open a ticket in jira.percona.com

1 Like
3

I’m sorry. I mean
Orphan files will be generated when data is recovered using point-in-time Recovery Oplog Replay of PBM. How can we avoid this situation

1 Like
4

At this time you cannot restore a single shard, it’s all or nothing (although that might change in the future). See the “Important” box in this page: Running Percona Backup for MongoDB — Percona Backup for MongoDB 1.8 Documentation for more details on this.

1 Like
5

I am the whole cluster to restore the problem

1 Like