Forum Discussion

HEMANPR's avatar
HEMANPR
Level 6
15 years ago
Solved

Catalog Priority over SLP_LCP Duplicated Jobs

Hello People

I'm doing backups to disk and duplication to tape using LCP. I have 2 drive availables for the duplication jobs.

I set a Vault for eject the completed images duplicated in tape and create a catalog of Netbackup.

The Catalog Job are going to Queue and take almost 30hrs to run. I set the priority of the Catalog to 99999 and the backup job to 90000 for try to get first the catalog job but don't work. Catalog Job still waitting for tape drive and LCP duplication jobs continue using the tape drive for duplication. I can't set to Suspend the SLP LCP Duplicated jobs.

How can I fix this?

Suggestions?  Any work around for try to solve this issue?

7.1.x and Earlier
Backing Up
Backup and Recovery
Best Practice
Configuring
Features
NetBackup
Performance
Tip-How to
Troubleshooting
  • Marianne's avatar
    Marianne
    15 years ago

    This is all I can find: http://www.symantec.com/docs/TECH62438

    DOCUMENTATION: Suspending duplication operations in Storage Lifecycle Policies

    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.

     

    (See TN for more info)

6 Replies

  • HEMANPR's avatar
    HEMANPR
    Level 6
    15 years ago

    Please Team Any Help or Idea? I change the priority on my catalog (99999) and duplicated jobs(90000) but the duplicated still run priorly to the catalog.

    Help Please

  • HEMANPR's avatar
    HEMANPR
    Level 6
    15 years ago

    Please People any suggestion, Idea or Recomendation for this? Thanks

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    This is all I can find: http://www.symantec.com/docs/TECH62438

    DOCUMENTATION: Suspending duplication operations in Storage Lifecycle Policies

    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.

     

    (See TN for more info)

  • HEMANPR's avatar
    HEMANPR
    Level 6
    15 years ago

    Hello Marianne

    I will try ASAP this. I create a script with the inactive and active options.

    I will tell you the results. One's again, THANK YOU very much for your help.

  • HEMANPR's avatar
    HEMANPR
    Level 6
    15 years ago

    Hello Marianne

    I use the inactive destination option for the tape drive. We run the script and appear to stop all the newest duplication jobs set for duplicated using the LTO_Drive1.

    My new question is: When I use the active option to set my tape drive active again, all the pending duplication jobs set for use this LTO Drive will start or not?

     

    Im using this command:

    nbstlutil inactive -destination LTO_Drive1nbstlutil active -destination LTO_Drive1

  • Marianne's avatar
    Marianne
    Level 6
    15 years ago

    Correct.

    For more info, please have a look at this Best Practice Guide: http://www.symantec.com/docs/TECH75047

    You can verify with this command (as per extract from Best Practice Guide):

    For 6.5.4 and subsequent versions, use the nbstlutil command to display all unfinished copies:

    nbstlutil stlilist -image_incomplete -U

    The list is sorted by age. The image at the top of the list is the oldest, so the backup time of that image is the age of the backlog.
    ....
    SLPs process the oldest images first. Until the backlog is cleared up, your new backups will not be duplicated.