Peter Keller wrote
>
> On 01/04/2016 09:00 AM, pietersnld wrote:
>
>> Found the same in the source code (7.2)
>>
>> /*
>> * Given a Unix date return the week of the year.
>> * The returned value can be 0-53. Officially
>> * the weeks are number
Heitor Faria wrote
>> On 2016-01-04 at 10:46:46 Heitor Faria wrote:
>>
>>> > On 2016-01-04 at 09:01:44 Heitor Faria wrote:
>>> >
>>> >> > Em 4 de jan de 2016, pelo 08:10, pietersnld <
>>> >> >
> pietersnld@.sourcefor
pietersnld wrote
> In the schedule resource the manual says:
>
> = w00 | w01 | ... w52 | w53
>
> So why didn't my backup run in week 53?
> (Still a lot of time to fix no week 53 until 2016.)
>
> Pieter
Still not fixed after 6 years! (At least not in version
Dan Langille wrote
> This affects only FreeBSD users.
>
> At present, when upgrading sysutils/bacula-server or
> sysutils/bacula-client, the port/package will stop bacula-dir & bacula-sd
> (or bacula-fd respectively). This is done as part of the uninstall before
> doing the subsequent install.
>
bacula-13 wrote
> On Mon, 17 Jun 2013 17:52:27 +
> Doug Sampson <
> dougs@
> > wrote:
>
>> According to Laurent, all aspects of the Bacula system (director,
>> storage, & client) must be enabled with LZO support. I haven't tested it
>> without LZO support in the director and storage devices.
I use different pools for each device so jobs can run simultaniously. The
last jobs before the datbase backup migrate all volumes to one pool/device
wich is the place i store all my backups in the end. The migration runs on
the backupserver so no delays on the client. In my case the backupspeed wen
Use different devices on your storage daemon so backups can run parallel.
After your backups migrate the backups on the storage daemon to your final
location. Works for me. In this way I can run 3 jobs the same time.
Pieter
--
View this message in context:
http://bacula.10910.n7.nabble.com/Mul
