Am 18.08.25 um 23:48 schrieb Rob Gerber:
Glad it's working now!
me too!
re: encryption: What version of bacula are you running now? What errors
are you getting with encryption enabled?
It seems it wasn't able to access existing Volumes that were encrypted.
I disabled it to get the basics working and will try to proceed from here.
This is my local small test-box. The backups are "real", but I have a
second method etc / so I can start over more or less
This is bacula-15.0.3 on debian-13.0.0
At a glance, your most recent config looks reasonable. I will note that
with one 'drive' device in your SD, and no autochanger, you will only be
able to write one job at a time. This is why one might want to have
multiple 'drives' and an autochanger. MAYBE your spooling will change
this. Not sure, I haven't spooled a disk volume job.
Small setup, no problem with only one job at a time.
Slow disks, only 1 GB/s ... etc
Also, the usual advice is that it normally doesn't make sense to spool
jobs for disk volumes. Spooling attributes is another matter.
I think since you haven't specified 'spool directory = xyz' in your
devices, bacula will spool into the bacula working directory (/opt/
bacula/working if installing from the bacula community repos). Might
want to be sure you have enough space there wherever you are spooling,
if you decide to keep spooling jobs. Also, make sure your spool disk is
fast enough to keep up.
Yes, understood. Just added that for tests ... disabled now.
I think that if you are spooling data to the same disks you will write
the disk volumes to, then it will double the resource usages of the
bacula jobs as it must both read and write from/to the same disk
resources. Better to use separate fast SSD or ramdisk (if UPS supported)
spool disks. Again, however, spooling doesn't usually make sense for
destination media that isn't magnetic tape (or maybe optical disk).
I agree fully.
regarding 'autochanger = something':
I read the bacula manual and typed a lot about it, but I'm not sure what
I typed or read was correct. At most, I would suggest searching the
bacula pdf manual for 'enhanced autochanger support' and reading that
section of the manual. Basically, it looks like 'autochanger = yes' is
valid for device {} resources in bacula-sd.conf, but not valid in
bacula-dir.conf anymore.
Marcin thankfully wrote about that, great ;-)
I am sorry if I have misunderstood something in your emails. Today has
been hectic.
No problem. mondays, we know ... mine was long and hectic as well.
Thanks for your help.
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
