The restoration is done by large in parallel. There is obviously some additional time required to process a large amount of exports by nature, but considering the restoration phase internally takes a few hours, the overall export of a 10k job should typically be completed within half a day.
Robert -- the 100 recordings limit is on the batch download API. The S3 bulk export job can go well beyond that per job.
------------------------------
Director, Product Management – Recording and Real-time Supervision
Workforce Engagement Management (WEM)
------------------------------
Original Message:
Sent: 01-16-2025 12:22
From: Braiden Woodward
Subject: Genesys Recordings - Archive and Unarchive Concerns
Hi Daniel,
Thanks for this information. How does it work if you're doing this in bulk with say 10,000 archived interactions, does it take hours per interaction for the job to finish? ie it will take a very long time to do this in bulk?
We have also noticed the Genesys job will say it is complete, but it hasn't and it is still trickling the files into the S3 bucket. Does this timeout eventually or will it continue until it has unarchived and exported all recordings?
------------------------------
Braiden Woodward
Service Delivery Team Lead
Original Message:
Sent: 03-20-2024 12:36
From: Daniel Ho
Subject: Genesys Recordings - Archive and Unarchive Concerns
Hi Santiago,
The recording bulk action API supports exporting already archived recordings, directly. Internally we will temporarily restore the recording from Glacier (which will take a few hours) and then export them once restored. That restoration does not count towards the 100 restoration limit.
------------------------------
Daniel Ho
Product Line Manager – Recording and Quality Management, Genesys Cloud
Workforce Engagement Management (WEM)
Original Message:
Sent: 03-18-2024 08:18
From: Santiago Serna
Subject: Genesys Recordings - Archive and Unarchive Concerns
Hi @Genesys,
I would appreciate if you give us light on following question.
We are theoretically proposing the use case for an "exit plan" regarding recordings stored in Genesys' AWS subscription.
Assuming that we store all recordings in the AWS subscription of Genesys Cloud
- We set up a policy to archive interactions over 90 days old and pass them to long-term storage (Glacier).
- So we'll only have calls from last 3 months available for consult in a S3 Frequent Access.
After a couple of years we want to take ALL the conversations out from Genesys' AWS subscription (those that are in Glacier and the ones in S3 Frequent Access) and export them to our S3.
In order to accomplished that, which would be the recomended solution?: set up a bulk policy to move them to OUR S3 Bucket or use API to Bulk Download?
Our concerns are:
- Can the recordings in Genesys long-term be exported directly to our AWS subscription ? Or should we have to unarchive and then export them to our Bucket?
- If we have to unarchive and go through Genesys S3 Frequent Access, will we exceed the storage included in Fair Use Policy and incur in extra costs?
- Would the limitation "Your organization can restore up to 100 archived interactions at a time" apply to our use case?
Hope to have explained and look forward to hear your recommendations.
Thanks in advance
#ArchitectureandDesign
#SystemAdministration
------------------------------
Santiago Serna
Banco Santander Totta S.A.
------------------------------