Forum Discussion
Solved
Versioning consuming TB's of tenant storage
Is anyone else seeing version history in Document libraries consuming HUGE (I am seeing TB's of storage consumed in my Tenant)? I noticed we were consuming a lot of storage month over month, so c...
This is a known limitation.
Organizations typically resort to using PowerShell scripts or apps (example) to keep the versions (and the associated storage consumption) under control.
Looks like Microsoft is going to address this: see Roadmap 145802
I have a tangential observation. We are also looking for solutions to keep versions from eating up our storage without losing all of the functionality. So, I created a new Doc Library and turned versioning OFF (via PnP Powershell). The plan is that users move Final versions of the files to this new library but collaborate and edit in the old library which still has versioning.
I did a test and moved files from the old library to the new library. I did get a warning that the new library had a lower version limit and that those versions would be lost. Great! However, the size, of those files collectively, and the site itself, is still exactly the same. So...did the versions really get deleted? I did wait about 24 hours as storage metrics don't seem to be real-time.
I did a test and moved files from the old library to the new library. I did get a warning that the new library had a lower version limit and that those versions would be lost. Great! However, the size, of those files collectively, and the site itself, is still exactly the same. So...did the versions really get deleted? I did wait about 24 hours as storage metrics don't seem to be real-time.