Netbackup Snapshot Manager After cancellation of Backup from Snapshot job the retry of Backup From Snapshot job does not arrive

Problem

After Backup From Snapshot job cancelation from WebUI, in some cases, a retry for the corresponding BFS job does not arrive/come.

Error Message

Month xx, 2025 4:31:00 PM - Info nbjm (pid=xxxxx) starting backup job (jobid=xx) for client CLIENT_NAME, policy 
BACKUPNOW+45f4a0a7-ece0-45b2-8607-9dc6b53babe4, schedule FULL_fdfcd96e-83e6-4c69-a785-e3cbadf783bf
Month xx, 2025 4:31:00 PM - granted resource datamover.0790f3720b674088bcd23cb8bec57820
Month xx, 2025 4:31:00 PM - estimated 0 kbytes needed
Month xx, 2025 4:31:00 PM - Info nbjm (pid=xxxxx) started backup (backupid=BACKUP_ID) job for client 
CLIENT_NAME, policy BACKUPNOW+45f4a0a7-ece0-45b2-8607-9dc6b53babe4, schedule FULL_fdfcd96e-83e6-4c69-a785-e3cbadf783bf on 
storage unit primary
Month xx, 2025 4:31:00 PM - started process bpbrm (pid=xxxxxx)
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) Reverse connection detected for host blackrock-nbsm
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) The data-in-transit encryption (DTE) is enabled for the client (blackrock-nbsm) as the global DTE mode is set 
to 'Preferred On' and the client DTE mode is set to 'Automatic'
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) Encrypting data-in-transit
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) CLIENT_NAME is the host to backup data from
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) reading file list for client
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) accelerator enabled
Month xx, 2025 4:31:02 PM - Info bpbrm (pid=xxxxxx) There is no complete backup image match with track journal, a regular full backup will be performed.
Month xx, 2025 4:31:02 PM - connecting
Month xx, 2025 4:31:03 PM - Info bpbrm (pid=xxxxxx) starting bpbkar on client
Month xx, 2025 4:31:03 PM - Info bpbkar (pid=2135) Backup started
Month xx, 2025 4:31:03 PM - Info bpbrm (pid=xxxxxx) bptm pid: 100090
Month xx, 2025 4:31:03 PM - Info bptm (pid=100090) start
Month xx, 2025 4:31:03 PM - Info bptm (pid=100090) Encrypting data-in-transit
Month xx, 2025 4:31:03 PM - Info bptm (pid=100090) using 262144 data buffer size
Month xx, 2025 4:31:03 PM - Info bptm (pid=100090) using 30 data buffers
Month xx, 2025 4:31:03 PM - connected; connect time: 0:00:00
Month xx, 2025 4:31:04 PM - Info bpbkar (pid=xxxx) INF - Backing up Hypervisor Type Azure, VM Server xxxxx-nbsm, VM GUID  
CLIENT_NAME, Display Name xxxxxxx
Month xx, 2025 4:31:04 PM - Info bptm (pid=100090) start backup
Month xx, 2025 4:31:05 PM - Info bptm (pid=100090) backup child process is pid 100123
Month xx, 2025 4:31:05 PM - begin writing
Month xx, 2025 4:31:09 PM - Info bpbkar (pid=2135) 38 entries sent to bpdbm
Month xx, 2025 4:31:09 PM - Info bpbkar (pid=2135) 39 entries sent to bpdbm
Month xx, 2025 4:31:10 PM - Info bpbkar (pid=2135) 40 entries sent to bpdbm
Month xx, 2025 4:31:21 PM - Info bpbkar (pid=2135) accelerator sent 50688 bytes out of 13168349696 bytes to server, optimization 100.0%
Month xx, 2025 4:31:21 PM - Info bptm (pid=100090) waited for full buffer 1 times, delayed 1055 times
Month xx, 2025 4:31:22 PM - Info bptm (pid=100090) EXITING with status 0 <----------
Month xx, 2025 4:31:22 PM - Info blackrock-nbu (pid=100090) StorageServer=PureDisk:blackrock-nbu; Report=PDDO Stats (multi-threaded stream used) for 
(blackrock-nbu:PureDiskVolume): scanned: 12859765 KB, CR sent: 7573 KB, CR sent over FC: 0 KB, dedup: 99.9%, cache disabled, where dedup space saving:99.9%, 
compression space saving:0.0%, new transferred data encrypted
Month xx, 2025 4:31:22 PM - Info bpbrm (pid=xxxxxx) validating image for client CLIENT_NAME
Month xx, 2025 4:31:26 PM - Info bpbrm (pid=xxxxxx) Cleanup datamover request started.
Month xx, 2025 4:31:46 PM - Info bpbrm (pid=xxxxxx) Cleanup datamover request completed.
Month xx, 2025 4:31:46 PM - Info bpbkar (pid=xxxx) done. status: 0: the requested operation was successfully completed
Month xx, 2025 4:31:46 PM - Error nbpem (pid=xxxx) duplicate exited with status 150 (termination requested by administrator)
Month xx, 2025 4:31:46 PM - end writing; write time: 0:00:41
Month xx, 2025 4:31:46 PM - Info nbjm (pid=xxxxx) Successfully updated preferred configuration ID for Asset: CLIENT_NAME
Month xx, 2025 4:31:46 PM - Info nbjm (pid=xxxxx) Successfully updated last backup status for Asset: CLIENT_NAME
termination requested by administrator(150)

Cause

In some scenarios, by the time the cancel request gets processed, there is a possibility that the image for a particular backup id is already validated and completed. Hence, there will not be any retry jobs.

we can see a validation in the above job details "validating image for client CLIENT_NAME" without any errors which indicates that the processing for this backup id is completed.

Solution

To confirm the backup id status whether it is completed or not we can use nbstlutil command.

/usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -backupid <backup_id>

Also, users can also check the recovery point for a corresponding backup from WebUI.