Deleting a STU fails if still defined in any SLP version

Problem

When trying to delete a Storage Unit when decommissioning a storage server, getting this error:

Error Message

Storage unit or storage unit group cannot be deleted because it is referenced in a storage lifecycle policy. The referencing SLP may be an older version. Use the nbstl command to view/change older SLP versions
Status code: 228

Cause

You cannot delete a storage unit or storage unit group if a storage lifecycle policy (SLP) references it. The SLP may be an older version. The NetBackup Administration Console displays the most recent version of an SLP while the reference to the storage unit or storage unit group may be located in a earlier version.

Solution

Run this command to find all versions of the SLPs; then isolate the SLPs that need to be changed:

nbstl -L -all_versions > /admin/nbstl_all_versions.txt

Name: Example-SLP-Name
                 Data Classification: (none specified)
            Duplication job priority: 0
                               State: active
                             Version: 0                          <---------- Note The Version Needing Change
Operation  1              Use for: 0 (backup)
                             Storage: stu_adv_example12
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: 0 (Fixed)
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: 0 (client)
                        Operation ID: 0
                     Operation Index: 1
Operation  2              Use for: 1 (duplication)
                             Storage: Original_PD_STU             <---------- Remove this one
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: 0 (Fixed)
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: true
                               State: active
                              Source: Operation 1 (backup:stu_adv_example12)
                        Operation ID: 0
                     Operation Index: 2
Operation  3              Use for: 3 (replication to remote master)
                             Storage: Remote Master
                         Volume Pool: (none specified)
                        Server Group: (none specified)
                      Retention Type: 0 (Fixed)
                     Retention Level: 1 (2 weeks)
               Alternate Read Server: (none specified)
               Preserve Multiplexing: false
      Enable Automatic Remote Import: false
                               State: active
                              Source: Target 2 (duplication:Original_PD_STU)
                        Operation ID: 0
                     Operation Index: 3


Need to change, for example, Original_PD_STU to stu_disk_chang-to14 for version 0, operation 2, of this SLP in EMM SLP tables.  There must be the same number of arguments as the number of operations in the SLP (in this case, 3 operations means 3 arguments after "-residence").  We must specify the arguments in the same order as the operations.  So in the example below, only the second argument is different than what is already defined, and we will specify the existing values for operation1 and operation 3.  The Value of __NA__ is used when a residence is "Remote Master" for replications.  __NA__ is generally a placeholder for NULL in this command for other values.

nbstl Example-SLP-Name -modify_version -version 0 -residence stu_adv_example12,stu_disk_change-to14,__NA__
<command>SLP Name<action (i.e. modify_version)><action qualifier, if needed><what we're modifying>value for Operation 1,value for Operation 2,value for Operation 3,


To think of it another way, the command is technically modifying ALL the residences, and you have to re-supply the values for all Operations in the correct order, with the change in-line (in the above example, Operation 2, or the second comma-separate value, is the only one that is different.  All the other Operations will be 'modified' with the same value that was previously defined, so no effective changes for Operation 1 and Operation 3 above.


Once this was done, we were able to delete the Storage Unit in the Administration Console.  This change does not alter any historical Storage Lifecycle Operations; in other words, this will NOT re-duplicate any SLP Complete images to the altered storage unit.  This change is ONLY for deleting the Storage Unit and effecting incomplete images for this Storage Lifecycle Policy.

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)