Direct to S3 feature flags and backup-job path lifecycle
Parent: MongoDB Backup and Restore · Published reference · snapshot 2026-10-31
↓ Facts as markdownall context files
Source-anchored research for Direct to S3 feature flags and backup-job path lifecycle. Run status: COMPLETED.
These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
How-to and procedures
- Set mms.featureFlag.backup.d2s3 to enabled in the Ops Manager custom configuration to activate Direct to S3 Backup globally. (low confidence) (verified as of 2026-10-14) [source]
- Set mms.featureFlag.backup.d2s3 to controlled for project-level opt-in, then activate Settings > Beta Features > Backup D2s3 in the project. (low confidence) (verified as of 2026-10-14) [source]
Facts and statements
- After project activation, new eligible backup jobs use Direct to S3 from their first snapshot without per-job opt-in. (medium confidence) (verified as of 2026-10-14) [source]
- Backup jobs that existed before feature activation keep their existing Direct to S3 setting; activation does not automatically change those jobs. (low confidence) (verified as of 2026-10-14) [source]
- An operator can enable or disable Direct S3 Backup for an individual job through Admin > Backup > Jobs, then save the change. (low confidence) (verified as of 2026-10-14) [source]
- The per-job Direct S3 Backup control appears only for jobs whose snapshot store is an S3 blockstore. (medium confidence) (verified as of 2026-10-14) [source]
- For a sharded cluster, select Apply to all cluster members to enable Direct to S3 for every shard and the config server, then save. (low confidence) (verified as of 2026-10-14) [source]
- Ops Manager places uploadPath=AGENT_DIRECT_S3 in the backup cursor description, and the MongoDB Agent reads that value to select the job’s upload path. (low confidence) (verified as of 2026-10-14) [source]
- The MongoDB Agent freezes the upload path for a job. A snapshot already in progress completes on its original upload path; the documentation does not specify the effective boundary for every later manual toggle or flag revocation. (low confidence) (verified as of 2026-10-14) [source]
Children
- No children recorded.