You can also do that per Job OR JobDefs too, If you the same schedule for more
than 1 client this may be more appropriate for you:
Job or JobDefs {
Pool = "thisjob-inc-pool" # default 'level' pool *REQUIRED even if not used*
Full Backup Pool = "thisjob-full-pool"
Incremental Backup Pool = "t
lst_hoe02 wrote
> If this is really NFS double-check that both sides agree to use at
> least NFSv3 as older NFS versions have a 2GB limit and Bacula clearly
> is not able to write more data to the file in question.
Spot on, in /etc/autofs.master the file system was mounted with the option
-nf
Woah, that's exactly whath I need.
I'm reorganizing my backup system an I need to restructure the volume
usage, so the best solution is separating full and incremental backups.
Thanks Bill and Silas for teaching me how to do this =D
Now let's implement.
Good bye and thanks.
2012/12/10 Bill Arl
On 12/10/12 11:46, Bill Arlofski wrote:
> Hi Louis,
>
> Yes, you can do this withing a Schedule:
>
> An example is below, but it kind of funny.
heh Should have been "but it wrapped kind of funny"
--
Bill Arlofski
Reverse Polarity, LLC
On 12/10/12 11:19, Luis H. Forchesatto wrote:
> Its possible to separate full and incremental backups from the same client
> in separated volumes.
>
> The client has one full backup weekly and for the other 6 days it has an
> incremental backup. I would like to keep the full backup separated and a
On 12/10/2012 11:19 AM, Luis H. Forchesatto wrote:
Its possible to separate full and incremental backups from the same
client in separated volumes.
The client has one full backup weekly and for the other 6 days it has
an incremental backup. I would like to keep the full backup separated
and a
Its possible to separate full and incremental backups from the same client
in separated volumes.
The client has one full backup weekly and for the other 6 days it has an
incremental backup. I would like to keep the full backup separated and all
the incremental backups that is run during the week b
I am trying to use a tape library for a copy job (for off-site backups).
I have 3 magazines of tapes, and I planned to just rotate between them
for 3 weeks of off-site backups. The first week went fine, but I can't
get the second week to work.
The problem appears to be that Bacula wants to use sp
Robert Wirth dfki.de> writes:
> ...
> Fseek on attributes file failed: ERR=No space left on device
> ...
> Last Volume Bytes: 1,283,646,163,968 (1.283 TB)
>
> Really, the tape isn't full! The other 5 jobs (and this one
> after being rescheduled) continue to write that tape AD0016L5
> which
Hi,
Situation:
--
The backup strategy is doing a yearly Full, monthly Diff and daily Incr.
This worked well over years with Bacula 1.x and 2.x.
Some months ago, I upgraded SD and DIR from Bacula 2.2.8 to 5.0.1
The Diff/Incr jobs continued to do well.
But now, while doing a Full for the
Hello,
2012/12/7 Stieneke, Dan
> Reading the mail archive, it seems I’m not alone in wanting to see
> concurrent spooling/despooling.
>
>
>
> Could we hand off the job to a standalone spooler like mbuffer (
> http://www.maier-komor.de/mbuffer.html)? For a simple tar to LTO-4 job it
> makes a t
11 matches
Mail list logo
