§ Databases · Document
MongoDB backups, natively.
A point-in-time archive of a whole replica set using the oplog, or one archive per database on standalone servers, read from a secondary where one exists.
What Xtic runs
mongodump --host=127.0.0.1 --username=xtic_backup --authenticationDatabase=admin --config=/dev/fd/3 --readPreference=secondaryPreferred --oplog --archiveShown with placeholders. Credentials never appear on a command line: they reach the tool through the environment, a file descriptor or a short-lived file in memory.
Restore paths
- Original or fresh instance: mongorestore --drop with oplog replay
- Under a new name: namespace mapping from app.* to app_restore.*
- Selective: single collections
Verification
Exit code and stream on every run; mongorestore --dryRun against a sandbox in deep verification. Every artifact is also hashed, and the stored copy is read back and compared before the run counts as verified.
Version rule
Restore to the same major and feature compatibility version.
Good to know
- Sharded clusters are refused with an explanation — they need a coordinated backup
- Users and roles are included per database when you choose to include server objects
- Indexes are rebuilt on restore, which takes CPU time on large collections
- Licence and editions: No edition gates for dumps.
More databases