I'm running MongoDB 3.2.9 with WiredTiger on 3 EC2 instances. When backing up the database volumes using elastic block store snapshots, do I need to perform
db.fsyncLock() when running a 3 node replica set where all nodes are running without journal enabled? Additionally, for reference, my
storage.dbPath maps to a dedicated EBS volume for
/data on each
mongod instance on each EC2 server. There are also separate dedicated volumes for logs.
I'm working off of the below documentation for reference, but it's not clear how these steps map from single instance deployments to replica set deployments: https://docs.mongodb.com/ecosystem/tutorial/backup-and-restore-mongodb-on-amazon-ec2
If I do need to run
db.fsyncLock(), does the lock apply to all instances on all EC2 servers? The documentation says that it locks the 'entire'
mongod instance, but it's not clear to me whether the instance in this case refers to an instance on a single EC2 server, or if this applies to all instances in the replica set spread over all EC2 servers (3 EC2 servers in my case).