Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested answer

Cleanup excessive blob storage

(0) ShareShare
ReportReport
Posted on by 5
Hi community,
 
We are using a sandbox T4 Finops environment to act as a baseline with migrated data to other sandbox environments.
We start with a clean set of data and use DMF to load lots of zip files containing setup and transactional data(originating the source system from the customer)
 
Now I noticed in the admin powerplatform view that our file storage is very high.
This got me looking into the storage account used by Finops where I see a couple of folders keep coming back on multiple sandbox environments:
* DMF
* Documents
* temporary-file
 
The first one is containing those zip-files which we loaded via DMF.
Second is holding document attachments.(docuref-docuvalue attachments)
But I'm not sure about this last one, it seems it is holding again some DMF related data + also loads of .tmp files.
The total number of size of this last one is a staggering 480GB.
 
So I'm wondering if someone knows what kind of data ends up in this temporary-file folder + if there is an out-of-the-box approach into cleaning these?
I could just delete its contents but am afraid I might delete some data needed by the environment.
As for cleaning the DMF folder, I was hoping the: 'Job history cleanup' in DMF would handle that but documentation only talks about sql data, not uploaded blob files:
 
Guess important to take into account is that these sandbox environments are handled by MS so writing your own scripts to autoclean these storage accounts might stop working when any update gets enforced.
Anyone else facing this, knows a way to safely clean the storage account?
 
 
  • Suggested answer
    Community member Profile Picture
    5 on at
    Cleanup excessive blob storage
    Found out the reason as to why the files weren't picked up for deletion.
     
    These 2 parameters were empty on our side(since we started from a copy from a devbox environment):
    update FILEUPLOADCONFIGURATION set MAXBUNDLECOUNT = 4
    update FILEUPLOADCONFIGURATION set MAXFILESPERBUNDLE = 5000
     
    Fill them in and the batch job: â€˜Scans for tempory files that have expired’ will do the rest.
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Daivat Vartak – Community Spotlight

We are honored to recognize Daivat Vartak as our March 2025 Community…

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Kudos to the February Top 10 Community Stars!

Thanks for all your good work in the Community!

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 293,272 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,931 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156 Moderator

Leaderboard

Product updates

Dynamics 365 release plans