slp operation

You can cancel secondary slp operation. Since secondary slp has been inactive for such a long time, I would recommend canceling all incomplete slp operation before activating the secondary slp operation, and then monitor operation from there. You will need to write a a shell script to cancel incomplete slp operations.

This is a previous thread about canceling slp operation - see Mark reply 12-08-2011 09:31 AM

https://vox.veritas.com/t5/NetBackup/Cancel-Duplication-jobs/m-p/443050

Tech note for nbstlutil command used to cancel slp operation

http://www.veritas.com/docs/000093204

Be aware that if you cancel an image from SLP, and it has gone past it's expire (try-to-keep) time, it will instantly expire.  Also, if the images are set as 'Expire after copy' they will also expire if you cancel them.

Not an issue if you want to get rid of the images, but a big issue if you wanted to keep them and then duplicate them manually.

You can list out jobs within SLP, and inactivate individual jobs.

I use this to prevent them from processing when I am micromanaging my SLP duplications.

You can then activate the jobs you want.

Since incomplete SLP jobs are essentially kept as infinite retention, you should potentially have tons of images that are incomplete and should be expired...

If you KNOW the retention is past, you can simply cancel the oldest jobs.

1. list the jobs - format is client_epoch

nbstlutil stlilist -image_incomplete -U | grep Image | cut -f 2 -d "

2. inactive the job 

for each of the images from #1, nbstlutil inactive -backupid $id

3. cancel the old jobs

for each of the images from #1 that are too old, nbstlutil cancel -backupid $id