On 02/19/2018 08:57 AM, Mike Eggleston wrote:
> Sorry it took me a while to get this answer... life is...
[...snip...]
> Running Jobs:
> Console connected at 19-Feb-18 09:05
> JobId Type Level Files Bytes Name Status
> ===
:50 AM
> To: Mike Eggleston ;
> bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Testing VirtualFull; job created but not running;
> why?
>
> On 02/19/2018 08:57 AM, Mike Eggleston wrote:
> > Sorry it took me a while to get this answer... life is
w, but I'm confused about this. I have autochangers commented
out.
Thanks,
Mike
-Original Message-
From: Bill Arlofski [mailto:waa-bac...@revpol.com]
Sent: Monday, February 19, 2018 10:50 AM
To: Mike Eggleston ;
bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Testi
On 02/19/2018 10:18 AM, Mike Eggleston wrote:
> Hi Bill,
>
> In the pools definition I have "#Maximum Volume Jobs = 1" and in
> bacula-sd.conf I have "Maximum Concurrent Jobs = 20". I also have "Maximum
> Concurrent Jobs = 20" in bacula-dir.conf. What else do I need to check? I
> know you prese
Here an example of my conf. one pool for one client.
If that can help you.
Job {
../..
Name = "client1"
Accurate = yes
../..
}
Pool {
Name = client1
Pool Type = Backup
Recycle = yes # Bacula can automatically
recycle Volumes
AutoPrune = yes
On 02/15/2018 01:06 PM, Mike Eggleston wrote:
> I have my test setup of Bacula. I have two servers configured.
>
> Now I’m trying to test VirtualFull of one of those servers (that has Full,
> Incremental, etc.).
>
> I modified the director configuration file and created another Pool for the
> Vir
I have my test setup of Bacula. I have two servers configured.
Now I'm trying to test VirtualFull of one of those servers (that has Full,
Incremental, etc.).
I modified the director configuration file and created another Pool for the
VirtualFull.
The second Pool is listed as NextPool for my prima
