Important Deadline: Migrate to MongoDB Atlas

[Martii]

Received this today about mLabs. I'll look it over but mostly likely @sizzlemctwizzle will need to do this especially if development is to continue. I'd rather not lose the dev database entries as I use it to test changes to make sure things don't break. Since I took production away from there some time ago there is no need to modify production mongoDB.

Important Deadline: Migrate to MongoDB Atlas by December 08, 2020

Hello from mLab,

On October 9, 2018 we announced that mLab was joining MongoDB, Inc. and that as part of merging the two organizations we would be sunsetting mLab’s service and working with users to migrate to MongoDB Atlas.

Since this announcement, mLab and MongoDB Atlas have worked together to build tools to migrate mLab-hosted database deployments to MongoDB Atlas with ease and minimal downtime.

The deadline to migrate your mLab deployment(s) to MongoDB Atlas is December 08, 2020. However, we encourage you to migrate as soon as possible. With MongoDB Atlas, you'll be able to take advantage of the latest MongoDB versions, auto-scaling, full-text search, support for compliance standards (e.g., SOC2, HIPAA), and much more.

Failure to take action will result in the loss of your data.

Key details about the "OpenUserJS.org" mLab account:

Admin Username - clipped Admin Email - clipped

All deployments in this account must be migrated to MongoDB Atlas, including:

clipped/openuserjs_devel

Relevant documentation:

  Migration FAQ:   https://docs.mlab.com/mlab-to-atlas/

  Step-by-Step Guide to Migrating Sandbox Databases to Atlas:   https://docs.mlab.com/how-to-migrate-sandbox-databases-to-atlas/

The guide will walk you through creating an Atlas organization and connecting it to your mLab account so that you can access the migration tool that was built specifically for making migrations from mLab to Atlas as easy as possible.

If you have questions or run into any issues, you can simply reply to this email (support@mlab.com) for help.

Sincerely, mLab Support

[Martii]

OY!

Since mLab is in the process of sunsetting its service, if you want to upgrade your existing mLab Sandbox database, you’ll need to migrate to one of the Atlas for-pay clusters: * FAQ entry.

If it is pay for a sandbox we'll need to see the pricing difference between hosting it via a secure VPS droplet and a WiredTiger space. This was mentioned, buried, back in #1548 Cha-ching! ... or just running MongoDB locally and lose dev collaboration is another option. Perhaps having a downloadable gzip archive here on GH for import (mongorestore). Performed an archive import (export from mLabs) using mongodump -h ds131963.mlab.com:31963 -d openuserjs_devel -u dev -p oujs123 --gzip --archive=~/tmp/mLabDevDB.gz to production so we have a recent snapshot (credentials are public for dev so not clipped). Will keep a copy myself of this ~135.6 KiB archive.

---

Further down in the FAQ:

If you have multiple mLab Sandbox databases that you would like to migrate to Atlas, note that:

(1) There is a limit of one Atlas free-tier cluster (M0) per Atlas project.

This is why I said "If" above... this will make it difficult perhaps to migrate those to newer MongoDB versions... would have to be in an Atlas account to see how that part works.

[Martii]

@sizzlemctwizzle

Beyond expired...

MongoDB connection is disconnected
MongoDB connection error
Authentication failed.
Terminating app

If Atlas isn't used then the docs (and code) need to be updated to instruct using (local) MongoDB only. A copy of the dev DB (dirty) is in the dev folder of GH here.