Forum Discussion

manmah's avatar
manmah
Level 2
3 months ago

Image Duplication Backlog

Hello everyone!

I've only recently started working with NetBackup and I've been dealing with it a few weeks now. Now, onto my question regarding duplication and its backlog.

Over the weekend, many duplications piled up due to errors or due to the closing of the time window, resulting in them going into an error state. However, these are executed as new jobs until the image is successfully duplicated, which fills up the queue.

Regardless of the cause, is there a command or, better yet, a way for me to check if the images causing the errors are present in this job so I can abort them?

Thank you in advance for your feedback!

Best regards,
M

Windows Server 2019

2 Replies

Sort By
  • manmah's avatar
    manmah
    Level 2
    5 days ago

    I unfortunately overlooked the notification for the reply to my post.
    Thanks for the input anyway!

    I have found a solution for my situation, that actually work well for me.
    When images fail, I simply cancel them with the following command "nbstlutil cancel -backupid %imagename%" and cancel all associated SLPs in the activity monitor.
    This restarts them and the non-faulty images are read in again.

  • Slartybardfast's avatar
    Slartybardfast
    Level 5
    3 months ago

    To view the backlog and get an idea which SLP has the the backlog you can use "nbstlutil report" from a command line. You have not mentioned whether you are on Linux or windows. For Linux the command is /etc/openv/nettbackup/bin. For windows it is located <INSTALL_DRIVE>\Program Files\Veritas\NetBackup\bin.

    You could use something like the following to find a list of incomplete images:

    "nbstlutillist -image_incomplete |findstr /C:"V7.6.0 C" >C:\temp\image_incomplete_Copy.txt" obviously this is a windows syntax command for Linux the grep command will need to used. My linux is rusty but something along the lines "nbstlutillist -image_incomplete |grep "V7.6.0 C" >/tmp/image_incomplete_Copy.txt"

    I am sure one of the gurus here on the forum will correct any silly mistake.