Forum Discussion

Wolaf25's avatar
Wolaf25
Level 4
10 years ago

Duplicate to tape continuos runing without SLP, SLP was removed

Hi

I removed one SLP used for duplicate images from DataDomain to physical tapes.

But the duplications job remain executing without any logic.

I stopped and started NBU,  without unsuccessfully.

I reboot the server and the same result, duplications job still remain running.

As appears one process is in loop in EMM, I guess.

How can I stop this loop?

Master server is a linux 2.6.32-358.32.3.el6.x86_64, NBU is 7.5.

Thanks

7.5
Backup and Recovery
Linux
NetBackup
  • RonCaplinger's avatar
    RonCaplinger
    10 years ago

    To list all of the waiting duplications to the tape drives from this SLP, enter:

    nbstlutil stlilist -lifecycle ddnicpe0100_prod_full -destination nims0102man-hcart2-robot-tld-0 -image_incomplete

    This will list all of the images that are still trying to write to tape from that lifecycle.  If you want to cancel all of them, you can try entering this command:

    nbstlutil -cancel -lifecycle ddnicpe0100_prod_full -destination nims0102man-hcart2-robot-tld-0 -force

    Then enter the first command above to make sure they are all properly cancelled, and not just waiting for their next increment of time to run.

  • mph999's avatar
    mph999
    Level 6
    10 years ago
    nbstlutil stlilist will show the state, 1 or 2 is not complete, 3 is. nbstlutil cancel -backupid will stop further dupications for the given backupid
  • Wolaf25's avatar
    Wolaf25
    Level 4
    10 years ago

    Hi

     That command stop a specific job, but how can I to stop all the duplication daemons?

     

  • Wolaf25's avatar
    Wolaf25
    Level 4
    10 years ago

    $ ./nbstlutil stlilist | grep tld-0
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
    V7.5.0 C nims0102man-hcart2-robot-tld-0 1 1
     

    Is this normal ?

     

  • mph999's avatar
    mph999
    Level 6
    10 years ago
    You can deactive a specific SLP nbstlutil active | inactive [-wait | -force] [[-lifecycle name [-destination name] | -backupid value] So nbstlutil inactive -lifecycle [SLP name] should work
  • Wolaf25's avatar
    Wolaf25
    Level 4
    10 years ago

    But the problem is that I dont want to desactivate the SLP completely, the SLP have 3 steps.

    first step is backup to the PROD Data Domain

    second step is duplicate to DR Data Domain

    and the 3er step is duplications from DR Data Domain to physical tapes, this step was removed, but is running and running again, but ... in the "SLP" does not appears this step ...

    SLP name is : ddnicpe0100_prod_full       and this 2 steps are into this SLP

    Backup ddnicpe0100_prod_su -- -- Fixed 6 months -- No No
    Duplication ddnicle0200_dr_su -- -- Fixed 3 months -- No No

    the 3er steps was removed and was for duplicaction from DDnicle0200_dr_su to

    nims0102man-hcart2-robot-tld-0 into physical tapes.

     This step was removed and run again and again without any logic.

    Any idea what is happen?

    Clear cache did not work.

    Thanks

     

     

     

     

  • mph999's avatar
    mph999
    Level 6
    10 years ago
    From the output, the 1 at the end show that these images are 'not started' - it can be normal, but after some time the images should progress to '2' (in process) and then finally '3' (complete). Use the -U option on the command and it replaces the number with words, so a bit easier to follow. So, when you say the step was removed, this was from the SLP config ? Then the step was put back. What do you mean by 'it was run again and again without any logic' Do you mean the duplication runs to tape, then it runs again and so on, do any of these complete successfully. Basically, once the SLP is submitted, you can't stop it - you can only cancel that image and remove from SLP control. For just one image that has the problem, what does nbstultil stlilist -U show
  • RonCaplinger's avatar
    RonCaplinger
    Level 6
    10 years ago

    It sounds like you made a change to an existing Storage Lifecycle Policy, you did not delete it. 

    Changing the SLP steps in the SLP configuration has no effect on any already-running backups that specify that SLP, nor does it prevent any remaining duplications that were defined, before the change was made.

    If these duplications really are running because the backups started before your SLP change, and you don't want the images to duplicate to tape, you must run the "nbstlutil cancel -backupid xxxxxxx" to cancel the remaining duplication to tape.

     

  • Wolaf25's avatar
    Wolaf25
    Level 4
    10 years ago

    Yes, not express myself properly, is my fault, the SLP was changed, no deleted, I just remove the duplication to the tape, and this duplications run and run again.
     

    Backup ddnicpe0100_prod_su -- -- Fixed 6 months -- No No
    Duplication ddnicle0200_dr_su -- -- Fixed 3 months -- No No

    This the status actual from the SLP, existed a third  step, I removed it, but the duplication still remain.

    How Can I list the remaining duplication to tape?

    Thanks to both.

     

     

     

  • RonCaplinger's avatar
    RonCaplinger
    Level 6
    10 years ago

    To list all of the waiting duplications to the tape drives from this SLP, enter:

    nbstlutil stlilist -lifecycle ddnicpe0100_prod_full -destination nims0102man-hcart2-robot-tld-0 -image_incomplete

    This will list all of the images that are still trying to write to tape from that lifecycle.  If you want to cancel all of them, you can try entering this command:

    nbstlutil -cancel -lifecycle ddnicpe0100_prod_full -destination nims0102man-hcart2-robot-tld-0 -force

    Then enter the first command above to make sure they are all properly cancelled, and not just waiting for their next increment of time to run.

  • Wolaf25's avatar
    Wolaf25
    Level 4
    10 years ago

    Thanks RonCaplinger and mph999 for your help.

    As I read, I saw  that is recomended to desactive SLP before to change.

    Regards