Simple guidelines on how to modify attributes of SLP version

Article:TECH145081  |  Created: 2010-11-28  |  Updated: 2011-08-16  |  Article URL http://www.symantec.com/docs/TECH145081
Article Type
Technical Solution

Issue



After modifying storage unit of SLP policy, the old SLP duplications would not start.


Error



N/A


Environment



SLP versioning is available from Netbackup 6.5.5 onwards.


Cause



The old SLP duplication jobs are not picking up the changed SLP settings while newly started duplication jobs are using the new settings.

It is possible customer setup SLP duplication to multiple destinations. After making copy1, customer changes the storage unit (STU) in SLP policy for copy1, and source STU for copy2 is the destination STU for copy1.

As a result, copy2 can never be made and in SLP_state 1 (NOT _STARTED)


Solution



1) How to get details of all SLP versions?

Run command:
(for UNIX) /usr/openv/netbackup/bin/admincmd
(for Windows)  \Netbackup\bin\admincmd

# nbstl -L -all_versions

                           Name:  SLP1

                           Version: 1
Destination 1    Use for: backup
                           ...
                           Storage Unit:  STU1
                           ...

Destination 2    Use for: duplication

                           ...
                           Storage Unit:  STU2
           Alternate read server:   __NA__
                            ...

                           Name:  SLP1
                           Version: 0
Destination 1    Use for: backup
                           ...
                          Storage Unit:  STU3
                           ...

Destination 2    Use for: duplication
                           ...
                           Storage Unit:  STU2
           Alternate read server:   __NA__
                           ...

Suppose you want to change the above backup storage unit for SLP1 version 0 to STU1, the command is:


# nbstl  SLP1  -modify_version -version 0 –residence STU1,STU2

STU1 is the value you want to change to (for destination 1)
STU2 is the value to remain the same (for destination 2), but you still have to specify it in the command. Otherwise you will get "invalid command usage".

How it works is, for SLP1 if you have 2 destinations, you need to have 2 values in each attributes modification.

Example 1:
           
     To change STU (for destination 1 only) and alternate read server (for destination 2 only) for SLP1 version 0

           # nbstl SLP1 -modify_version -version 0 -residence STU1,STU2 -as __NA__,readhost1

Example 2:
           
     If policy SLP3 has 3 destinations and you want to change the last duplication STU to STU4 for SLP3 version 1

           # nbstl SLP3 -modify_version -version 1 -residence STU1,STU2,STU4    (where STU1, STU2 are the same as orig value, and STU4 is the new value)

Example 3: 
           
     How to display one specific SLP's versions ( where SLP3 below is the name of the SLP )

           # nbstl SLP3 -L -all_versions





Article URL http://www.symantec.com/docs/TECH145081


Terms of use for this information are found in Legal Notices