On Mon, 18 May 2009 17:05:05 +0200, Frank Altpeter  
<frank.altpeter AT gmail DOT com> wrote:

> Any pointer on how to really completely remove a client would be very
> appreciated ...

See the purge and delete console commands in the manual. I've used them  
like this:

- purge volumes first (this purges filenames etc., unlike 'prune'  
regardless of retention times)
- delete volumes (from bconsole, not physically yet)
- delete the pool they belong to if no other volumes use the same pool (if  
you have separate pools for every client for example)
- reload Bacula director config in which  
client/device/fileset/job/pool/schedule/storage stanzas relating to the  
client are deleted. This needs to be done right away, e.g. 'status dir' in  
the meantime may readd the pool you just deleted because it's still in the  
config.
- edit bacula-sd.conf to remove the client, bacula-ctl-sd restart
- use dbcheck to get rid of the last remnants (dangling paths and the like)
- physically delete volume files or tape


------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users