Hello Jose,
Many thanks for letting us know that the SyncOnClose directive is missing
in Bacularis. At the moment I opened a feature request for that in the
Bacularis project on GitHub:
https://github.com/bacularis/bacularis-app/issues/45
Best regards,
Marcin Haba (gani)
On Mon, 20 May 2024 at
I will do it by hand directly in the .conf, I do not see the device option
in Bacularis.
Thanks
On Thu, May 16, 2024 at 1:36 PM Martin Simmons wrote:
> Does this happen with every job?
>
> You could try adding
>
> SyncOnClose = no
>
> to the device settings to prevent it from doing the sync.
>
On 20/05/2024 21:35, Heitor Faria wrote:
Hello Marco,
> i have:
> Maximum blocksize = 512K
I usually don't like setting fixed block sizes, but letting Bacula
determine. But Maximum Block Size = 1 MB or even a little bit more
should be safe for LTO-9.
https://www.bacula.lat/otimizando-a-v
On 20/05/2024 21:25, Heitor Faria wrote:
Hello Marco,
> Anyway, i'm hit another trouble. Seems that creating the spool file
took an
insane amount of time: source to backup are complex dirs, with millions of
files. Filesystem is ZFS.
Is the ZFS local? Does it have ZFS compression or dedup ena
Hello Marco,
> i have:
> Maximum blocksize = 512K
I usually don't like setting fixed block sizes, but letting Bacula determine.
But Maximum Block Size = 1 MB or even a little bit more should be safe for
LTO-9.
https://www.bacula.lat/otimizando-a-velocidade-de-fitas/
https://www.bareos.com
Hello Marco,
> Anyway, i'm hit another trouble. Seems that creating the spool file took an
insane amount of time: source to backup are complex dirs, with millions of
files. Filesystem is ZFS.
Is the ZFS local? Does it have ZFS compression or dedup enabled? I wouldn't use
those options for da
Am 15.05.24 um 16:02 schrieb Rob Gerber:
To manually remove the disk volumes, and associated job and file
entries, do a delete operation. Easily done in Bacularis or baculum, (I
haven't done it in bconsole though I'm sure it's doable there too). I
would have a catalog backup restored BEFORE I