I understand that there are instances when an SLP will create a new version and these versions can be seen by running the following command:
nbstl -L -all_versions
What I'd like to understand is what actions cause a new version to be created as opposed to a modification of a current version. For example, if I have a single SLP which does a backup to disk then duplication to an MSDP on a different media server followed by a further duplucation tape library A which is version 0 then I modify this SLP by deleting the duplication to MSDP and also change the duplication from Tape Library A to Tape Library B instead - will that create a new version of the SLP or not?
If it doesn't create a new version, what scenario would create a new version?
Solved! Go to Solution.
Great - thanks Amol
And just to confirm, if I had a bunch of incomplete SLP backups that existed before I made any changes to the current SLP, these would retain the SLP version of the original SLP (before I made the SLP changes) and so wouldn't automatically adapt to the updated configuration? eg in my example, they would still try to duplicate to MSDP and the original tape libary A rather than the new tape library B?