Disk Cleanup- FineBI Help Document

Last update：November 20, 2025

Overview

Version

FineBI Server Version	Functional Change
6.0	/

Application Scenario

As the project running time increases, the memory occupied by the project also grows. You may often worry about which files can be cleaned up.

1. Since many intermediate system files, which ultimately serve no purpose, are generated without consideration for memory constraints, such files are continuously generated but will not be cleaned up.

2. As junk files accumulate in the project system without timely cleanup, they may degrade system performance and even cause a system crash eventually.

3. To save disk resources, you expect the project to take up less disk space, but do not know what can be cleaned up and what must be retained.

4. Manually cleaning up logs and other files is too time-consuming. You want to configure an automatic cleanup mechanism to reduce the O&M time.

Function Description

FineBI provides the Disk Cleanup function. You can safely and conveniently clean up the disk, which prevents business file loss risks due to accidental deletion and crashes caused by disk issues.

1. The Disk Cleanup function can help admins efficiently identify files that can be cleaned up in the system.

2. You can set the automatic cleanup logic for some files.

3. The disk can be efficiently cleaned up to save disk resources and prevent disk crashes.

Cleanup Logic

The Disk Cleanup function includes automatic cleanup and manual cleanup.

The following table lists the disk cleanup content and logic.

Folder/File	Usage	Automatic Cleanup	Manual Cleanup
Backup file	1. Default file path: FineBI installation directory\webapps\webroot\backup If the backup file path is customized, the custom path is scanned. 2. File usage: Project backup file 3. Cleanup level: Perform cleanup with caution.	Automatic cleanup is not supported.	The files of specific dates (day level) are directly displayed in the file path. You can manually select files of the required dates for cleanup. You are advised to clean up the files stored for more than three months. Files stored within three months are not displayed.
schedule	1. File path: FineBI installation directory\webapps\webroot\WEB-INF\schedule 2. File usage: Intermediate file generated by task schedule 3. Cleanable range: Keep the files generated within one year and clean up the rest. 4. Cleanup level: You are advised to perform cleanup.	Automatic cleanup is not supported.	The files of specific dates (day level) are directly displayed in the file path. You can manually select files of the required dates for cleanup. You are advised to clean up the files stored for more than 12 months. Files stored within 12 months are not displayed.
assets/vcs	1. File path: FineBI installation directory\webapps\webroot\WEB-INF\assets\vcs 2. File usage: FineReport template version management file 3. Cleanable range: Keep the files generated within 30 days and clean up the rest. 4. Cleanup level: You are advised to perform cleanup.	Keep the files generated within 30 days and clean up the rest.	Files are displayed not by date. All historical version files generated 30 days ago are merged and displayed together. The selected files will be cleaned up together. You are advised to clean up the files stored for more than 30 days. Files stored within 30 days are not displayed.
treasures	1. File path: FineBI installation directory\webapps\webroot\WEB-INF\treasure 2. File usage: Cloud O&M log package file 3. Cleanup level: You are advised to perform cleanup.	Keep the files generated within 12 months and clean up the rest.	The files of specific dates (day level) are directly displayed in the file path. You can manually select files of the required dates for cleanup. You are advised to clean up the files stored for more than 12 months. Files stored within 12 months are not displayed.
fanruan.log	1. File path: FineBI installation directory\logs\fanruan.log 2. File usage: FanRuan project operation log 3. Cleanup level: Perform cleanup with caution.	Keep the data generated within three months and clean up the rest.	Manual cleanup is not supported.
dump	1. File path: The file path is not fixed, and the system scans the exported dump file that has not been cleaned up in time. 2. File usage: dump file 3. Cleanup level: You are advised to perform cleanup.	Keep the files generated within one week and clean up the rest.	The files of specific dates (day level) are directly displayed in the file path. You can manually select files of the required dates for cleanup. You are advised to clean up the files stored for more than one week. Files stored within one week are not displayed.
Catalina.log	1. File path: Tomcat installation path\logs\Catalina.log 2. File usage: Tomcat operation log 3. Cleanup level: Perform cleanup with caution. 4. Notes If the log is not divided into volumes in Tomcat, do not perform cleanup.	Keep the files generated within one week and clean up the rest.	The files of specific dates (day level) are directly displayed in the file path. You can manually select files of the required dates for cleanup. You are advised to clean up the files stored for more than one week. Files stored within one week are not displayed.
Catalina.out	1. File path: Tomcat installation directory\logs\Catalina.out 2. File usage: Tomcat's standard output and standard error log 3. Cleanup level: Perform cleanup with caution. 4. Note If the log is not divided into volumes in Tomcat, do not perform cleanup. If the file does not exist in the Windows system, do not perform cleanup.	Keep the files generated within one week and clean up the rest.	The files of specific dates (day level) are directly displayed in the file path. You can manually select files of the required dates for cleanup. You are advised to clean up the files stored for more than one week. Files stored within one week are not displayed.

Manual Cleanup

Scanning the Disk

Select the files that need to be scanned, and click Start Scanning to immediately scan for redundant files that can be manually cleaned up, as shown in the following figure.

During the scanning, if you click Stop Scanning, the scanning will end, and redundant files that have already been scanned will be returned, as shown in the following figure.

After the scanning is complete, the platform will push the message "The disk has been scanned, which can be viewed under Intelligent O&M > Disk O&M." to the super admin, as shown in the following figure.

After the scanning is complete:

1. You will be informed of the total size of cleanable files.

2. You can expand the tree structure to view cleanable files.

3. You can view the size of each file.

4. You can click Rescan to rescan cleanable files.

Cleaning the File

On the scanning completion page, select the disk file to be cleaned up, and click Clean Now. The prompt "The selected file and data will be permanently cleaned up and cannot be restored." will pop up.

Click OK to clean up the required disk file.

During the cleanup, if you click Stop Cleanup, the cleanup will be interrupted, and the cleaned file cannot be restored, as shown in the following figure.

After the cleanup is complete, the platform will push the message "The disk has been cleaned, which can be viewed under Intelligent O&M > Disk O&M." to the super admin, as shown in the following figure.

After the cleanup is complete, you will be notified that "The cleanup is complete. The size of the file cleaned this time is XXX MB", as shown in the following figure.

Auto Cleanup

1. Log in to FineBI as the admin, choose System Management > Intelligent O&M > Disk O&M > Disk Cleanup, and click the icon to enter Global Setting.

2. Enable Auto Cleanup, set Auto Cleanup Interval, and click Save.

3. After Auto Cleanup is enabled successfully, the content that supports automatic cleanup will be automatically detected and cleaned up at 2:30 AM based on the configured interval.

Helpful
Not helpful
Only read

中文（简体）中文（繁體）日本語

English

Disk Cleanup