MongoDB Backup and Operational Readiness

When to use

Invoke when establishing a MongoDB backup strategy, adding point-in-time recovery, validating that a restore actually meets RPO/RTO, wiring oplog-window observability, or producing operational runbook inputs for a production deployment.

Do not use for: document modeling or migrations (use mongodb-data-model-and-migration); query/index tuning (use mongodb-indexing-and-query-optimization); replica-set topology and failover behavior (use mongodb-replication-and-ha-readiness); auth/RBAC/TLS/CSFLE and the backup-artifact encryption key model (use mongodb-security-and-data-access-hardening); storage/volume/bucket provisioning (infrastructure layer — this skill designs the backup procedure, not the storage substrate).

Inputs

Required:

• An existing replica-set topology from mongodb-replication-and-ha-readiness (snapshot consistency, the source member for backups, and the oplog window all depend on it).
• Approved architecture/reliability RPO/RTO per data tier, or explicit confirmation they are intentionally deferred.

Optional: