CM Repository File System Check 
Use
This report checks entries in the file system of CM repositories running in persistency mode DBFS or FSDB. The results list entries that can be deleted without risk.
Features
You can set the scope when you start the report.
Scope tab
Parameter |
Description |
CM repository prefixes with persistence mode DMFS or FSDB |
Automatic listing of all prefixes of CM repositories running in persistency mode DBFS or FSDB. Select at least one entry. |
You can specify the following parameters for the report.
Parameters tab
Parameter |
Description |
Minimum Size |
Minimum file size in bytes. To search for files of any size, choose -1. |
Minimum Age (Days) |
Age in days that orphaned files need to have in order to be found by the report. |
Collect Empty Folders |
If activated empty folders in DBFS mode are found. Empty folders can be deleted without risk. |
Collect Temporary Files |
If activated temporary files that the CM repository created beneath the root directory are found. Temporary files should normally be eradicated automatically by other means. If this does not happen you can find temporary files using this report and delete them. |
Collect Content Files |
If activated orphaned entries in the file system with no connection to the database are found. |
Collect Alien Files |
If activated all files or folders beneath the root directory are found that were not created by a CM repository manager and therefore do not match the naming convention. |
When you display the results you can use the Commands tab. You can delete objects found.
Commands tab
Command |
Description |
Remove |
Removes the selected objects from the file system permanently. |
The objects found are given an RID in the report. However, they do not represent resources. If you follow the link you receive an error message.
We recommend that you execute this report once a month. Carry out the report several times in succession to make sure that all entries with errors have been found and eradicated.
See also: