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.
2012/3/24 Steve Thompson
> 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?
>
Avoid changing a client's name. You can change IP resolution o
Am Sat, 24 Mar 2012 16:52:32 -0400 schrieb Steve Thompson:
> Bacula 5.0.2. For the following example job:
>
...
> }
>
> 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
> Bacula 5.0.2. For the following example job:
>
>
>
> 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 confu
Bacula 5.0.2. For the following example job:
Job {
Name = "cbe_home_a"
JobDefs = "defjob"
Pool = Pool_cbe_home_a
Write Bootstrap = "/var/lib/bacula/cbe_home_a.bsr"
Client = clarke-fd
FileSet = "cbe_home_a"
Schedule = "Saturday3"
}
FileSet {
Name = "cbe_home_a"
In
