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. NetBackup™ Web UI Administrator's Guide
  3. Section VI. Configuring backups
  4. Managing policies
  5. About dynamic multi-streaming
  6. Considerations and prerequisites
NetBackup™ Web UI Administrator's Guide

Considerations and prerequisites

  • NetBackup 11.2 or later must be installed on the primary server, media server, and client.

  • The client platform must be RHEL 9.x.

  • The same protocol node (NetBackup client) must be used to back up a share. If the protocol node changes, the NetBackup client in the policy also changes, and the next backup runs as a full backup.

Supported NetBackup features

You can use dynamic multi-streaming along with the following NetBackup features.

  • Incremental backups

  • Accelerator

  • Checkpoint restart

  • Client-Direct with MSDP storage

  • Auto Image Replication (AIR)

  • Duplication

  • Malware scanning

  • Intelligent Catalog Archiving (ICA)

  • Include/Exclude lists

  • WORM storage target

  • Granular file recovery

Known limitations

Dynamic multi‑streaming does not support certain NetBackup features and configurations. These include the following:

  • A single share can be backed up by only one NetBackup client.

  • Inline Entropy Analysis is not supported when dynamic multi-streaming is enabled for a Standard policy.

  • Synthetic schedules

  • Multiplexing

  • Storage unit set with the ANY option.

  • Bare Metal Restore (BMR)

  • Use of the ALL_LOCAL_DRIVES directive.

  • True Image Restore (TIR)

  • User specified backup or archive schedules.

When you plan or configure dynamic multi‑streaming, ensure that you do not use any unsupported options to avoid operational issues.

Feedback

Was this page helpful?
Previous

About dynamic multi-streaming

Next

Policy configuration

Feedback

Was this page helpful?