TeselaDB
DocumentationDownload

Rollback plan

How to go back to MongoDB if the migration does not go well.

Prepare how to go back to MongoDB if the migration does not go well. Decide it before moving the traffic.

Requirements

  • The source MongoDB cluster, not deleted, until you sign the migration off.

While you test

Leave MongoDB as it was and test TeselaDB with a copy. If something fails, the application stays on MongoDB.

After moving the traffic

What is written to TeselaDB after the switch has to go back too. mongodump works against TeselaDB:

Shell
mongodump --uri "mongodb://root:<password>@node-01:27017/shop?tls=true&tlsCAFile=./ca.pem" --gzip --archive=back.gz
mongorestore --uri "mongodb://user:<password>@mongo-01:27017/" --gzip --archive=back.gz

Check

With the return copy restored, the document count of each collection you copied back from TeselaDB is the same in MongoDB and in TeselaDB.

Common problems

  • An API key or a teselaBuckets option only exists in TeselaDB. It has no equivalent in MongoDB and does not go back.

See also

PreviousAdapt your applicationNextMCP server