Moving Attachment from DB to S3 - Attachment migration wizard
We are upgrading from 7.4 to Infinity 24.2 , we are moving to AWS cloud environment, and we need to move all attachment from pega data base to S3 bucket.
We are planning to use Attachment Migration wizard for this migration.
We need to migrate 5 million of records present in Link Attachment table which is equal or more than 3TB of data in work attach table.
We need clarification on below queries.
1. Do pega recommend using Attachment Migration wizard for higher volume of attachment migration like in our case which could be more than 3TB data and 5million records.
2.Do we need to consider creating multiple background processing node to run this migration in backend.
3.Do we need to do any customization in this queue processor.
4. Do we need to do this only during black out period or we can run this process in background and user can still access the system.
5.If I update my case type content storage to Repository instead of pega data base , how my existing attachments will be retrieved if user is trying to access those attachments, and my attachment migration wizard is still running in background.
6.How much time attachment migration wizard will take to move this data to S3.
7.If there is any exception during data migration how we can debug that.
8.What is recommended approach for confirming no conflict, data loss, or negative impact.
We are upgrading from 7.4 to Infinity 24.2 , we are moving to AWS cloud environment, and we need to move all attachment from pega data base to S3 bucket.
We are planning to use Attachment Migration wizard for this migration.
We need to migrate 5 million of records present in Link Attachment table which is equal or more than 3TB of data in work attach table.
We need clarification on below queries.
1. Do pega recommend using Attachment Migration wizard for higher volume of attachment migration like in our case which could be more than 3TB data and 5million records.
2.Do we need to consider creating multiple background processing node to run this migration in backend.
3.Do we need to do any customization in this queue processor.
4. Do we need to do this only during black out period or we can run this process in background and user can still access the system.
5.If I update my case type content storage to Repository instead of pega data base , how my existing attachments will be retrieved if user is trying to access those attachments, and my attachment migration wizard is still running in background.
6.How much time attachment migration wizard will take to move this data to S3.
7.If there is any exception during data migration how we can debug that.
8.What is recommended approach for confirming no conflict, data loss, or negative impact.
9.If system have issue and went down due to high usage or any other uncertain issue – what can be done under such circumstances.
10.How can we confirm from data base and S3 end that all migration is successful , can we close the wizard after executing it.