[Providing some context to the messages by quoting at least part of the
previous thread is helpful for people to understand.]

On 2017-11-16 at 09:52 CST Douglas Rand wrote:
Seitan, do you see how your consolidate job is using the Consolidated
pool? In your CLNT_root job you over-ride the pool to be Incremental. But
you don't in the consolidate job, so the definition from the root_cons
jobdefs takes effect.   In your root_cons jobdefs try setting the Pool
to Incremental.

If you follow the documentation at http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-28600023.3 you'll have good luck. You'll have to reference >>
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#x1-1570009.14
to find some of the details to fill in.

On 11/20/17 00:12, Seitan wrote:
but won't this setting make all consolidations go into incremental
volumes? What I've tried to to is to make daily backups to land into
Incremental volumes and all consolidations (even full consolidations) to be
written into Consolidated volumes.

The documentation sets this out fairly clearly:

In case of a Copy or Migration job, this setting determines what Pool will
be examined for finding JobIds to migrate. The exception to this is when
Selection Type Dir Job = SQLQuery, and although a Pool directive must still
be specified, no Pool is used, unless you specifically include it in the SQL
query. Note, in any case, the Pool resource defined by the Pool directive
must contain a Next Pool Dir Pool = ... directive to define the Pool to
which the data will be migrated.

And consolidation jobs are really nothing but automated virtual full jobs. The Next Pool directive says where to WRITE the job. But the Pool directive says where to READ the data for the job. You need both a source and destination.

--
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to