Hi,
just wondering how the versioning of binary files works in Matrix.
Is there any information published anywhere or could someone summarise briefly how it works?
I'm asking those question mostly in relation to disk space.
What happens for example if a user, re-upload a PDF, 4-5 times?
Cheers.
Versioning of binary files works the same as any other file - the older versions of the files are stored in the data/file_repository directory, so they can be accessed through rollback mode.
In the upcoming 3.8 version, you will be able to purge versions of files in the file repository that are older than a certain age, as an option in the rollback management script.
A little more information: Every version of the file uploaded is stored in the data/file_repository/asset_type/ location for the file asset. Then, the latest copy of the file is stored either in date/private or data/public, based on the current status and permissions of the asset itself.
So, you'll always have n + 1 copies of the file (where n is the number of versions).
Actually, n + 2 at most. A copy is stored in both the public and private dirs for files if they are public. If the public file dir is blown away, Matrix can still reconstruct it.
[quote]Actually, n + 2 at most. A copy is stored in both the public and private dirs for files if they are public. If the public file dir is blown away, Matrix can still reconstruct it.
[right][post=“8593”]<{POST_SNAPBACK}>[/post][/right][/quote]
Cool. I didn’t think to check if the private copy was maintained. 
Thanks for that, Backup and regular trimming should take care of disk space concerns.