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™ Administrator's Guide, Volume I
  3. Section IV. Configuring storage lifecycle policies (SLPs)
  4. Storage lifecycle policy versions
  5. Storage lifecycle changes and versioning
Veritas NetBackup™ Administrator's Guide, Volume I

Storage lifecycle changes and versioning

-all_versions

Use to display all versions of an SLP definition. Without specifying this option, only the most recent version is displayed by default.

-version number

Use to display a specific version.

-modify_current

Use with most nbstl configuration options to make changes to the current SLP version without creating a new version. Knowing the current version number is not necessary if this option is used.

-modify_version -version number

Use with most nbstl configuration options to make changes to a specific version without creating a new version.

Use -modify_current or -modify_version to change any of the following configuration options:

-dp

The duplication priority.

-residence

The storage unit to be used for each operation.

-pool

The volume pool for each operation.

-server_group

The server group for each operation.

-rl

The retention level for each operation.

-as

The alternate read server for each operation.

-mpx

The preserve multiplexing option for duplication copies.

Some fields require values for all of the operations in the SLP. Make sure that the number of values that are specified for the fields matches the existing operation count.

For example, in an SLP that contains three operations, to change the value of one, a value must be given for all three operations. Note that the values for all three operations are replaced. To change the value for the second operation, provide the existing values for the first and the third operations.

Some configuration options cannot be changed using -modify_current or -modify_version. To change any of the following options, you must create an entirely new SLP version:

-uf

The type of the operation.

-managed

The retention type for the operation: Fixed, Capacity managed, or Expire after copy.

-source

The source of an operation, used primarily in hierarchical SLP configurations.

-dc

The data classification of an existing version.

The number of operations. You cannot add an operation or remove an operation from the SLP definitions.

You cannot instruct an SLP to follow the configuration of a previous version that has been superseded. To revert to the behavior of a previous version, change the definition to match the earlier definition. The change creates a version with the same content as the previous version, but with a new version number.

More Information

Creating a storage lifecycle policy

Feedback

Was this page helpful?
Previous

About storage lifecycle policy versions

Next

When changes to storage lifecycle policies become effective

Feedback

Was this page helpful?