Storage lifecycle changes and versioning
Administrators can make changes to a storage lifecycle policy in one of the following ways:
Using the NetBackup Administration Console.
Any change that an administrator makes to an SLP using the NetBackup Administration Console creates a new SLP version. The new version is created when the changes to the SLP are committed or saved. The NetBackup Administration Console always displays the most recent version.
Using the NetBackup web UI.
Any change that an administrator makes to an SLP using the NetBackup web UI creates a new SLP version. The new version is created when the changes to the SLP are committed or saved. The NetBackup web UI always displays the most recent version.
Using the nbstl command.
If an administrator uses nbstl to change an SLP, nbstl creates a new version by default.
However, the nbstl command contains options to view different versions and to modify the definitions of existing SLP versions without creating a new version. The options are as follows:
-all_versions | Use to display all versions of an SLP definition. Without specifying this option, only the most recent version is displayed by default. |
-version number | Use to display a specific version. |
-modify_current | Use with most nbstl configuration options to make changes to the current SLP version without creating a new version. Knowing the current version number is not necessary if this option is used. |
-modify_version -version number | Use with most nbstl configuration options to make changes to a specific version without creating a new version. |
Use -modify_current or -modify_version to change any of the following configuration options:
-dp | The duplication priority. |
-residence | The storage unit to be used for each operation. |
-pool | The volume pool for each operation. |
-server_group | The server group for each operation. |
-rl | The retention level for each operation. |
-as | The alternate read server for each operation. |
-mpx | The preserve multiplexing option for duplication copies. |
Some fields require values for all of the operations in the SLP. Make sure that the number of values that are specified for the fields matches the existing operation count.
For example, in an SLP that contains three operations, to change the value of one, a value must be given for all three operations. Note that the values for all three operations are replaced. To change the value for the second operation, provide the existing values for the first and the third operations.
Some configuration options cannot be changed using -modify_current or -modify_version. To change any of the following options, you must create an entirely new SLP version:
You cannot instruct an SLP to follow the configuration of a previous version that has been superseded. To revert to the behavior of a previous version, change the definition to match the earlier definition. The change creates a version with the same content as the previous version, but with a new version number.
More Information