On Sat, 24 Mar 2012, James Harper wrote:

>> more than one client is available to backup the (shared) storage. If I change
>> the name of the client in the Job definition, a full backup always occurs the
>> next time a job is run. How do I avoid this?
>
> That's definitely going to confuse Bacula. As far as it is concerned you 
> are backing up a separate client with separate storage.

I still don't follow this. The client has changed, but everything else 
(pool, storage, catalog, etc) is the same. I don't see why a full backup 
is forced, or why bacula should be even slightly confused.

Steve

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users