SLP jobs are not getting activated, images are not processed successfully; duplications of some images from certain policies are not processed, others are successful.

  • Article ID:100027618
  • Modified Date:
  • Product(s):


Some images managed by a storage lifecycle policy (SLP) were not being submitted to nbpem successfully.  These images were added to a batch, but the duplication could not be started correctly due to a problem submitting the job request to nbpem.  Images from a particular SLP were not moving forward to duplication and left on the disk based storage. This condition risks filling up the disk storage, or making less storage available for future jobs.

Error Message

# /usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -U -lifecycle SLP_number_two
Copy to destination_storage is NOT_STARTED
 on both "IN_PROCESS" and "NOT STARTED" images

nbstserv logs show the following relevant messages:
08/29/2012 11:13:12.495 [Debug] NB 51216 nbstserv 226 PID:4397 TID:7 File ID:226 [No context] 4 [RS::submitToPEM] found co-mingled SLP's, <SLP_number_one> != <SLP_number_two> (ReplicationSession.cpp:1096)
08/29/2012 11:13:13.469 [Debug] NB 51216 nbstserv 226 PID:4397 TID:7 File ID:226 [No context] 4 [RS::submitToPEM] submitting job to PEM... (ReplicationSession.cpp:1273)
08/29/2012 11:13:13.472 [Debug] NB 51216 nbstserv 226 PID:4397 TID:7 File ID:226 [No context] 1 [RS::submitToPEM] error submitting job to PEM, err = -230 ,skipping...(ReplicationSession.cpp:1319)


The default configuration of SLP is to allow multiple SLPs with the same priority to to be batched together in one duplication job. The nbstserv log shows the following parameter set:


The message in the nbstserv log referencing "co-mingled SLPs" indicates that images from different SLPs but with the same priority were being grouped together in a single batch. This can affect the batching of some duplication jobs, and cause some images to not submit to nbpem along the way.

The /usr/openv/netbackup/db/config/LIFECYCLE_PARAMETERS file can allow this default behavior to change and set the images to be batched based on the SLP only, not mixing multiple SLPs with the same priority.



Setting the DUPLICATION_GROUP_CRITERIA parameter to 0 in the  /usr/openv/netbackup/db/config/LIFECYCLE_PARAMETERS file allows the batches to be created based on the SLP only.  Images from other SLPs will not be considered for a particular batch.  This allowed the images that remained backlogged to move forward. Once duplicated the disk storage is freed up for new images.


Was this content helpful?

Get Support