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. Veritas NetBackup™ Snapshot Client Administrator's Guide
  3. Policy configuration
  4. Backup Selections tab options when configuring a policy
Veritas NetBackup™ Snapshot Client Administrator's Guide

Backup Selections tab options when configuring a policy

Note the following about the options on the Backup Selections tab:

  • Snapshot Client policies do not support the ALL_LOCAL_DRIVES entry in the Backup Selections list (except for the VMware and Hyper-V snapshot methods).

  • For snapshots, the maximum pathname length is approximately 1000 characters (as opposed to 1023 characters for backups that do not use a snapshot method).

    See Maximum pathname length.

    The NetBackup Administrator's Guide, Volume I, describes other file-path rules.

  • When you configure a snapshot method in a MS-Windows policy, the backward slash (\) must be entered in the Backup Selections list after the drive letter.

    If the backward slash is not included, the snapshot image does not appear in the NetBackup catalog.

  • Wildcards are permitted if the wildcard does not correspond to a mount point or a mount point does not follow the wildcard in the path.

    Note:

    This is applicable to a Storage Lifecycle Policy that has snapshot as the first operation and does not contain any backup or replicate operation.

    For example, in the path /a/b, if /a is a mounted file system or volume, and /a/b designates a subdirectory in that file system: the entry /a/b/*.pdf causes NetBackup to make a snapshot of the /a file system and to back up all pdf files in the /a/b directory. But, with an entry of /* or /*/b, the backup may fail or have unpredictable results, because the wildcard corresponds to the mount point /a. Do not use a wildcard to represent all or part of a mount point.

    In another example, /a is a mounted file system which contains another mounted file system at /a/b/c (where c designates a second mount point). A Backup Selections entry of /a/*/c may fail or have unpredictable results, because a mount point follows the wildcard in the path.

    Information is available on the Cross mount points policy attribute.

    See Snapshot tips.

  • For a raw partition backup of a UNIX client, specify the /rdsk path, not the /dsk path. You can specify the disk partition (except on AIX) or a VxVM volume.

    Examples:

    On Solaris:

    /dev/rdsk/c0t0d0s1
     /dev/vx/rdsk/volgrp1/vol1

    On HP:

    /dev/rdsk/c1t0d0
     /dev/vx/rdsk/volgrp1/vol1

    On AIX and Linux:

    /dev/vx/rdsk/volgrp1/vol1

    On Linux:

    /dev/sdc1

    On AIX clients, backing up a native disk partition is not supported. A raw partition backup must specify a VxVM volume, such as /dev/vx/rdsk/volgrp1/vol1.

    Note that /dev/vx/dsk/volgrp1/vol1 (without the "r" in /rdsk) does not work.

More Information

Configuring a Snapshot Client policy

Feedback

Was this page helpful?
Previous

Configuring a Snapshot Client policy

Next

Off-host backup configuration options

Feedback

Was this page helpful?