I have been validating MongoDB full instance restore using Veeam Explorer for MongoDB (VBR v13) and would like to raise a discussion related to file ownership and permissions after restoring.
Observed Behavior
When restoring a full MongoDB instance to a Linux server, the restored MongoDB data files are owned by the OS user used during the restore process (restore authentication user).
As a result:
- MongoDB service fails to start under the original
mongodservice account, or - The node cannot be cleanly added back to an existing MongoDB replica set
- Manual post‑restore steps are required (
chown/chmod) to revert ownership to the original MongoDB service user
This aligns with current permission requirements documented for MongoDB restore operations, where the restore user must have root privileges on the target system. [helpcenter.veeam.com]
Challenge / Risk
From an operational and security perspective, this introduces several challenges:
- Requires manual intervention after every full instance restore
- Increases human error risk during DR or recovery scenarios
- Slows down RTO for MongoDB replica‑set recovery
Expected / Desired Behavior
- Automatically preserve original file ownership and permissions from backup metadata
OR - Post‑restore automatic ownership correction to the original MongoDB user/group
This would allow:
- Immediate MongoDB service startup
- Seamless re‑addition to replica sets
- Reduced security exposure
- Faster and cleaner DR workflows
Business Impact
- Reduces manual recovery steps
- Aligns with automated recovery
Environment (for context)
- Veeam Backup & Replication v13
- MongoDB Replica Set (Linux)
- Full instance restores using Veeam Explorer for MongoDB
Has anyone from the community encountered the same behavior
If so, was the only workaround to manually modify the restored MongoDB data files’ ownership and permissions (for example, reverting them back to the original mongod service account) in order to:
- Start the MongoDB service successfully, and
- Add the node back to the replica set?
Appreciate any shared experiences or alternative approaches.
