Forum Discussion
Solved
Automatic version retention
Hey Guys, I've been looking into automatic version control options in SHP and came across the automatic retention setting. This guided me to this site https://learn.microsoft.com/en-us/shar...
- Versions are only created when the item is modified, so there should be any redundant ones. Well, unless the users are making redundant changes 😄
Versions are only created when the item is modified, so there should be any redundant ones. Well, unless the users are making redundant changes 😄
- The Microsoft definition of modified also include renaming the document or changing metadata. These actions also result in new document versions even though the document itself has not been modified. For small files the impact is limited but for large files with frequent changes this starts consuming your storage quota. There are apps that allow renaming, changing metadata without adding a new version.
- Thanks for the input.
The working of the versioning system isn't new to me and I realise it has its flaws like you so clearly mentioned in your reply.
While I was waiting for a reply on this, I enabled the auto retention feature in a test tenant and enabled it on a DL with a dummy file in it.
It indeed only created version for changes to the file and no redundant version were kept. Good stuff.
We're looking into this because we have (as example) 35MB PPTX files that are currently taking up 6-12GB of storage due to the versioning being set to unlimited / 500 max limit.
Autosave is such a pain in the **bleep** here.
I'm going to do some further testing on some DL's that aren't business critical. I have high hopes.
