DOCUMENTATION: Suspending duplication operations in Storage Lifecycle Policies (updated for the NetBackup 6.5.2 release update)

Article:TECH62438  |  Created: 2009-01-08  |  Updated: 2009-01-08  |  Article URL http://www.symantec.com/docs/TECH62438
Article Type
Technical Solution


Environment

Issue



DOCUMENTATION: Suspending duplication operations in Storage Lifecycle Policies (updated for the NetBackup 6.5.2 release update)

Solution



Manual:
Veritas NetBackup Administrator's Guide, Volume I for UNIX and Linux Release 6.5, Page: 253
Veritas NetBackup Administrator's Guide, Volume I for Windows Release 6.5, Page: 249
Veritas NetBackup Commands UNIX and Linux Release 6.5, Page: 449
Veritas NetBackup Commands Windows Release 6.5, Page: 424

Modification Type: Supplement.

Modification:
A Storage Lifecycle Policy is a plan or map of where and how long backup data will be stored.  The Storage Lifecycle Policy determines to where the backup is initially written and where it is subsequently duplicated.  It also automates the duplication process and determines how long the backup data resides in each of location to which it is duplicated.

By design, Storage Lifecycle Policies initiate the duplication operations "as soon as possible" after the backup completes, and continues to retry the duplication until successful.  This usually means that the duplication jobs start a few minutes after the initial backup using the Storage Lifecycle Policy completes.

While it is desirable to run the duplication as soon as possible after the backup completes this can sometimes result in resource contention, particularly if the original backups are being sent to tape or SharedDisk storage and the duplications are being handled by an alternate host.  There may also be periods during which maintenance is being carried out and device access is limited.  In these circumstances it is useful to be able to suspend duplications.  

Storage Lifecycle Policies do not have a built in mechanism that allows the duplications to be suspended but the nbstlutil command can be used to deactivate individual Storage Lifecycle Policies thus preventing duplications from occurring.

Customers who wish to disable duplication operations in Storage Lifecycle Policies during particular periods should create scripts using the nbstlutil command and schedule them to run at particular times to disable and enable the duplication capability.

The following command can be included in scheduled scripts to prevent a Storage Lifecycle Policy called GOLD_SPL from duplicating backups:
nbstlutil inactive -lifecycle GOLD_SLP

Once this command has been issued no duplication operations will occur for the GOLD_SLP policy until the following command is issued:
nbstlutil active -lifecycle GOLD_SLP

Setting the Storage Lifecycle Policy to "inactive" will not stop duplications that are already in progress.

Note that setting the Storage Lifecycle Policy to inactive does not prevent backups from using it, the setting only prevents duplication of the original backups from occurring.

Duplication operations can also be prevented in the same way at the storage destination level.  In the case the Storage Unit or Storage Unit Group used for the duplication is specified with the -destination command line switch.  For example, the following command can be included in scheduled scripts to prevent duplication operations that write to the Storage Unit STU2:
nbstlutil inactive -destination STU2

Once this command has been issued, no duplication operations in any Storage Lifecycle Policy that write to STU2 will occur until the following command is issued:
nbstlutil active -destination STU2

Setting the duplication destination to "inactive" will not stop duplications that are already in progress.

Note that setting the destination Storage Unit or Storage Unit Group to inactive does not prevent backups from using it. The setting only prevents duplication of the original backups from occurring.

The change of status resulting from the issuing of these commands is persistent and the corresponding command must be issued to clear a particular status setting.

The active status of a particular Storage Lifecycle Policy or duplication destination can be determined using the nbstl command.  It is recommend that this command be included in scripts to confirm the current state before after issuing an nbstlutil instruction.  

The state of the Storage Lifecycle Policy or duplication destination is the last field in each line when using the command nbstl -l and is set to 0 for active and 1 for inactive.  The following example shows the change in the output of nbstl -l for a Storage Lifecycle Policy called GOLD_SLP when the duplication destination STU2 is disabled:

# nbstl -l

GOLD_SLP *NULL* 0 0
0 STU1 ONSITE *ANY* 0 0 *NULL* 0 0
0 STU2 OFFSITE *ANY* 0 3 *NULL* 0 0

# nbstlutil inactive -destination STU2

# nbstl -l

GOLD_SLP *NULL* 0 0
0 STU1 ONSITE *ANY* 0 0 *NULL* 0 0
0 STU2 OFFSITE *ANY* 0 3 *NULL* 0 1

The command nbstl -L displays more information about the fields displayed here.

For more information about the nbstl and nbstlutil commands, consult pages 409-412 of the Veritas NetBackup 6.5.2 Documentation Updates (linked below).





Legacy ID



307360


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


Terms of use for this information are found in Legal Notices