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 processing is not yet complete (1573).
Doing this from commandline it says about the same (of course).

When trying to cancel its replication it gives also an error:
# nbstlutil cancel -backupid <Imagename>
Operation not successful: status = 220 (database system error)

According to Marianne in a previous issue 220 means 'no image found'.

The image is still active in a way:
# nbstlutil list -backupid <Imagename>
V7.6.0 I <Masterserverhostname> <Imagename> <Masterserverhostname> 1384237218 prd-cat-netbackup_catalog 7 0 zm_catalog_slp 3 false 1384242929 *NULL* 1  {00000000-0000-0000-0000-000000000000} 0 0 1384237225
V7.6.0 C <Masterserverhostname> <Imagename> 1 2147483647 1385360418 <stuname> 1 0 0 0 0 *NULL* 2147483647 0 2147483647 0 0 0 1 1
V7.6.0 F <Masterserverhostname> <Imagename> 1 1 0 @aaaa2 <Mediaserverhostname> *NULL* 0 6 1 3488240640 0 @aaaa2 *NULL* 1;DataDomain;<>DDhostname>;<diskpoolname>;<lsuname>;0

Now I am kind of stuck.

Tags (2)
1 Solution

Accepted Solutions
Accepted Solution!

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

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.

9 Replies

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

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 ?

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

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.

Highlighted

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

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.

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

Thanks Marianne and Nicolai, I'll make a call and see how Veritas will be solving this. Pierre.

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

Please let us know the outcome!

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

I had a case like yours before. Most likely Veritas will provide you with a custom SQL job that cleans the EMM inconsistency.

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

I will post the results when (if) Veritas has solved this issue.

Accepted Solution!

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

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.

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

Lowell Palacek provided the solution, thank you Lowell!

# bpexpdate -backupid <imagename> -d 0 -force_not_complete
Changing the expiration time of images that have not finished SLP processing can prevent completion of the SLP processing and lead to premature image expiration and potential data loss.
Are you SURE you want to proceed y/n (n)? y
Are you SURE you want to delete zmpbc003.rechtspraak.minjus.nl_1384237218 y/n (n)? y

Now the image has been removed. No commands can be issued against this image because it is gone:
# bpexpdate -backupid <imagename> -d 0 -force
no entity was found
# nbstlutil cancel -backupid <imagename> -force
option '-force' is no longer necessary and has been deprecated
No images or lifecycles matching criteria found.

We should have found this solution earlier because it is a documented feature of bpexpdate:
-force_not_complete
By default, an SLP-managed image or its copies cannot be expired if SLP processing is still in progress. The -force_not_complete option overrides this restriction and expires the image even if it is not SLP complete. Note that when you terminate further SLP processing of an image, other image copies may expire as well.

Thanks again Lowell.

 

Tags (2)