The challenge
The Preservation Hold Library is where SharePoint keeps content that retention policy says cannot be destroyed, including files users have deleted. Nobody could say what was in an 8 TB library, what had been deleted from the live site, or by whom.
At that size the library view will not open, a browser-based tool cannot finish, and a multi-hour run that fails must not start over.
What we built
We built a .NET 8 console application that works through the library in order, keeps only running totals so memory use stays steady, and saves its progress so an interrupted run continues where it stopped. A SharePoint web part covers smaller libraries.
Output is a complete CSV file plus an Excel workbook with a capped detail sheet. The "deleted by" field is labeled as a best-available indicator, because SharePoint does not expose who deleted a file outside the audit log.
Outcome
Working at the scale it was built for. Testing during the build found and fixed issues that would otherwise have affected the results at 8 TB.