How to restore data on a single member in replica set by PMM

Dear All,

Today, I found an issue from a UAT MongoDB server with version 7.0.24 hosted on rhel8, the service is died down around 10 months (last active is 2025 August), and the database is not actually big which is not larger than 2GB, but the server is died down for around 10 months, so its may take long time to recovery from oplog (that actually not possible to recover), so I decided to clear the data of this secondary node and rejoin the replica set to restore data by initial sync. And the result is as expected, the data restored within a minute. Besides the initial sync, would the PBM provide any solution subject to a single node from a replica set instead of recovery data on the whole replica set? As my knowledge, recover data on a single node in the replica set is still not available in PBM. I hope the one has similar experiences could share your solution, thanks!

Best Regards,
Alvin

Hi @Alvin_Ma - nice to see you again in the forum!

Thanks for the feedback, and I’m happy that you managed to resurrect your old MongoDB deployment. Usually, that’s the recommended approach to use initial sync (logical or physical via File copy-based initial sync) to recover a single node.

What would be better if that is triggered by PBM?

Sir, its glad to hear your reply! My concern on initial sync is that its not a good way to restore data if the database size is big, says, the data volume near to 900GB or even TB… In such case, initial sync would have high possibility of fail. That’s why I asked for the pbm restore solution for a single node which are going to rejoin the replica set.