s involved are running Debian 10 with Bacula 9.4.2. All
clients are on the same subnet.
Thanks,
Brendan Martin
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Several months ago, I got copy jobs set up and working. Sizes, counts,
and retention settings were all identical to the corresponding primary
pools when I started. After a while, I began seeing copy jobs waiting
for appendable volumes. I began manually marking the oldest volume per
pool for recy
I have recently gotten copy jobs configured and working. I am running
7.4.4 on Debian 9.
I find that my copy pools for some systems are requiring more volumes
than the corresponding primary pools. I initially suspected that this
was somehow tied to retention settings and the primary and copy bac
, Josh Fisher wrote:
>
> On 9/6/2018 1:17 PM, Brendan Martin wrote:
>> I have configured a copy job on my primary backup server. The copy
>> volumes will be on a secondary system running another storage
>> daemon. Both systems are running Bacula 7.4.4 on Debian 9.
>>
>
I have configured a copy job on my primary backup server. The copy
volumes will be on a secondary system running another storage daemon.
Both systems are running Bacula 7.4.4 on Debian 9.
From the primary console, this command:
status storage=Remote-File
successfully returns version, daemo
Thanks; I suspected that would eventually be the case.
On 10/22/2015 8:24 PM, Heitor Faria wrote:
>> I am running Bacula 5.2.6 on Debian 8.1. My backups are disk-based.
>>
>> I have a local primary backup server and a remote secondary backup
>> server. The secondary is intended to contain copies
want to do, or defining (non-copy)
jobs to backup the primary to the secondary, which I would prefer not to
do, I'm not sure how best to accomplish remote backup copies.
Is anyone doing this in an environment with a similar configuration?
Thanks,
Brendan M
le
}
I do understand that Copy jobs work differently, but I am not
understanding all the details of how to adjust things for them. Also,
just to confirm, the Level for all Copy jobs should be Full, correct?
Thanks,
Brendan Martin
---
ted, since after the start time, a few minutes later,
bacula tries the mount operation and then starts counting the Max Wait
Time.
I don't know why the log shows start time equal to end time for these
jobs, maybe this is a bug in this version.
Best regards,
Ana
On Wed, Jul 8, 2015 a
rs:1
SD Errors: 0
FD termination status:
SD termination status:
Termination:Backup Canceled
On 7/8/2015 2:16 PM, Ana Emília M. Arruda wrote:
Hello Brendan,
On Wed, Jul 8, 2015 at 12:27 PM, Brendan Martin
mailto:bren...@physics.tamu.edu>> wrote:
I have a B
I have a Bacula Director 5.2.6 running on Debian 8.1.
To avoid an excessive delay in the backup schedule in the event of
insufficient volumes, I added a Max Wait Time value of 600 (seconds) in
the JobDefs for a couple of clients. Jobs for those clients
subsequently were cancelled immediately u
11 matches
Mail list logo
