Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section IV. End user
  4. Troubleshoot the Portal
  5. File selector wildcards

File selector wildcards

When specifying file paths in the Support Tools, wildcards may be used to select multiple files. All matching is case-insensitive, regardless of platform. Multiple paths can be specified by separating the paths by commas (with optional white space) for example, mbs/logs/, mbs/rawdata/. If a path contains a comma then you should enclose the entire path in [square brackets]. Note that doing so will preclude the use of some of the following wildcard options.

The following table displays potential wildcards for file selection:.

Table: File selector wildcards

Value

Description

<file path>

The exact file will be retrieved for example, mbs/conf/collectorconfig.xml

<directory path
> or <directory
 path>/

All contents of the directory will be retrieved for example mbs/logs/

*

Matches any part of the filename within the same directory. For example mbs/logs/*.log will get all .log files that are in the mbs/logs directory (but not in any sub-directories).

**

Matches any part of the path, including crossing directory boundaries. For example mbs/rawdata/**192.168.0.1** will retrieve any file in the mbs/rawdata directory or subdirectories that contains 192.168.0.1 in the filename.

/**/ (or **/ 
at the start 
of the path)

Matches zero or more directories. For example mbs/rawdata/**/192.168.0.1/** will retrieve any file under the mbs/rawdata directory that is also under a sub-directory named 192.168.0.1.

Note:

/**/ (or **/ at the start of the path) may only be present once.

?

Matches any single character. For example mbs/rawdata/192.168.0.? would match either of mbs/rawdata/192.168.0.1 or mbs/rawdata/192.168.0.2.

{a,b}

Specifies alternative values, exactly one of which must be matched. For example mbs/logs/{metadata,eventcollector}.log will retrieve either of mbs/logs/metadata.log or mbs/logs/eventcollector.log.

[characters]

Matches any single character that is specified within the square brackets. Either individual characters or a range may be specified. For example 192.168.0.[125-7] would match any of 192.168.0.1, 192.168.0.2, 192.168.0.5, 192.168.0.6, 192.168.0.7.

Note:

This wildcard cannot be used if the path is enclosed in square brackets.

[!characters]

Matches any single character that is not specified within the square brackets. Either individual characters or a range may be specified. For example 192.168.0.[!125-7] would match any of 192.168.0.3, 192.168.0.4, 192.168.0.8, but would not match 192.168.0.1.

Note:

This wildcard cannot be used if the path is enclosed in square brackets.

Feedback

Was this page helpful?
Previous

Requesting a support package

Next

Retrieving log files

Feedback

Was this page helpful?