-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

sorry, must have reached my multitasking limit without fresh coffee...

Peter DrakeUnderkoffler
Xinupro, LLC
617-834-2352



Joe Royer wrote:
> Thanks for trying to help, but did you read my message at all?
> 
> NetBackup 5.1 MP5
> was the first line of the message.  I also said I tried to manually
> bpduplicate the image _specifying_the_name_of_the_image_.
> 
> When bpduplicate couldn't find it by name, I decided to search the
> restore catalog and sure enough it wasn't there.  I hate to delete 90%
> of the incremental for that day, but I guess NBU had failed me anyway at
> that point.
> 
> Things are moving again after deleting the fragments, but I'm definitely
> calling this a bug.  I have 1.7TB of DSSU in my production environment
> (MP4) and haven't seen this problem (where it's far more likely to happen).
> 
> Thanks
> 
> 
> On Wed, 29 Nov 2006, Peter DrakeUnderkoffler wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Not sure which version and MP you are running  so that info might help
>> someone help you.  If the file is left on the dssu file system, the
>> backup
>> image is held within the name of the file  It will be the first part
>> of the file name up to "_C1".  The form of the file is this:
>>
>> CLIENT_STARTTIMESINCEEPOCC_F#.STARTTIMESINCEEPOC.img
>>
>> where CLIENT is the client name as configured within your policies
>> where STARTTIMESINCEEPOC is a number of seconds since the epoc
>> where C# is copy number
>> where F# is fragment number.
>>
>> For instance, if the file name is:
>>
>> vader_1164805206_C1_F1.1164805206.img
>>
>> the backup image name is:
>>
>> vader_1164805206
>>
>> You should be able to search the catalogs for that image name as such:
>>
>> bpimagelist -backupid  vader_1164805206
>>
>> If there is nothing there, you can remove the file.  Don't ever remove
>> a file from the DSSU if the image still lives in the catalogs.
>>
>> At least this might help you clean up your storage temporarily.  As to
>> the source of the problem, I'd love to know if that is a bug.
>>
>> Thanks
>> Peter
>>
>> Peter DrakeUnderkoffler
>> Xinupro, LLC
>> 617-834-2352
>>
>>
>>
>> Joe Royer wrote:
>>
>>> NetBackup 5.1 MP5
>>>
>>> I have noticed twice now, that if a large job is writing to a DSSU and
>>> it fails or is killed, it doesn't get destaged, ever.  This can fill
>>> up the DSSU.  I am also not able to locate the image, even by name
>>> with the bpduplicate command so I can't manually destage it.
>>>
>>> Help?  I don't particularly want to delete it from the DSSU.
>>>
>>
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFbbcAl+lekZRM55oRAu72AJoDzVNevrdTg5PoPd1jdo6Q1Hp+uACg341x
zwSY0+EOEbVzlnKvJJZjXX8=
=Viti
-----END PGP SIGNATURE-----