I can think of a few reasons why this might be happening.

1) Don't run bpexpdate commands in quick succession. My NBU servers can
only run one bpexpdate at a time and even after the command returns with
status zero, I still use a "sleep" command to wait 10 seconds before
running the next loop.  Running the same command without the "sleep"
command often causes erratic results.

2) Is this 5.1?  I've got several DSSUs in 5.1 that experience partial
deletes.  I.E. I'll clear the DSSUs once a quarter and I'll find 20 of
75 fragments of some old image still hanging out on the disk space even
though those fragments are no longer listed in the catalog.  Nothing I
can really do about this because my support contracts have expired on
these systems so I just deal with it.

3) Are you using the -copy 1 switch in the bpexpdate?  I'm not sure why,
but on my DSUs this seems to help.

What OS / version is this on?

-Jonathan



-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of A Darren
Dunham
Sent: Friday, July 17, 2009 11:36 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Removing DSU data files.

On Fri, Jul 17, 2009 at 10:03:08AM -0500, Ed Wilts wrote:
> > I've run some image cleanup jobs and none of them appeared to touch 
> > the files either.
> >
> > Am I doing something wrong?  How can I get the files to go away when

> > the image expires?
> 
> They do go away but the process is asynchronous.  Once you've done the

> bpexpdate, the image cleanup will get triggered.  Fire up the activity

> monitor and you can see the "Image Cleanup" jobs that run.

Yes, this was pretty much just a test.  Nothing ran overnight except a
hot catalog backup and some image cleanup jobs  I also tried firing one
off manually.

> Depending on how busy your master and media servers are, and how big 
> those images are, it can take a bit of time to do the cleanups but 
> they should happen.  You can manually trigger them, but if they're not

> happening automatically, you've got a bug somewhere.

I'd like to be able to force it to ensure it's gone at a particular
point in time.  I do see that an image cleanup runs immedately after my
bpexpdate.

> You can confirm that the image really has expired in the catalog with 
> a `bpimagelist -backupid <backupid> command and search for the FRAG
lines.

Right.  The entire image is gone from the catalog.

I just tried another two expirations.  One of the images was deleted
immedately.  The second is still present, even after runing cleanups
manually.  :-( I am most definitely not using '-nodelete' on the
expiration command line.

Now I'm confused.

--
Darren
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu