Hi @Bernardo_Garcia,
So if we want to involve an automated backup solution for mongo clusters (aka, mongo clusters intended as MongoDB deployments), then … do those clusters should be created within MongoOps Manager deployment context?
If so, then those mongo deployments will not have to do with atlas service, they will be indeed part of the MongoOps service deployment
If you have concerns or requirements around backup retention for your use case, it would be worth reviewing the Atlas - Snapshot Scheduling and Retention Policy documentation.
MongoDB Atlas has an integrated Cloud Backup feature for dedicated clusters (M10+). It sounds like your goal is to get Atlas backup snapshots regularly saved to storage in your own S3 buckets (per your earlier discussion on Moving existing atlas mongo snapshots to external storage.
There currently isn’t a feature to directly export cloud snapshots from Atlas to S3 at this stage. I expect you can work out your own custom solution using the Atlas API, but I also recommend sharing your use case as a feature suggestion on the MongoDB Feedback Engine so others can upvote, comment, and follow any updates.
Another thing is since my atlas cluster has three replicaset nodes (1 primary and two secondaries) perhaps a mongodump / mongorestore approach against the secondary nodes could be something sustainable? I am not sure, since the data in the short term will be GB for every snapshot, and the memory ram is just 2gb. I wouldl have to scale the cluster (M10 plan actually)
You could possibly perform the mongodump with the –host and --port options where the --host would be a secondary node in your cluster. Of course this does void the fact that the mongodump can still adversely affect mongod performance. It would, in the case of specifying a secondary node in the --host option, focus the possible adverse effects to that particular node.
So to sum up, Is mongo ops manager just useful when we raise a mongo deployment databases using MongoOps manager from the beginning right?
Ops Manager can be useful but the important thing in the context of this discussion is that it is to be used for self hosted MongoDB Deployments and cannot interact with MongoDB Atlas clusters / servers.
Hope this helps!
Jason