Zitat von Adam Podstawka <[email protected]>:
Hi, i have a little creepy Problem.All Jobs, which take more than a day (24h), are always run as a FULL job. Any tips or suggestions where to begin to get the problem solved?
To my knowledge Bareos decides at starttime of the job if it should be a full, incremental or whatever so the duration of the job doesn't matter at all. I suspect that you lack some valid previous full backup within the retention period so you should carefully check this settings.
It's a bit ugly, because of the amount of data which is backuped. Some Jobs need for a full something like 30tb to 40tb of tapecapacity.Could this problem lead from the "reschedule if failed" config? I'm running 14.2 on (Ubuntu 14.04 LTS) Linux.And last question, i need plenty of time for jobs with compression enabled, but without it takes somethink like a 10th of the time, should i use more the hardware tapedrive compression from LTO6 or the bareos compression?Thanks Adam
It depends. Bareos compression is done at the client(s) and per file. So if you have many clients with compressable data and congested network you should use Bareos compression to scale with the number of client CPUs. If you have only a few clients and your network is really fast you better let the LTO6 do its job.
Also check if you are using lz4 compression and attribute/data spooling to get the data fast enough to the LTO drive.
Regards Andreas -- 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.
smime.p7s
Description: S/MIME Cryptographic Signature
