Try changing (or adding if you don't have it already) the heartbeat interval
variable. I have about 160TB I'm currently backing up total & some of the boxes
are 8-29TB jobs. Heartbeat is must, for large jobs, as far as I'm concerned.
- Steve
Sent from my iPhone
On Jul 14, 2012, at 8:19 PM, "St
On Sat, 14 Jul 2012, Joseph Spenner wrote:
> That's insane! :)
Heh :)
> Ok, can you maybe carve it up a little? How big is the backup?
I have already carved it up just about as much as I can. I have to back up
about 6 TB in 28 million files (that change very slowly) to a remote
offsite SD.
On Jul 14, 2012, at 5:38 PM, Steve Thompson wrote:
> Bacula 5.0.2, CentOS 5.8.
>
> I have this in my job definitions:
>
>Full Max Run Time = 29d
>
> but still they are terminated after 6 days:
>
> 14-Jul 20:27 cbe-dir JobId 39969: Fatal error: Network error with FD
>during Backup: ER
Bacula 5.0.2, CentOS 5.8.
I have this in my job definitions:
Full Max Run Time = 29d
but still they are terminated after 6 days:
14-Jul 20:27 cbe-dir JobId 39969: Fatal error: Network error with FD
during Backup: ERR=Interrupted system call
14-Jul 20:27 cbe-dir JobId 39969: Fata
Are wildcards in the -e file for exclude files handled? It would seem
that the answer is no. The man page is less than explicit in how this
file should be laid out. Any suggestions here?
The backstory is that I'm having to restore to bare metal, and I don't
know which volume has the configuration
Hi,
i've configured Bacula with a copy job that will copy our backups
to a tape.
I've made this configuration:
Job {
...
Type = Backup
Level = Incremental
Full Backup Pool = x-FullPool
Incremental Backup Pool = x-IncrementalPool
Differential Backup Pool = x-DifferentialPool
S
