Jul 28 2023 04:57 AM
Jul 28 2023 04:57 AM
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 checked out the largest sites.... YIKES!!!! Spotted PowerPoint files that were consuming almost 900 GB, Yes GB!! I drilled in to version history.....Turns out it is a 400-500MB PowerPoint, but had 500 versions (actually on version 735) but the default is to save 500 versions. So the number gets rather large as far as total storage consumption. I am sure in my use case example, the end user doe snot know this or care about having 500 versions. They would be happy with 3-10 versions to roll back to, but having to set this at the library level for all libraries is crazy.
This is crazy! I have found a PowerShell script that I am testing to eliminate all versions except xx (I am little surprised that this is not included with Library settings from MS, the only way a user can "cleanup" is delete all versions or go 1 by 1 and delete the older versions.
Oh, and the other thing I noticed is I can set version history limit via the interface for a Comms Site to 10 versions, but the lowest number I can set a Teams based SP site is 100... which if the file is 100-500 MB and lots of collaboration is happening, well that chews up a ton of storage. Outside of an extreme example or maybe legal requirement - how many versions do most users need to roll back to?
I am the only one that is feeling this pain? How are you managing this in your tenants without constantly buying more storage from MS? I am not against buying more storage when the service is being used, but this seems like a bad approach from MS to drive the version history to 500 by default and not provide a way to set the limit to something else for the entire tenant without having to develop our own solutions to manage this.
Jul 28 2023 07:11 AMSolution
Jul 28 2023 07:50 AM
Aug 10 2023 09:57 AM
Aug 10 2023 10:22 AM
newtoki@ It seems like you're dealing with a situation where versioning is consuming a large amount of storage for a tenant or user. If you're referring to data versioning within a software system, here are some potential steps and considerations to address this issue:
Assessment and Analysis: