cancel
Showing results for 
Search instead for 
Did you mean: 

Too many incomplete SLP

andrich2016
Level 4

There is more than 1,000 SLP jobs incompletes, when I list them:

/usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -image_incomplete -l

Its a sample of the command:

/usr/openv/netbackup/bin/admincmd/nbstlutil stlilist -image_incomplete -l |more
V7.6.0 I XXXXXXXXXXXXXXXXXX_1645755458 MSDP-Tape30-Exadata 2
V7.6.0 C SL150 1 1
V7.6.0 I XXXXXXXXXXXXXXXXXX_1645767872 MSDP-Tape30-Exadata 2
V7.6.0 C SL150 1 1
V7.6.0 I XXXXXXXXXXXXXXXXXX_1645789323 MSDP-Tape30-Exadata 2
V7.6.0 C SL150 1 1

 

1 ACCEPTED SOLUTION

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

What is the status of field 11 of the SLP's (1=NOT_STARTED, 2=IN_PROCESS, 3=COMPLETE, 0=NOT_MANAGED)  ?

See : https://www.veritas.com/support/en_US/article.100011244

If you have a lot of status 1 "NOT_STARTED", you systems is likely loading more data to the MSDP  than can be stages to tape, meaning SLP jobs are piling up. Remember stage to tape is a full rehydration of data

Try to:

  • Optimize tape writing by adjusting NUMER_DATA_BUFFERS and SIZE_DATA_BUFFERS
  • Backup at night, run tape writing job during the day. Don't mix write and read jobs, performance will do down
  • Monitor SLP backlog as part of regular system monitoring.

View solution in original post

2 REPLIES 2

Nicolai
Moderator
Moderator
Partner    VIP   

What is the status of field 11 of the SLP's (1=NOT_STARTED, 2=IN_PROCESS, 3=COMPLETE, 0=NOT_MANAGED)  ?

See : https://www.veritas.com/support/en_US/article.100011244

If you have a lot of status 1 "NOT_STARTED", you systems is likely loading more data to the MSDP  than can be stages to tape, meaning SLP jobs are piling up. Remember stage to tape is a full rehydration of data

Try to:

  • Optimize tape writing by adjusting NUMER_DATA_BUFFERS and SIZE_DATA_BUFFERS
  • Backup at night, run tape writing job during the day. Don't mix write and read jobs, performance will do down
  • Monitor SLP backlog as part of regular system monitoring.

Thanks for reply.

I had this issue because one of our library was down and all the SLP that used this library was queued.

I canceled this SLP queue and now its running fine.