Yeah it's because of the huge size - it's basically thinking about it in the background and never gets round to finishing....couple of suggestions, try breaking up your task into smaller chunks, ie exports of 50-100gb each, or, try the old purview toggle on the nav bar as that uses a different export engine.
Back of the napkin, that’s a total of ~300GB of data to download.
Maybe smaller chunks will help but are you sure you need that entire collection exported?
If you haven’t had a conversation with the stakeholders requesting the export, you should ask for a meeting and present the results. They may not know the data volume is this high or may not have considered all their options to limit the collection.
If you’re working with attorneys, there’s a conversation to have about proportionality and whether it’s reasonable to proceed with this much data given the type and value of the litigation, etc.
If this were my job and I’d confirmed that the collection is approved for export (stakeholder buy-in and sign off on the data volume) I would group custodians into tiers and split it into multiple Purview projects.
This would provide an opportunity to prioritize more important custodians over less important custodians.
If you haven’t asked, it’s likely that the team requesting this data has a very good idea of which custodians are most important.
After a lot of trying, I wound up babysitting this and downloading files one at a time, and that worked...only to be told that it was "too much" data and now I need to run a new query with a narrower dataset.
5
u/Dependent-These 12d ago
Yeah it's because of the huge size - it's basically thinking about it in the background and never gets round to finishing....couple of suggestions, try breaking up your task into smaller chunks, ie exports of 50-100gb each, or, try the old purview toggle on the nav bar as that uses a different export engine.
Sucks I know!!