Backup and restore
Take a consistent backup of the whole cluster without stopping writes and restore it elsewhere.
teseladb admin backup copies every range at the same timestamp, so the backup is consistent even though writes carry
on during the process.
Take a backup
teseladb admin backup --at now --out /backups/2026-11-03The folder receives the SST files of each range exported at that timestamp and manifest.bson, with the SHA-256 of
each file. --at accepts now or a seconds.increment timestamp.
Restore
A restore runs on a new, empty cluster: no collections and a single data range.
teseladb admin restore --from /backups/2026-11-03Before touching anything it checks the SHA-256 of every file. If one does not match or the cluster is not empty, it fails without changing anything.
With the MongoDB tools
mongodump and mongorestore also work, with --oplog and --oplogReplay. They are useful to migrate from or to
MongoDB; for backups of the cluster itself, teseladb admin backup is faster because it copies files, not documents.
A guide to schedule them is in Scheduled backups.