Skip to main content
NetApp Knowledge Base

How to configure file extension scanning for Vscan

Views:
63
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:
1/29/2025, 5:58:01 AM

Applies to

  • ONTAP 9
  • Vscan

Description

  • Explanation of the behaviour of the scanning process, specifically how inclusion and exclusion lists of file extensions function.

Note: Double extension is supported from ONTAP 9.14.1

  • The notation used in configuration examples in Procedure below was chosen for readability only and does not suggest a specific format or syntax to be used
Scanning Rules
  • Priority of Exclude List: If a file extension is present in both the include and exclude lists, the exclude list takes priority. This means the file will not be scanned.
  • Empty Include List: An empty include list is treated as "*", meaning all file extensions are included by default. In this scenario, if a file extension is not found in the exclude list, the file will be scanned.
  • Files Without Extensions: If a file does not have any extension, it will be scanned as the scan-file-with-no-ext field is by default set to true. Set this field to false if scanning of files without extension is not desired.
  • Priority of Longer Extensions: Longer extensions take priority over shorter ones. For example, an extension like “mk.out” takes priority over “out” for the file ontap.mk.out
  • Priority of Longer Extensions:
    • ONTAP Vscan supports filtering of files for scanning based on up to two extensions.
    • When dealing with double extensions (example, ontap.mk.out), take precedence over single extensions (example, ontap.out). For instance, if your exclude list contains both single and double extensions (such as ["mk.out", "out"]), the system will first attempt to match files against the double extensions.
    • If no match is found, it will then check against the single extensions.
    • This prioritization ensures that more specific file types are accurately filtered before considering more general ones.
  • Wildcard in Include List: The wildcard * in the include list will have the lowest priority compared to specific file extensions.

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.