Search
Welcome to M-Files Empower – our new support experience. We'd love to hear what you think!Give feedback
Home/Support and troubleshooting/Troubleshooting/Common problems

Destroying files in M-Files does not release disk space

Last updated on 28 September 2020

Admin
M-Files Admin

Overview

Deleting an object from M-Files vault does not remove it from the file storage or from the database. It rather gets invisible to normal users. User with appropriate permissions can see those deleted objects with search or view with defined filter "Deleted = Yes". Then the user with proper permission can permanently destroy those objects or undelete(recover) the deleted objects.

Solution

While using Firebird as M-Files vault database engine, destroying an object immediately removes related files to that object from the server for both object's metadata and File Data. There will be no need to run additional commands in this case. As while using Firebird as database engine in M-Files, the files are never stored within the database rather stored in file system managed by M-Files.

If MS SQL Server is being used as vault's database engine and storing file data on the disk space, objects removed from M-Files server as soon as objects are destroyed. But File Data stays on the disk until user runs Vault Optimization(Thorough) with "Delete the files of destroyed objects" option ticket from M-Files Admin. This is proper and only way to remove destroyed objects File Data completely from the server.


Figure 1: M-Files vault database optimization(Thorough).
 

Further Reading:

Deleting and Undeleting Objects:
https://www.m-files.com/user-guide/latest/eng/deleting_and_undeleting_objects.html

Manual Optimization:
https://www.m-files.com/user-guide/latest/eng/faq_manual_optimization.html

Maintenance Guidelines for M-Files Administrators (section 2.4.1):
https://kb.cloudvault.m-files.com/Default.aspx?#3ECA226F-7B54-428B-B539-DE443E6134EC/object/B56AF064-5AF1-47E0-98A3-4C26D7B77CCD/latest

 

Still need help?