Duplication: nbstlutil report numbers

Question

Hello,I would like to ask you or better clarify command "nbstlutil report". What exactly is considered in the number of copies? Only "images to be duplicated" or&nbsp; "images to be duplicated together with images that are already duplicated and waiting e.g. for expiration"?From nbstlutil report -lifecycle xxxx I got following:Backlog of incomplete SLP CopiesIn Process (Storage Lifecycle State: 2):Number of copies: 4028Total expected size 22996802 MBSLP Name: (state)Number of copies:&nbsp;4028&nbsp;Size:&nbsp;22996802&nbsp;&nbsp;MBBecasue when I want to cancel whole processing via "nbstlutil cancel -lifecycle xxxx" I got only 1876 images instead of total 4028 images, that's why I'm wondering what's included in the "total number".Thank you for any clarification.Tom&nbsp;

nicolai · Answer

If you have modified the SLP during it's lifecycle, you need also to specify the SLP version number to cancel/report

https://www.veritas.com/support/en_US/doc/123533878-127136857-0/v123553953-127136857

nbstlutil cancel [-lifecycle name | -destination name] [-version number] [-before mm/dd/yyyy hh:mm:ss | -after mm/dd/yyyy hh:mm:ss] [-nowarn]

tomas_pospichal · Answer

Nicolai&nbsp;So far what I've checked, there is only one SLP version and that's version 2 (checked 0, 1, 3 = nothing there)&nbsp;with that total number&nbsp;1876&nbsp;to be cancelled but it does not match with the total number from the report (4028), I also used the version parameter with that command.

sanket_pathak1 · Answer

Tomas_Pospichal&nbsp;How many secondary operations you have in this SLP ?Primary operation being Backup... how many duplication/replication jobs you have added to the SLP ?

tomas_pospichal · Answer

sanket_pathak1Hello,there are two operations in that SLP - one for Backup which is primary operation, one for Duplication which is secondary operation. That's all.

sanket_pathak1 · Answer

looks like.. some stale entries are added to the count. Not sure if this is the right step but you can try. Note this will need some extensive logging to enable and further analysis. You can try working with Tech Support to get the right analysis from the logs1. Enable nbstserv log -- vxlogcfg -a -p NB -o nbstserv -s DebugLevel=62. Enable bpdbm log -- create BPDBM_VERBOSE = 5 entry into bp.conf. make sure to have bpdbm log directory created. Delete older logs if possible.3. Enable nbemm log -- vxlogcfg -a -p NB -o nbemm -s Debug Level=64. Now try to cancel the SLP, but dont do it really. I am hoping intiating cancel operation would log images list in bpdbm and nbstserv log.5. Collect the logs for review and share it with Tech Support.6. Disable the loggingvxlogcfg -a -p NB -o nbstserv -s DebugLevel=0vxlogcfg -a -p NB -o nbemm -s DebugLevel=0remove the BPDBM_VERBOSE = 5 entry from bp.conf7. Now that you are working with Tech Support, it is also worth to capture NBSU and nbdb dump.

Forum Discussion

Duplication: nbstlutil report numbers

5 Replies

Related Content

Missing nbstlutil

nbstlutil command

Understanding NBSTLUTIL command results

Duplicate cluster ID numbers

How To Cancel SLP 1000 Images nbstlutil cancel using script in windows