File Blocking is provided as a component of the FSA Agent. When you add a new file server the wizard gives you the option to include File Blocking. If you have an existing file server, you can add the FSA Agent by right-clicking the file server and selecting "Install FSA Agent".
See Adding file servers.
Note: |
To use File Blocking in a clustered file server environment, you must configure an FSA resource in the cluster group that holds the virtual server resource. See About FSA clustering. |
You configure File Blocking within a volume policy and then apply that policy to disk volumes. It is possible for the volumes also to be processed by a File System Archiving task, but there is no requirement to do this.
You configure File Blocking for a volume by applying a volume policy in which you have defined File Blocking rules. The rules control the file types that are allowed on the volume, which folders to monitor, and the actions to take when a policy violation occurs.
For example, the action could be to allow the file to be created but for a warning message to be sent to the user and the event to be logged.
File Blocking quarantines those files that are blocked because of content-checking. Files that are blocked because of their file types are not moved to quarantine.
In summary, you must do the following to configure File Blocking:
On NTFS file servers, install the FSA Agent.
See Adding file servers.
If you are adding File Blocking for a NetApp filer, you must already have installed File Blocking on a Windows file server target that is able to run the File Blocking service on behalf of the NetApp filer.
Note: |
Do not install the FSA Agent on an Enterprise Vault server. An Enterprise Vault server cannot act as the File Blocking agent server for a NetApp filer. |
It is possible for a Windows file server to perform File Blocking for more than one NetApp device, but for best performance you are recommended to have one Windows file server per NetApp device.
See Adding file servers.
Define local quarantine locations. Each file server requires a quarantine location that is used when Enterprise Vault moves blocked files to quarantine.
In the case of NetApp devices, the quarantine location must be on the Windows file server that is running the File Blocking service for the NetApp device.
(Optional) Configure a central quarantine location. When this is defined, it is used in preference to the local quarantine locations on each file server. If the central location is not available, the local quarantine locations are used.
Specify how Enterprise Vault is to send mail when a File Blocking rule requires a mail notification.
Optionally, specify for each file server, a list of users whose files are exempt from File Blocking.