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. FlashBackup configuration
  4. Configuring FlashBackup policy for backward compatibility (UNIX only)
Veritas NetBackup™ Snapshot Client Administrator's Guide

Configuring FlashBackup policy for backward compatibility (UNIX only)

Before NetBackup 5.0, FlashBackup was a separate product with two built-in snapshot methods: snapctl driver (nbu_snap) for Solaris clients and a VxFS snap driver for HP clients. The configuration procedure for a pre-5.0 FlashBackup policy was different from the procedure in 5.0 and later, as follows:

  • Unless FlashBackup was combined with NetBackup 4.5 ServerFree Agent, the snapshot methods were preset to the snapctl driver (Solaris) and VxFS snap driver (HP).

  • The cache partition for the snapctl driver and VxFS snap driver had to be specified as a CACHE= entry in the policy's file list.

  • To use multiple data streams, other directives had to be added to the policy's Backup Selections (file) list.

The following procedure and related topics explain how to configure a FlashBackup policy with a CACHE= entry in the policy's Backup Selections list. This means of configuration is provided for backward compatibility.

To configure FlashBackup policy for backward compatibility (UNIX only)

  1. Leave Perform snapshot backups deselected on the policy Attributes tab. NetBackup uses nbu_snap (snapctl driver) for Solaris clients or VxFS_Snapshot for HP.
  2. On the policy's Backup Selections tab, specify at least one cache device by means of the CACHE directive. For example:
       CACHE=/dev/rdsk/c0t0d0s1

    This cache partition is for storing any blocks that change in the source data while the backup is in progress. CACHE= must precede the source data entry. Note the following:

    • Specify the raw device, such as /dev/rdsk/c1t0d0s6. Do not specify the block device, such as /dev/dsk/c1t0d0s6.

    • Do not specify the actual device file name. For example, the following is not allowed:

      /devices/pci@1f,0/pci@1/scsi@3/sd@1,0:d,raw
    • Wildcards (such as /dev/rdsk/c0*) are not allowed.

    • The CACHE entry must precede the entry for the source data you want to back up.

    • All entries in the Backup Selections list, including the source data, must be the full path name of a raw device in the form:

      On Solaris: /dev/rdsk/cxtxdxsx

      On HP: /dev/rdsk/cxtxdx

      where x is an integer.

    • For multiple data streams, you can include multiple entries in the Backup Selections list.

      For example:

      CACHE=/dev/rdsk/c1t4d0s0
      /dev/rdsk/c1t4d0s7
      CACHE=/dev/rdsk/c1t4d0s1
      /dev/rdsk/c1t4d0s3
      /dev/rdsk/c1t4d0s4
    • See Requirements for the cache partition.

    • See About the cache partition.

More Information

About the cache partition

Requirements for the cache partition

Directives for multiple data streams

Configuring FlashBackup policy for backward compatibility (UNIX only)

Feedback

Was this page helpful?
Previous

Configuring a FlashBackup policy

Next

About the cache partition

Feedback

Was this page helpful?