I second Alex' request, and it also seems to me that Alex' version is 
quite an expansion of what item 6 of the project file requests.

Item 6 just requests that there should be a way to delete a file system 
file for pruned/purged volumes. The way I read it, the record in the 
catalog would not be touched, and the volume would still be recycled. 
Eventually, a file with the same name would be recreated. Item 6 is 
primarily targeted at reducing the disk space usage. It also probably 
wouldn't accomplish all that much because as far as I understand it, 
bacula only prunes a volume immediately before reusing it.

Alex seems to be requesting (and I definitely am requesting) that after 
the retention period, the volume be removed from recycling altogether, 
never to be reused in any way. This means a change in the pruning logic 
as well as a feature similar to item 6, "delete file on prune".

I consider Alex' request a very important feature; it would fix a major 
misfeature in bacula. Currently, you can use the job name and date when 
autolabeling a new volume, but as soon as that volume is recycled, a 
different job ends up in the same file, causing endless confusion.

Another note: this "delete on prune" feature must be able to handle 
files on disks that are currently not mounted, such as a USB drive that 
has been taken off site.

Eric Bollengier wrote:
> Hello,
>
> What is the difference with item 6 of the current project file ?
>
> Bye
>
> Le Monday 16 February 2009 11:02:34 Alex F, vous avez écrit :
>   
>> Item 1. Delete volume on purge.
>> Origin: Alex F, alexxzell at yahoo dot com
>> Date: 16 February 2009
>>
>> What: A feature that would permit Bacula to delete a volume from the hard
>> disk after it has been purged.
>>
>> Why: Useful for users backing up to hard disks. I for instance, am doing
>> this, and have to manually list volumes, seek and delete them, and
>> afterwards delete them from the mysql database. Woulld be acceptable if I
>> had to do it for 1 client...but I have many servers being backed up so this
>> is time-consuming. Maybe a new status could be defined when listing jobs,
>> something like "Deleted". I know Bacula treats backups like if it were tape
>> jobs, but I believe that this approach is a little outdated, and some help
>> should be pointed towards the users who use Servers for the purpose of
>> backing up.
>>
>> Thank you.
>>     


-- 
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About

Office: 866-642-7116
http://www.4nettech.com

This e-mail and attachments, if any, may contain confidential and/or 
proprietary information. Please be advised that the unauthorized use or 
disclosure of the information is strictly prohibited. The information herein is 
intended only for use by the intended recipient(s) named above. If you have 
received this transmission in error, please notify the sender immediately and 
permanently delete the e-mail and any copies, printouts or attachments thereof.


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users