change a backupid retention

[issmag]

hi,

i can't change an expire date for a backup ID.

when i typed the command : bpexpdate -backupid backupid_11111111111 -d 12/12/2104, the command passed,

but when i check with bpimagelist -U -backupid backupid_11111111111 i find that the expire date does'nt change !!

i tried to duplicate this image to a tape and give it a time until december, but i can't, i got the error message :  it is a life cycle image that cannot be manually duplicate.

could you help me please ?

the Master server is Windows 2008 R2.

netbackup entreprise 7.5.0.5

this backup passed on a DataDomain.

thanks in advance !

[RamNagalla]

you can not manaully chage the expire date or duplicate the image for the images that are contorled by SLP, 

if you would like to do that you need to follow below

nbstlutil cancel -backupid <backupid>

then try changing the expire date and also duplicating..., but it will not carry any SLP retenctions or images... you have to take care it manually.

http://www.symantec.com/business/support/index?page=content&id=TECH170086

If you try to expire the image or the image copies manually that are not SLP-complete, the request fails with a 1573 error. To expire the image or images, you can do one of the following:

• Wait for the image or copy to become SLP-complete.
• Use the nbstlutil cancel command to terminate the SLP processing.
• Add the -force_not_complete option to the bpexpdate command to force the expiration even if the image or copy is not SLP-complete.

[Yasuhisa_Ishika]

Date you specified is beyond 2038. Try to set date before 2038.

[Nicolai]

My point also - infinity backup are 2038 in Netbackup 

Retention Periods with end dates beyond 2038, excluding Infinity on Windows

http://www.symantec.com/docs/HOWTO68516

Try doing :

bpexpdate -recalculate [-backupid backup_id] -d infinity

[issmag]

yes you're right, it was a mistake of keyboard typing, i typed 2014.

but now firned i have a serious problem, the image has an expire date in the past, so i can't no longer change the expire time and date, please need your help, i have to change the expire date.

when i typed  the command bpexpdate -recalculate i got the message : Failed to process an image whose expiration date is in the past.

please, i need your help before the backup clean up job pass and delete this image.

thanks in advance

[Yasuhisa_Ishika]

You can "import" expired backups if tapes have never been overwritten. Follow the steps described in this guide page 789.

http://www.symantec.com/docs/DOC5159

[issmag]

hello,

i did the importation but, the image has been deleted :(

i tried to increase the clean up time to prevent the cleanup to delete the images, but the job start many time, even i increased the time intervall...

[Marianne]

What is the date on your NBU master server?

12/12/2014 is NOT in the past. Or did you maybe make some more typo errors? 
Like 10/12/2014 perhaps?

There is no return from expiration of backup on disk. The expiration triggers nbdelete on media server that will also delete the data on disk. So, not possible to import.

Use extreme care with bpexpdate in future.
The command is followed by a confirmation message.
Read this message carefully before pressing 'y'.

[issmag]

hello marianne,

i just typed :

bpexpdate -recalculate -backupid backupid_11111111111

and i got the message, when i connfirmed it, i verified with bpimagelist, and i had the bad info, i saw that the date has been changed and the image has been expire (the date was with two days in the past).

the date on the master server was correct...

[Nicolai]

a bpexpdate -recalculate does not modify any dates according to my testing.

[Marianne · Accepted solution]

You should ALWAYS use bpexpdate -recalculate with a new retetion level or with a new expiration date.

In NetBackup 7.5, if 'bpexpdate -recalculate' is invoked from the command line without the '-d' or '-ret' option, incorrect expiration dates for images may be recalculated, which may lead to early expiration of those images.
http://www.symantec.com/docs/TECH188688 

[Nicolai]

Don't think this is the problem.  That issue is fixed in 7.5.0.3 - the user is at 7.5.0.5

But I think we can conclude that backup image is lost and that is why bpexpdate must be used with caution.

[Marianne]

We have seen in the past that installations are not always at the patch level that the user thought it was.
we have also seen in the past that bugs come back that was previously fixed.

Moral of the story to take a lesson from this experience:

Never use bpexpdate -recalculate without a new date or a new retention level...

Yes, use with CAUTION!