In the production environment, in a MongoDB Atlas database, a collection contains massive amounts of data stored, including aged and current data. However, aged data is not frequently accessed through applications, and the data piles up daily in the collection, leading to performance degradation and cost consumption. This results in needing to upgrade the cluster tier size to maintain sufficient resources according to workload, as it would be difficult to continue with the existing tier size.
Overall, this negatively impacts application performance and equates to higher resource utilization and increased costs for business.
Resolution
To avoid overpaying, you can offload aged data to a cheaper storage area based on the date criteria, which is called archival storage in MongoDB. Later, you can access those infrequently archived data by using MongoDB federated databases. Hence, cluster size, performance, and resource utilization are optimized.
To better manage data in the Atlas cluster, MongoDB introduced the Online Archive feature from MongoDB Atlas 4.4 version onward.
Advantages
It archives data based on the date criteria in the archival rule, and the job runs every five minutes by default.
Separate federated connection strings connect archived data.
Pre-requisites
Online Archive is supported by cluster tier M10 and above.
Indexes offer better performance during archival.
To create or delete an online archive, you must have one of the following roles:
Project Data Access Admin, Project Cluster Manager, or Project Owner.
Online archival configuration setup
The cluster DemoCluster has a collection called movies in the database sample_mflix. As per the business rule, you are storing aged and the latest data in the main cluster, but day by day, data keeps piling up, as expected. Therefore, right-sizing your cluster resources by upgrading tier size leads to increased costs.
To overcome this issue and maintain the cluster efficiently, you have to offload the infrequent or aged data to lower cost storage by the online archive feature and access it through a federated database connection. You can manage online archival at any point in time as per business requirements through managing archives.
In your case, you have loaded a sample dataset from the MongoDB Atlas cluster setup — one of the databases is sample_mflix — and there is a collection called movies that has aged, plus the latest data itself. As per the business requirement, the last 10 years of data have been frequently used by customers. Therefore, plan to implement archived data after 10 years from the collection based on the date field.
To implement the Online Archive feature, you need a basic M10 cluster or above:
Figure: Overview of cluster configuration details on MongoDB Atlas web browser
Define archiving rules
Once business requirements are finalized, define the rules on which data fields will be archived based on criteria like age, size, and other conditions. We can set up Online Archive rules through the Atlas UI or using the Atlas API.
The movies collection in the sample_mflix database has a date field called released. To make online archival perform better, you need to create an index on the released field using the below command.
After creating the index, you can choose this field as a date-based archive and move the data that is older than 10 years (3652 days) to cold storage. This means the cluster will store documents less than 10 years old, and all other documents move to archival storage which is cheaper to maintain.
Before implementing the archival rule, the movies collection's total document count was 21,349, as seen in the below image.
Figure: Before setting up online archive – sample_mflix database movies collection document count: 21,349
Implementation steps
Step 1: Go to Browse Collections on Cluster Overview and select the Online Archive tab.
Figure: Location to configure online archive from main cluster – DemoCluster
Step 2: You have to supply a namespace for the collection, storage region, date match field, and age limit to archive. In your case:
For instance, today is February 28, 2024, so that means that 3652 days before today would be Feb 28, 2014.
Figure: Configure an online archive – archiving rule criteria to configure online archive.
Step 3: Here are a couple of features you can add as optional.
Delete age limit: This allows the purging of data from archival storage based on the required criteria. It's an optional feature you can use as per your organization's decision.
In this example, we are not purging any data as per business rules.
Schedule archiving window: This feature enables you to customize schedules. For example, you can run archive jobs during non-business hours or downtime windows to make sure it has a low impact on applications.
Figure: Configure an online archive – archiving rule step and additional configuration criteria (optional)
Step 4: You can add any further partition fields required.
Figure: Configure online archive – partition query fields
Step 5: Once the rule configuration is completed, the wizard prompts a detailed review of your archival rule. You can observe Namespace, service provider (AWS), Storage Region (Mumbai), Archive Field, Age Limit, etc.
Figure: configure an online archive – Review and Confirm page
Step 6: Once the steps are reviewed, click on BeginArchiving to create data federation instances in the DataFederation tab. Then, it will start archiving data based on the validation rule and move to AWS S3 storage. One of the best features is you can modify, pause, and delete online archival rules any time around the clock. For instance, your archival criteria can change at any time.
Figure: configure an online archive – Begin Archiving confirm page
Step 7: Once the Online Archive is set, there will be an archive job run every five minutes by default. This validates criteria based on the date field and moves the data to archival storage. Apart from that, you can set up this job as per your custom range instead of the default schedule. You can view this archival job in the cluster main section as seen in the below image, with the actual status Archiving/IDLE.
Figure: Online archive – overview page from main cluster consolidated rule information.
The Atlas Online Archive feature will create two federated database instances in the Data Federation tab for the cluster to access data apart from the regular connection string:
A federated database instance to query data on your archive only
A federated database instance to query both your cluster and archived data
Figure: Data federation – online archive federated database instances window
When the archival job runs as per the schedule, it moves documents to archival storage. As a result, the document count of the collection in the main cluster will be reduced by maintaining the latest data or hot data.
Therefore, as per the above scenario, the movies collection now contains fresh/the latest data.
Movies collection document count: 2186 (it excludes documents more than 10 years old).
Every day, it validates 3652 days later to find documents to move to archival storage.
You can observe the collection document count in the below image:
Figure: movies collection latest count on base cluster after online archive setup.
How to connect and access
You can access archived or read-only data through the Data Federation wizard. Simply connect with connection strings for both:
Archived only (specific database collection for which we set up archive rule)
Cluster archive (all the databases in it)
** You can point these connection strings to downstream environments to read the data or consume it via end-user applications._
Atlas Data Federation
Data Federation provides the capability to federate queries across data stored in various supported storage formats, including Atlas clusters, Atlas online archives, Data Lake datasets, AWS S3 buckets, and HTTP stores. You can derive insights or move data between any of the supported storage formats of the service.
Figure: Once the archival job has run, we will see data movement to federated instances with details.
DemoCluster archive: This is a federated database instance for your archive that allows you to query data on your archive only. By connecting with this string, you will see only archived collections, as shown in the below screen. For more details check, visit the docs.
Here, the cluster name DemoCluster has archived collection data that you can retrieve only by using the below connection string, as shown in the image.
Figure: Data federation – federated instances connection string access steps
As shown in the image, you can view only those archived collections data in the form of READ-ONLY mode, which means you cannot modify these documents in the future.
Figure: Archived database collection – sample_mflix.moves data only from this connection string
DemoCluster cluster archive:
This federated database instance for your cluster and archive allows you to query both your cluster and archived data. Here, you can access all the databases in the cluster, including non-archived collections, as shown in the below image.
Connection string:
Note: Using this connection string, you can view all the databases inside the cluster and the archived collection’s total document count. It also allows READ-ONLY mode.
Figure: Archived cluster data – both your cluster and archived data access by using this instance/connection string
Project cluster overview
As discussed earlier, the main cluster DemoCluster contains the latest data as per the business requirements — i.e., frequently consumed data. You can access data and perform read and write operations at any time by pointing to live application changes.
Note: In your case, the latest data refers to anything less than 10 years old.
Connection string:
In this scenario, after archiving aged data, you can see only 2186 documents for the movies collection with data less than 10 years old.
Figure: MongoCompass – only latest data available on main cluster after online archive setup. Aged data can be accessed through separate federated database instances as discussed in the Federated Databases tab.
You can use MongoShell, an application, or any third-party tools (like MongoCompass) to access the archived data and main cluster data.
Alternatively, with all three of these connection strings, you can fetch from the below wizard in cluster connect.
Connect to cluster and Online Archive (read-only archived instance connection string)
Connect to cluster (direct cluster connection to perform CRUD operations)
Connect to Online Archive (read-only specific to an archived database connection string)
Figure: Three separate connection strings after online archive setup completed
MongoShell prompt: To connect both archived data from the Data Federation tab, you can view the difference between both archived data in the form of READ-ONLY mode.
Figure: ShellPrompt → The left side is only an archived database view; the right side is an Atlas online archive cluster databases view.
MongoShell prompt: Here in the main cluster, you can view a list of databases where you can access, read, and write frequent data through a cluster connection string.
Figure: ShellPrompt → Base cluster list of databases where CRUD operations are performed from the application
Conclusion
Overall, MongoDB Atlas's online archival feature empowers organizations to optimize storage costs, enhance performance, adhere to data retention policies by securely storing data for long-term retention periods, and effectively manage data and storage efficiency throughout its lifecycle.
We’d love to hear your thoughts on everything you’ve learned! Join us in the Developer Community to continue the conversation and see what other people are building with MongoDB.
Rate this article
Related
Tutorial
Exploring Window Operators in Atlas Stream Processing
May 02, 2024 | 4 min read
Industry Event
SYDNEY, AUSTRALIA | IN-PERSON
Developer Day Sydney
May 27, 2024 - May 28, 2024
Tutorial
Working with MongoDB Charts and the New JavaScript SDK
Apr 02, 2024 | 10 min read
Tutorial
MongoDB Atlas With Terraform: Database Users and Vault
_Thumbnail.png&w=3840&q=75)
