MongoDB Atlas Production and QA databases are in a single cluster

[Enkidu93]

Because we take backups per cluster, if we need to restore QA, there's no straightforward way (to my knowledge) to roll just QA back without also rolling production back. Regardless, we should consider moving them to separate clusters so they are completely isolated. Minimally, we should make updates to the backup strategy (if possible) so that just QA or prod can be restored or document a method to restore QA or production separately.

[Enkidu93]

@pmachapman, I was kinda hoping you could take this one since you've done the work with the backups and Atlas maintenance, but I'm happy to if you'd rather not. We don't have to separate the QA database into a new cluster if there's a way to restore just one of the databases in a cluster from a backup. I think you were out when we hit this problem initially so I wasn't able to ask if you had a method in mind for doing this and ended up having to just un-migrate things in mongosh.

[pmachapman]

@Enkidu93 No problem, I can pick this up!

[pmachapman]

The procedure to restore a subset of the collections in a cluster is quite convoluted: https://www.mongodb.com/community/forums/t/how-to-restore-a-single-collection-from-a-mongodb-atlas-snapshot/211921

It looks like the best option is to create a new cluster.

[ddaspit]

We would want to restore a database not an individual collection. I would guess that it would be simpler.