Controlling mongod shutdown during PBM incremental restore

MongoDB Percona Backup for MongoDB
, ,
1

Hello everyone,

I’m working with Percona Backup for MongoDB (PBM) on a Percona Server for MongoDB (PSMDB) cluster and I’d like to use incremental backups and restores. In one of the forum threads I saw that the restore process triggers a full shutdown of all mongod instances in order to apply the backups:
https://forums.percona.com/t/cannot-restore-from-incremental-backup-pbm-and-psmdb-in-the-same-pod/28041/2?u=nir-elk

My questions are:

  1. Can I control the shutdown behavior?
    For example, is it possible to perform a staggered shutdown of my replica set members—shutting down one secondary at a time, restoring it, and then moving on—instead of taking down the entire cluster at once?
  2. Is there a way to restore without shutting down any mongod instances?
    Or to minimize downtime by keeping parts of the cluster online while another part is being restored?

Any advice on PBM configuration options, flags, or best practices to achieve this would be greatly appreciated. Thank you in advance for your help!

— Nir

2

Hi, a staggered shutdown would be a bad idea. During restore you need to prevent any writes to the cluster for consistency reasons.
What I suggest you do in that scenario is simply restore to a brand new cluster: Restore from a backup into a new environment - Percona Backup for MongoDB