There are situations in which you need to stop a running scan. A few examples follow:
Prioritization. While a scan on share A is running, you learn that potentially dangerous files were added to Share B. You want to scan Share B immediately, in as little time as possible. To maximize the performance of the scan on Share B, you can pause the first scan and then resume it later.
Troubleshooting. You are experiencing network problems. To help isolate the problem, you can pause all running scans. If the network problems persist, you can eliminate the File Protect appliance as a contributing factor, and then resume the scans.
Testing. You are configuring scans and testing different ways to filter them. After you start a scan, you quickly realize that it needs to be more fine-tuned. You can abort the scan and then configure another one that more closely meets your needs.
You can pause or abort scheduled or on-demand scans that are in progress, and then resume them when you are ready.
You can save preliminary, continuous, and on-demand scans and then start them when you are ready, instead of running them immediately. You can edit preliminary, continuous, on-demand, scheduled, and running scans to adjust their filters or other parameters.
You can delete configured, aborted, completed, and canceled scheduled scans. You cannot delete running, paused, and active scheduled scans. If you enter an fmps scan command for a scan that is deleted, you will see a message that states the scan is not found.
Important
Scans on shares containing a small number of files are paused or aborted almost immediately. However, if the share being scanned contains more than 10,000 files, there could be a delay of a few seconds or minutes from the time you pause or abort the scan and when the scan actually stops.
Prerequisites
Operator or Administrator access