> 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
Hi Anton,
On Sat, Mar 24, 2012 at 11:35:38PM +0400, Anton Nikiforov wrote:
> I will try spooling, thanks for the suggestion, but i cannot understand
> why spooling will help with my problem. The storage is not tape or DVD.
> It is HDD, so there should no problems with or without spool.
> My proble
Hello Adrian and thanks for fast replay.
24.03.2012 20:30, Adrian Reyer пишет:
> On Sat, Mar 24, 2012 at 12:08:36PM +0400, Anton Nikiforov wrote:
>> (all 4 storages have different adresses and run on different machines)
>> Each client should be backed up on each storage. So i have jobs for that
>>
On Sat, Mar 24, 2012 at 12:08:36PM +0400, Anton Nikiforov wrote:
> (all 4 storages have different adresses and run on different machines)
> Each client should be backed up on each storage. So i have jobs for that
> like this:
May I ask why? Just for distributed backup Data?
> When i decrease numb
Dear ALL!
I'm new to this forum but using Bacula for years and happy with it.
But now i reach somekind of trouble in Bacula Configuration:
I have the following:
Director:
Director {
Name = dir
QueryFile = "/etc/bacula/scripts/query.sql"
WorkingDirectory = "/var/lib/bacul
