Hie Adobe Community,
Adobe services are configured in form of Author and Publish setup in our cluster, we are in process of upgrading the AEM 6.5 to later service patch versions.
On back of data clean up for preparing the cluster ready for upgrade/ backup, we noticed the segment store in publish instances are heavily consumed at storage levels (mostly because of 'data*.tar.bak' ).
/aem/crx-quickstart/repository # du -sh *
748.0K blobids
6.6G datastore
425.4M index
152.2G segmentstore
We are looking for safe options to clean up the bak files and configure auto clean of backup files after regular intervals. Please do advise over same.
Thanks
Pavan
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @Pavan_KumarTi ,
To clean up and reduce the size of the 'segmentstore' in AEM 6.5, particularly focusing on the 'data*.tar.bak' files, you can follow these steps. This will help you safely manage and clean up the repository before your upgrade:
Stop the AEM Instance: Before making any changes to the repository files, ensure the AEM instance is stopped to prevent data corruption.
./aem stop
Backup: Before performing any cleanup, ensure you have a full backup of your repository and any other critical data.
Run Offline Compaction: Run offline compaction to clean up the segment store. This process will remove old and unused segments.
java -jar aem-quickstart.jar -v -r compaction
Delete Old Backup Files: After running offline compaction, you can manually delete the 'data*.tar.bak' files. These are backup files created before compaction and are typically safe to remove after a successful compaction.
To configure automatic cleanup of old backup files and manage repository size, you can use the following OSGi configurations and repository maintenance tasks:
Configure TarMK Compaction: In the AEM Web Console, configure the TarMK compaction to run automatically and clean up old segments:
Enable Revision Cleanup: Configure automatic revision cleanup which includes compaction and other maintenance tasks:
Configure Blob Garbage Collection: To clean up unused blobs in the data store:
Here are some example steps to configure the automatic cleanup in AEM:
Access AEM Web Console: Open your browser and go to http://<AEM-HOST>:<PORT>/system/console/configMgr.
Configure TarMK Compaction:
Configure Revision GC:
Configure Blob GC:
By following these steps, you can effectively manage and reduce the size of your 'segmentstore' in AEM 6.5, ensuring a smoother upgrade and backup process.
Hi @Pavan_KumarTi ,
To clean up and reduce the size of the 'segmentstore' in AEM 6.5, particularly focusing on the 'data*.tar.bak' files, you can follow these steps. This will help you safely manage and clean up the repository before your upgrade:
Stop the AEM Instance: Before making any changes to the repository files, ensure the AEM instance is stopped to prevent data corruption.
./aem stop
Backup: Before performing any cleanup, ensure you have a full backup of your repository and any other critical data.
Run Offline Compaction: Run offline compaction to clean up the segment store. This process will remove old and unused segments.
java -jar aem-quickstart.jar -v -r compaction
Delete Old Backup Files: After running offline compaction, you can manually delete the 'data*.tar.bak' files. These are backup files created before compaction and are typically safe to remove after a successful compaction.
To configure automatic cleanup of old backup files and manage repository size, you can use the following OSGi configurations and repository maintenance tasks:
Configure TarMK Compaction: In the AEM Web Console, configure the TarMK compaction to run automatically and clean up old segments:
Enable Revision Cleanup: Configure automatic revision cleanup which includes compaction and other maintenance tasks:
Configure Blob Garbage Collection: To clean up unused blobs in the data store:
Here are some example steps to configure the automatic cleanup in AEM:
Access AEM Web Console: Open your browser and go to http://<AEM-HOST>:<PORT>/system/console/configMgr.
Configure TarMK Compaction:
Configure Revision GC:
Configure Blob GC:
By following these steps, you can effectively manage and reduce the size of your 'segmentstore' in AEM 6.5, ensuring a smoother upgrade and backup process.
@Pavan_KumarTi as mentioned by @HrishikeshKa segmentstore Compaction is only option, in this we have two options, 1. Online Compaction 2. Offline Compaction.
Please check adobe documentation for details.
Hi Shashi,
Thanks for sharing update, we have configurd online compaction which is runnign as expected weekly. Yet we are ended up with these large volumes of files 'data*.tar.bak' in our segment store.
Does these backup files are safe for me to remove straight away, or should i need to run the offline compaction before removing them ?
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies