Hello,
We are currently running backup on Commvault (FR42) for MongoDB Atlas protection with an enterprise customer. Our understanding iis that Commvault orchestrates native Atlas cluster snapshots through the Atlas REST APIs, with no backup copy possible — the data never leaves the Atlas/AWS perimeter and cannot be materialized on a Commvault Cloud Lib...
However, MongoDB Atlas natively supports exporting Cloud Backup snapshots to a customer-owned object store (S3, Azure Blob, GCS) via the Atlas Admin API, including S3 Object Lock immutability and PrivateLink transfer. Since Commvault already integrates with this API for snapshot orchestration, we would like to understand:
- Is there a technical or product reason why Commvault does not leverage the Atlas snapshot export API to provide a true secondary copy (backup copy / air-gapped copy) of Atlas data under Commvault management?
- Is such an integration on the roadmap for an upcoming Feature Release? If not, what is the recommended Commvault-supported approach for customers with regulatory requirements to hold Atlas data outside the MongoDB/AWS perimeter?
Thx !!
