Entity archive
This module provides a framework for archiving Drupal entity data to external storage, allowing you to keep your main database clean while retaining historical information. It uses a queue system and supports custom backend plugins for various storage solutions, such as MongoDB.
Provides functionality to archive entity information to some storage defined by the backend plugin. This can be needed for example if you want to keep database clean from old entities but don't want to loose entity information.
Features
- Structure for handling entity archiving using Drupal queue
- Allows defining own archiving backend plugins for different storage solutions
- Comes with MongoDB storage backend plugin but you can define your own
- See /admin/reports/status to see if entity archive is configured correctly
Note that this module doesn't introduce a way to populate the entity archive queue, you need to do it yourself. Good example could be to create cron that archives entities when they are x years old and then removes the entity from Drupal database once you confirmed that entity has been archived properly.
At the moment this module doesn't provide a way to view or restore the entity from the archive.
Post-Installation
Have archive backend ready for storing the entity information. The entity_archive module comes with MongoDB archive backend submodule. You can enable entity_archive_mongodb module to store entity data in MongoDB. See requirements from entity_archive_mongodb README.md-
After installation you can start adding Drupal queue items to entity_archive_queue_worker queue. See more details in the module README.md file.