NetBackup Storage Lifecycle Policy (SLP) - FAQ.

By | February 14, 2016

NetBackup Storage Lifecycle Policy (SLP) is a powerful feature used not only for image duplication but also for disaster recovery purpose. In this post you can find answers for questions related to SLPĀ  that I received under some posts that I already wrote:

Q: If I change some settings on SLP, will those changes immediately affect old backup jobs (which are not yet duplicated) or they will apply only on new backup jobs?

A: Those settings will be applied to new backup jobs only. Even you do not change a name of SLP and modify the SLP using GUI, you will create a new version of SLP. If you need to apply settings to older jobs, you have to inactivate and modify the SLP using command nbstl. e.g.

  1. List of SLP versions.

    nbstl -L -all_versions

  2. Inactivate a SLP you want to modify.

    nbstlutil inactive -lifecycle name_of_SLP

  3. Modify the correct version of SLP. Example changing source and destination unit (STUA and STUB).

    nbstlutil name_of_SLP -modify_version -version nr -residence STUA,STUB

Q: During duplication, for what job Media server is responsible?

A: E.g. sending data (MSDP, tapes) or controlling OST storage via 3rd plugins.

Q: Is there any way to check duplication job progress and time to finish?

A: Yes, it is necessary to use NetBackup OpsCenter or command line nbstlutil with (repllist or pendimplist or stlilist) option.

Author: Mariusz

Architect (~ 15 years experience based on passion...) with strong background as a System Administrator and Engineer. Focused on Data Center Solutions: Virtualization/Cloud Computing and Storage/Backup Systems. Currently living in Poland.

3 thoughts on “NetBackup Storage Lifecycle Policy (SLP) - FAQ.

  1. kiran

    Hello Mariusz,

    A great explanation as it is. Appreciate you taking time and posting valuble information. however am stuck in a kind of situation.
    A few SLPs were modified in the source which had replication as an operation in them. and replication targets are de-commissioned.
    now if I have to break the trust to keep the environment clean, I am getting a message, "Trusted master servers are being referred by one or more storage lifecycle policies on the source or target domain(1592).

    is there a way that I can identify the replication operation only on the modified SLPs and skip it out on the images?


    1. Mariusz Post author

      Have you checked versions of SLP? please check it via nbstl -L -all_versions Probably, there are old SLP versions.

  2. claritch

    Are there any impact of I change the Volume Pools to another volume pools of all the Operations (Operation 1,2&3) of SLP?


Leave a Reply

Your email address will not be published.

fifteen − one =