Overview
Version
| Report Server Version |
|---|
| 11.0.4 |
Application Scenario
As the project running time increases, the memory occupied by the project also increases. You may often worry about which files can be cleaned up.
1. Many system files in intermediate forms are finally useless. Since factors such as memory are not taken into consideration, such files are continuously generated but will not be cleaned up.
2. If there are more and more junk files that are not cleaned up in time in the project system, the system running status may be affected and even the system crash may be caused.
3. You hope that the project does not take up too much disk space, but do not know what can be cleaned up and what cannot be cleaned up.
4. Manually cleaning logs and other files is too time-consuming. You want to configure an automatic cleanup mechanism to reduce the O&M time and cost.
Function Description
FineReport provides the Disk Cleanup function. You can safely and conveniently clean the disk, preventing business file loss risks and crashes caused by disk issues.
1. Disk O&M allows you to perform disk cleanup with efficient recommendations for removable files.
2. You can set automatic cleanup logics 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.
Automatic cleanup requires no frontend settings and is used to directly clean the disk in the background.
For details about manual cleanup, see the following section.
The following table lists the disk cleanup content and logic.
| Folder/File | Usage | Automatic Cleanup | Manual Cleanup |
|---|---|---|---|
Backup file | 1. File path: %FR_HOME%\webapps\webroot\backup by default 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 folders of specific dates (day level) are directly displayed in the file path. You can manually select folders of required dates for cleanup. You are advised to clean up the files stored for more than 3 months. Files stored within 3 months are not displayed. |
schedule | 1. File path: %FR_HOME%\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 the rest. 4. Cleanup level: You are advised to perform cleanup. | Automatic cleanup is not supported. | The folders of specific dates (day level) are directly displayed in the file path. You can manually select folders of 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: %FR_HOME%\webapps\webroot\WEB-INF\assets\vcs 2. File usage: Version management file 3. Cleanable range: Keep the files generated within 30 days and clean the rest. 4. Cleanup level: You are advised to perform cleanup. | Keep the files generated within 30 days and clean 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: %FR_HOME%\webapps\webroot\WEB-INF\treasures 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 the rest. | The folders of specific dates (day level) are directly displayed in the file path. You can manually select folders of 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: %FR_HOME%\logs\fanruan.log 2. File usage: FanRuan project operation log 3. Cleanup level: Perform cleanup with caution. | Keep the data generated within 3 months and clean the rest. | Manual cleanup is not supported. |
dump | 1. File path: Dump files that are exported after system scanning and have 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 1 week and clean the rest. | The folders of specific dates (day level) are directly displayed in the file path. You can manually select folders of required dates for cleanup. You are advised to clean up the files stored for more than 1 week. Files stored within 1 week are not displayed. |
Catalina.log | 1. File path: %TOMCAT_HOME%\logs\Catalina.log 2. File usage: Tomcat operation log 3. Cleanup level: Perform cleanup with caution. 4. Note If the log is not divided into volumes in Tomcat, do not perform cleanup. | Keep the files generated within 1 week and clean the rest. | The folders of specific dates (day level) are directly displayed in the file path. You can manually select folders of required dates for cleanup. You are advised to clean up the files stored for more than 1 week. Files stored within 1 week are not displayed. |
Catalina.out | 1. File path: %TOMCAT_HOME%\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 1 week and clean the rest. | The folders of specific dates (day level) are directly displayed in the file path. You can manually select folders of required dates for cleanup. You are advised to clean up the files stored for more than 1 week. Files stored within 1 week are not displayed. |
Manual Cleanup
Disk Scanning
Log in to the decision-making system as the admin and choose System Management > Intelligent O&M > Disk O&M > Disk Cleanup.
Select the files that need to be scanned, and click Start Scanning to immediately scan redundant files that can be manually cleaned up.
During the scanning, if you click Stop Scanning, the scanning will end and redundant files that have already been scanned will be returned.
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 administrator.
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 Recommended Option to automatically select all files advised to be cleaned up.
5. You can click Rescan to rescan cleanable files.
File Cleanup
On the scanning completion page, select the disk file to be cleaned and click Clean Now. The prompt "The selected file and data will be permanently cleaned and cannot be restored." will pop up.
Click OK to clean the required disk file.
During the cleanup, if you click Stop Cleanup, the cleanup will be interrupted and the cleaned file cannot be restored.
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 administrator.
After the cleanup is complete, you will be notified that "The cleanup is complete. The size of the file cleaned this time is XXXM", as shown in the following figure.
Automatic Cleanup
1. Log in to the decision-making system as the admin and choose System Management > Intelligent O&M > Disk O&M > Disk Cleanup > Global Setting.
2. Enable Auto Cleanup, set Auto Cleanup Interval, and click Save.
3. Wait until Auto Cleanup is enabled successfully. Then the content that supports automatic cleanup will be automatically detected and cleaned up at 2:30 a.m.
Previous：Disk Usage Analysis
