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. When changes to storage lifecycle policies become effective
Veritas NetBackup™ Administrator's Guide, Volume I

When changes to storage lifecycle policies become effective

For the changes to become effective for a backlog of jobs, it may be necessary to cancel the applicable jobs.

When the nbstl command is used to alter an existing storage lifecycle policy version, those changes may not become effective immediately. The images that are managed by the SLP version that was altered may already belong to a job that is Active or Queued, as seen in the Activity Monitor. Once a job is queued, the characteristics (SLP attributes) are fixed for that job and subsequent changes to the definition have no effect. To make changes effective for a backlog of jobs, cancel the duplication jobs. The storage lifecycle policy manager creates and submits new duplication jobs for those images, using the changes to the configuration.

The following are conditions under which changes to an existing version are not immediately effective:

  • Changes to a Backup operation have no effect because the backup job is already underway or completed.

  • Changes to a Duplication operation do not affect the copies that previous duplication jobs created.

  • Changes to a Duplication operation do not affect the copies that have already been submitted and are currently represented by a duplication job in the Activity Monitor, whether it be Active or Queued. If you want your changes to apply to those active duplication jobs,cancel the applicable duplication jobs. Once the job is canceled, nbstserv re-forms and re-submits new duplication jobs for these copies, using the changes to the appropriate version of the SLP.

  • Changes to a Duplication operation affect the copies that have not yet been created and have not yet been submitted. (That is, they are not yet represented by a duplication job in the Activity Monitor). Your changes become effective for the next duplication session. Whenever nbstserv begins a new session, it re-reads the definitions for processing instructions.

  • If a duplication job does not complete successfully, unfinished images in the job are submitted as part of a new job. Changes to the version affect the resubmitted job.

Feedback

Was this page helpful?
Previous

Storage lifecycle changes and versioning

Next

Deleting old storage lifecycle policy versions

Feedback

Was this page helpful?