Olivier Gagnon <[email protected]> writes: > We use Bareos since 2 years and at first we were doing full backup > every month. The company growing fast, we had to change the schedule > to full backup every three months with differential every week. > > Now we are in another bottleneck. Actually two but they are > related. The first one is that we have 3-4 jobs that needs to run for > days for a full backup. Bareos is configured to cancel lower level > jobs but now each three months, it takes about 15 days to backup > everything. During that 15 days, we are missing quite a lot of daily > backups and the situation is not going to get better with more and > more data to backup.
is it possible to split the jobs? I do that a lot, my biggest servers have 30 different jobs, e.g. /srv/data1/*0 in one job, /srv/data1/*1 in another job ... and so on. that configuration is written in a template language (ERB in my case) to make it readable and less error prone. (unfortunately, my /srv/data2/*4 job still takes more than two days and I can't split it further sensibly :-/) > I have tried to add concurrent jobs but since Incr/Diff/Full backups > are done on three different Pools, the lower level jobs get stucked > anyway because the SD is mounted with a higher level Pool volume. you need a separate Storage and Device definition for each pool. -- Kjetil T. Homme Redpill Linpro AS - Changing the game -- 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.
