Forum Discussion

Pierre_J's avatar
Pierre_J
Level 4
6 years ago

Backup image expiration cannot be modified because its SLP processing is not yet complete

Hi there, We found a really old catalog backup in the Catalog which should long be expired. When trying to expire it in the GUI it says Backup image expiration cannot be modified because its SLP pr...
8
windows server 2012
  • Lowell_Palecek's avatar
    Lowell_Palecek
    6 years ago

    We do root cause when a need for a SQL script comes up. Sometimes we're able to change the product so that either the situation won't arise, or NetBackup will be able to handle it.

    With that in mind, I started searching our recent escalations for such a situation as yours. I found one that seems to match. (ET 3940173, Operation not successful: status = 220 (database system error))

    Rather than a SQL script, this one gave a command option that worked for the customer. Try this:

    >bpexpdate -backupid xxxxxxxxxxx -d 0 -force_not_complete

    The report says that -force_not_complete allows expiration of incomplete SLP images.

    BTW, status 220 doesn't always mean something not found - that's status 227. Often when a browse or bplist fails, NetBackup changes the 227 to 220.

Nicolai's avatar
Nicolai
Moderator
6 years ago

Try running nbstlutil with the -force option:

nbstlutil cancel -backupid <Imagename> -force

Else contact support. Do you have SLP job in the activity console that ends with status code 1 ?

  • Pierre_J's avatar
    Pierre_J
    Level 4
    6 years ago

    Hi Nicolai,

    Thanks for the thinking.

    # nbstlutil cancel -backupid <imagename> -force
    option '-force' is no longer necessary and has been deprecated
    Operation not successful: status = 220 (database system error)

    We had some staus 1 in replication jobs because of a Data Domain file system issue, but that is with recent images.
    The images which are stuck are from years ago, I can't figure out if there were any errors in those days.

    • Marianne's avatar
      Marianne
      Level 6
      6 years ago

      You will need to log a call with Veritas Support.

      They will need a database dump and then supply sql scripts to remove orphaned SLP entries.

      • Pierre_J's avatar
        Pierre_J
        Level 4
        6 years ago
        Thanks Marianne and Nicolai, I'll make a call and see how Veritas will be solving this. Pierre.
  • jdelarosa's avatar
    jdelarosa
    Level 3
    3 years ago

    Hi can I ask what is the impact to the SLP if a backup ends up with status 1, and that image is supposed to be duplicated? Thanks

    • davidmoline's avatar
      davidmoline
      Level 6
      3 years ago

      Hi jdelarosa 

      You should really start a new post rather than tacking onto an old (and solved) solution. Maybe a moderator can move this. 

      There is no impact to the SLP, it will perform the next step in the operation with the backup image that was saved during the first backup operation. Remember usually a status 1 implies one or more files could not be read cleanly during the backup impacting (potentially) thos files, but the rest of th ebackup is fine. The SLP will continue operations on what was backed up.

      Cheers
      David

      • jdelarosa's avatar
        jdelarosa
        Level 3
        3 years ago

        Thank you! we are experiencing a somewhat related issue so I was browsing through some discussions. But I will create a new post like you mentioned. Thanks!