On 1/26/2011 5:27 PM, Dan Langille wrote: > On 1/26/2011 8:26 PM, Randy Katz wrote: >> On 1/26/2011 5:17 PM, Dan Langille wrote: >>> On 1/26/2011 8:14 PM, Randy Katz wrote: >>>> On 1/26/2011 5:07 PM, Dan Langille wrote: >>>>> On 1/26/2011 7:55 PM, Randy Katz wrote: >>>>>> Hi, >>>>>> >>>>>> I did a delete volume=volumenate and it warns me it will delete the >>>>>> volume and all associated jobs and I confirmed. >>>>>> I see it did indeed delete all jobs associated with the volume, >>>>>> however, >>>>>> it did not remove >>>>>> the actual volume from the disk. Is this normal behavior? Please >>>>>> comment, thanks. >>>>> >>>>> Yes. >>>>> >>>>> BTW, this is quite clearly the expected behaviour. The documentation: >>>>> >>>>> http://www.bacula.org/5.0.x-manuals/en/console/console/Bacula_Console.html#delete >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> delete [volume=vol-name pool=pool-name job jobid=id] >>>>> The delete command is used to delete a Volume, Pool or Job record >>>>> from >>>>> the Catalog as well as all associated catalog Volume records that >>>>> were >>>>> created. This command operates only on the Catalog database and >>>>> has no >>>>> effect on the actual data written to a Volume. >>>>> >>>>> >>>> Oh, sorry, yeah I remember seeing that before. So here is my issue: >>>> >>>> 1. There was a good volume with a Full Backup and then 2 or 3 >>>> incrementals after that. >>>> 2. The next incremental said it could not find a good Full Backup >>>> so it >>>> made another Full. >>> >>> Do you have this [error] message? >>> >>> NOTE: Perhaps you altered the FileSet.... this will generate a Full >>> backup. >>> >>>> 3. I checked the next Incremental and it did see the last Full Backup. >>> >>> message? >>> >>>> So I assume *something* happened to the Full Backup, not sure what >>>> that >>>> could be at this point but now I am >>>> using double the disk space (this is a disk backup) so I wanted to >>>> release that space as the space will remain used >>>> until Max Full Interval is reached. I read somewhere in the list >>>> archive >>>> that you must manually remove the volume >>>> on disk (assuming one Volume per Backup) if you want to free up the >>>> space. >>>> >>>> So I want to make sure that the Volume *should* get physically deleted >>>> when the Max Full Interval is reached, is >>>> that so? This assuming one volume per backup, AutoPrune and Recycle >>>> are >>>> yes. >>> >>> Bacula *never* deletes Volumes. >>> >> ok, I will assume I changed the File Set and that is why it made a Full >> Backup. >> Does Bacula recycle the disk space on expired volumes? Or do they just >> sit there? > > For recycling, the volume to be recycled is overwritten. > > Please read up on recycling. > got it, thanks for the hand holding and terminology brush up!
------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
