Hi,
I try to understand the copy-job feature. I've a relativ simple setup. I
use three pools. One for full-backups, one for differential-backups and one
for incremental backups. These are configured like this:
Pool {
Name = Full-Pool
Pool Type = Backup
Next Pool = Extern-Full-Pool
Hi and thanks.
I also did it this way and using the old director in parallel until all
clients are migrated.
vol...@gmail.com schrieb am Mittwoch, 29. Juli 2020 um 21:25:41 UTC+2:
> I did upgrade from bareos to bareos using scratch new installation and
> migrating clients to it.
> Once
Hi again,
I setup a Always Incremental bareos configuration, like described hier:
https://docs.bareos.org/master/TasksAndConcepts/AlwaysIncrementalBackupScheme.html
Most of it is working correct, wihtout the last step.
What i want to achieve:
1) Incremental Backups from my clients -> go to
Hi,
i think this post isn't relevant anymore. I had a look at the "Always
incremental feature" ... which fits more to my backup strategy.
Also one question came up with this configuraiton, but I will start a new
thread about that.
Thanks.
Toni
Toni Burger schrieb am Montag, 3. August 2020
Hello again,
now, I'm sure. My longterm Jobs are marked as archive job type, like
described in the manual (with the script step). Archive Jobs are not
selected by the "PoolUncopiedJobs" selector to create a copy.
I could select these job with a own sql query:
SELECT DISTINCT
Hi again,
now, i tried some different approaches. But can't get to a solution :(.
1) I used my sql selection query above
-> Bareos select the jobs, but don't copy it. It says there is already a
copy for the job. That's right ... beacuse the job i try to copy is marked
as Archive :(
2) the
Hi,
i like to migrate from my existing bacula 9.6.5-2 to bareos 19.2.7. I'm
using postgres for the catalog.
I followed this howto:
https://docs.bareos.org/Appendix/BackwardCompatibility.html#upgrade-from-bacula-5-2-to-bareos
I'm aware, that my bacula version was not tested for upgrading.
