This is a bit older, but I wanted to post the resolution for it in case somebody else finds this post through Google.
It turned out that the culprit was the FirstWritten attribute. To fix it, simply update FirstWritten to some value other than 0000-00-00 (but in the distant past): UPDATE Media SET FirstWritten='2008-01-01' WHERE FirstWritten = '0000-00-00'; > -----Original Message----- > From: Kevin Keane [mailto:subscript...@kkeane.com] > Sent: Tuesday, December 15, 2009 2:58 PM > Cc: bacula-users@lists.sourceforge.net > Subject: Re: [Bacula-users] prune not working as expected > > > -----Original Message----- > > > I also checked: there are no jobs associated with these volumes. > > > > Yes, prune should mark those volumes are purged if there are no jobs. > > It's a mystery. > > Is there a way to turn on something like verbose output for pruning so > I can find out exactly what it does to troubleshoot that? > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
