> I'm running disk-storage-unit backups (not the disk-staging 
> storage units) on a NB5.1MP3 Solaris 9 server.  I've
> configured my storage units for a 2000MB fragment size.
> 
> Occasionally, I run into backup images which exactly fill the 
> fragments exactly and bpimagelist shows a final zero-sized
> fragment which doesn't exist on the storage unit.  I haven't
> been able to duplicate these backups to tape.  I've tried
> touching a file having the same name as the final fragment,
> but without success.  I've ultimately had to expire the backup.
> 
> Does anybody have a workaround for this?  It seems like this 
> is a potential problem regardless of the storage unit's
> fragment-size configuration.

Sounds like the bug mentioned here a few postings ago:  

> > Also, what if the fragment size is 32GB and the backup is 
> > exactly 32GB? Are two fragments written or one?
> 
> Yes.  :-)  See technote 280018 for a pre-5.1MP5 or pre-6.0MP2 bug
> related to this.

So, check out http://seer.support.veritas.com/docs/280018.htm

NetBackup 6 has a default disk STU frag size of 0.5TB (see the SAG), so
a larger frag size, up to your OS's file-size limit, is also an option.