MongoDb archival queries

  1. This limit applies per cluster, allowing a maximum of 50 online archives, of which up to 20 can be active at any given time. The remaining 30 must be in a paused state.

A paused archive will not continue archiving data from the cluster; only the 20 active online archives will transfer data to cloud object storage. However, queries executed on a paused archive will still return results without failure.

While this limit can be adjusted, please note that online archives utilize the cluster’s underlying resources. Increasing the limit may impact cluster performance.

  1. Queries on OA would be slower as compared to queries in the cluster. It would introduce latency in the query results to a few seconds
  2. Does not have such option.
  3. We do not have a pre-developed automated script to accomplish this. You will need to use the Atlas API or CLI to create one as per your requirements.
  1. For 7 days immediately after Atlas creates an archive, Atlas archives all data. After 7 days, Atlas archives data only when your data size reaches 5 MiB. If the data size is below 5MB after 5 days it won’t be archived.
  2. You have the option to delete archived data by setting the deletion age limit. Additionally, you can pause an individual archive and create a new one if it grows significantly. Some customers manage archives as large as 10TB without experiencing any issues.