Hello Graham,

Unfortunately, it appears that the ActionOnPurge feature is *broken* and 
*dangerous*. The usage of this command should be avoided in any cases!

We will try to fix it for the next release, but the amount of work is very 
important.

I will update the manual in this way, and the current code for Branch-5.0 will 
disable this feature.

Thanks for your testing.

Bye

Le mardi 26 janvier 2010 12:25:44, Graham Keeling a écrit :
> Hello,
> 
> I tried to use the new 'Action On Purge = Truncate' option. I started with
> a fresh install and empty catalog and added the option to my Pools.
> I ran a small backup, and I followed the bconsole purge options. I ended up
> with this:
> 
> Enter *MediaId or Volume name: *1
> 1 File on Volume "backup-0001" purged from catalog.
> There are no more Jobs associated with Volume "backup-0001". Marking it
>  purged. Connecting to Storage daemon Disk 1 at 192.168.100.121:9103 ...
> 3916 Error scanning action_on_purge command
> New Pool is: Disk 1
> *q
> 
> Oh dear.
> 
> So, I had a quick look at the code passing the director command to the
>  storage daemon. I think the problem is to do with it not
>  'bashing/unbashing' the spaces in my storage device name.
> My storage device name is "Disk 1.1".
> 
> So, I have a patch that seemed to make it do the intended thing (attached),
> although there seem to more problems. Another report to come...
> 

------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to