Forum Discussion
Scanning of Archive files
When scanning of archive files, we find that depending on the amount of archive files present (say on SQL server backups) the system disk space is used to unpack and scan the file.
This can cause the system drive to run out of disk space, and cause the scanning to fail or system to fail. At the moment there does not seem to be any configuration on where to extract the temporary files for scanning.
Can we add an option for this?
Hi SailCorpse,
Currently, as you've said, the system uses the system drive to unpack and scan archive files, and there's no configuration to change the location for temporary files. It would be great if we could add an option to specify a different location for temporary extraction, especially for large files like SQL server backups, to avoid disk space issues.
As a temporary solution to this, you could add an option to specify a different location for temporary files during scanning, especially for large files.
Another option is to increase disk space or optimize the scanning process to handle large archive files more efficiently. You could also consider allowing exclusions for certain large files to prevent system failures. These changes could help avoid the disk space issues you're experiencing.
Regards!
