Question
Nordea
SE
Last activity: 15 Jul 2022 8:07 EDT
Migrate attachments in smaller chunks
Hi,
we are planning to move all our attachment from database to external repository and I understand the same is explained here - https://docs-previous.pega.com/case-management/87/storing-case-attachments-using-external-storage
our production environment has approx 2 TB attachment and we are bit concerned about the performance issue during migration and the time it takes. is there any way we can control/limit the number of files that can be migrated in one process so that we can perform the migration in multiple attempts (in case it takes long time to move the 2 TB attachments in a day)
TATA Consultancy Services
IN
@AnandP Its depends on the external system accepting the load. We have done the below process to handle number of records and moving the attachment to repository.
1. Advanced agent/Scheduler browse the Link-Attachment instance queue to Standard Agent/Queue Processor and Use DSS to control the number of record browsing and processing it.
2. The Standard Agent/Queue Processor process the queue items update to repository as well in PEGA application.
3. Monitor the Scheduled and Brocken queue items
4. Based on the queue processing performance increase/Decrease the attachment records in DSS
5. Example: 1500 records take 15min. Configure the Advanced agent/Scheduler with buffer time gap for the next run.
6. The performance and process depends on attachment size and network capability
Nordea
SE
@Nadimuthu T Thanks for the quick reply. If I understand you correctly, in this scenario the migration needs to be triggered through a custom agent rather than OOTB attachment migration wizard as the same does not provide any option to limit the number of records?
Nordea
SE
@Nadimuthu T seems another option is to customize the ootb activity - pzQueueAttachmentsForMigration (called from OOTB migration wizard) to limit the number of records