Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

PowerProtect Data Manager 19.15 Network-Attached Storage User Guide

Guidelines for exclusion filters for NAS

Review the following guidelines for exclusion filters.

Excluding by file size

When viewing the size of a file on a remote file system, only the value in bytes is precise. The calculations used to round bytes to a different measurement are specific to each vendor and operating system. It is not recommended to use a non-byte measurement with the Equal to filter.

CAUTION: The calculations that are used in the following examples use base 2, since all operating systems use base 2. However, the PowerProtect Data Manager user interface performs calculations using base 10. If you are following these examples and providing a value in megabytes, convert the values that are documented from base 2 to base 10. Otherwise, use only bytes to avoid any chance of error.

For example, an asset host could indicate the following information for the size of a file:

Size: 750 MB (786,652,672 bytes)

If you use an exclusion filter of Equal to with a value of 750 MB, the rounding of bytes to megabytes almost certainly results in the file not being excluded.

Examples of exclusion filters to exclude this file by size include the following:

  • Equal to with a value of 786,652,672 bytes
  • Greater than or Equal to with a value of 749 MB or 785,000,000 bytes
  • Less than or Equal to with a value of 751 MB or 787,000,000 bytes

Using wildcards

Supported wildcards include an asterisk (*) to represent zero or more characters and a question mark (?) to represent zero or one character.

NOTE:Be careful when using the wildcard *. Depending on the wildcard location, you can match folders whose name matches the filter pattern and their contents, even when the names of those files do not match the filter. For example, *//log*.txt also excludes files with the .txt extension in a folder whose name starts with log, even if the names of the files do not start with log.

Unsupported characters in file and path names

File and path names that contain a comma () cannot be directly specified in a filter. To exclude such a file or path, use a wildcard.

Excluding by file type

The File Type filter enables you to exclude files and folders that use a file extension.

You can specify a single extension or multiple file extensions. Separate multiple entries with a comma and do not add a space between entries. You can also specify related extensions by using wildcards. For example, *.doc? matches both .doc files and .docx files.

Excluding by file and folders path

The Folder Path filter enables you to exclude files and folders in a specific path.

The following table provides examples for excluding files and folders using NAS supported folder path formats.

Table 1. Supported folder path formatsSupported folder path formats
Appliance Folder or File Path formats
Unity

CIFS :/sharename/foldername or filename

NFS :/sharename/foldername or filename

PowerStore

CIFS :/sharename/foldername or filename

NFS :/sharename/foldername or filename

Generic asset (NetApp)

CIFS :/sharename/foldername or filename

NFS :/sharename/foldername or filename

PowerScale

CIFS: powerscale:/ifs/sharename/foldername or filename

NFS : /ifs/sharename/foldername or filename

Excluding multiple paths

Use commas to separate multiple paths and do not add a space between entries. For example, to exclude the folder /sharename/folder1, and the folder /sharename/folder2, use the Folder Path filter /sharename/folder1,/sharename/folder2. Do not enclose each path in quotation marks.


Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\