[Bacula-users] ZFS not Restoring. (bad magic number)
Hello Folks. I am trying to configuring a ZFS Filesystem Dataset Backup using bacula. It has being a great learning, but a hard one too. I used the configurarion that Ben provide me, and after lots of Head Shaking I was able to Backup and Restore a Dataset Container to the Server. https://github.com/login?client_id=7e0a3cd836d3e544dbd9&return_to=%2Flogin%2Foauth%2Fauthorize%3Fclient_id%3D7e0a3cd836d3e544dbd9%26redirect_uri%3Dhttps%253A%252F%252Fgist.github.com%252Fauth%252Fgithub%252Fcallback%253Freturn_to%253Dhttps%25253A%25252F%25252Fgist.github.com%25252Foptiz0r%25252F68cb93172d72d2f8db48f7ab7b67c28e%26response_type%3Dcode%26state%3D922c7d4754dbaf1d19f928d907dcc29c48ecf6f3539633f4747f14c8d9025a87 Now I have another issues. Every time I try to copy the restore from the created zfs dump file to the production dataset it appears the following error Cannot receive: invalid stream (bad magic number). Can anyone help? Regards all Sergio Sa ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Ubuntu 22.04: bacula-fd from official repo cannot talk to src-compiled server on 20.04
> On Tue, 14 Nov 2023 09:42:44 +0100, Uwe Schuerkamp said: > > Anyway, I compiled openssl-3.0.12 from source on the 20.04 director / > stored and provided the location to bacula's configure script using > the "--with-openssl" directive in order to recompile it using the new > libraries / binaries in /server/openssl-3.012 (the chosen installation > location for the modern openssl). > > Sadly, bacula's "configure" failed to pick up the correct location and > insisted on using the system-provided binaries and libraries from the > old, system-provided ssl installation, so I guess something is not > right w/r to bacula's configure option for openssl. The --with-openssl=..path-to-openssl-install.. option works for me (Debian 11), where ..path-to-openssl-install.. is the path containing files like: include/openssl/ssl.h lib/libssl.so Also, LD_LIBRARY_PATH needs to be set at runtime. __Martin ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Compiling SD only
I got Bacula v11 compiled on my D-Link DNS-325 NAS. The steps needed were: Replace the stock firmware with Entware Install the Entware development toolchain and associated tools Download and compile Sqlite3. A DB is required in order to compile Bacula as there is no flag to enable compiling the SD only. Make will fail unless it finds a .h file for the chosed DB. Compile Bacula. I have a compile script which l'd be happy to share with anyone interested. There are a couple of tricks in there I found necessary. The last step will be to define the DIR conf on the Director box and the SD conf on the NAS. This is the bit I'm stuck on. Would anyone be able to share an example Director dir.conf and SD sd.conf for a remote SD? -Chris- On Sat, 11 Nov 2023, 14:08 Chris Wilkinson, wrote: > Thanks. I couldn't find one so you must be right. Is there a definitive > list of all the valid flags anywhere? I've never managed to find that > either. > > -Chris- > > On Sat, 11 Nov 2023, 12:40 Radosław Korzeniewski, < > rados...@korzeniewski.net> wrote: > >> Hello, >> >> sob., 11 lis 2023 o 12:08 Chris Wilkinson >> napisał(a): >> >>> I would like to compile SD only on a NAS. I have compiled FD only in >>> another context using the enable-client-only flag but not sure if there is >>> an equivalent SD flag. Could anyone advise what flag to use? >>> >> >> No such flag exists, AFAIK. You can simply delete Director after >> installation. >> >> best regards >> -- >> Radosław Korzeniewski >> rados...@korzeniewski.net >> > ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Ubuntu 22.04: bacula-fd from official repo cannot talk to src-compiled server on 20.04
On Thu, Nov 09, 2023 at 09:46:25AM -0500, Phil Stracchino wrote: > > One presumes you are aware of how old your Director's OpenSSL is? > Hello Phil, one presumes correctly. :-) However I was under the impression that a modern bacula (13.0.3) would either be able to talk to clients on new Ubuntu releases if using the bacula-fd from bacula's own repos for 22.04 or that "configure" on Ubuntu 20.04 (still in support) would complain loudly about the age of the system-provided ssl library. Anyway, I compiled openssl-3.0.12 from source on the 20.04 director / stored and provided the location to bacula's configure script using the "--with-openssl" directive in order to recompile it using the new libraries / binaries in /server/openssl-3.012 (the chosen installation location for the modern openssl). Sadly, bacula's "configure" failed to pick up the correct location and insisted on using the system-provided binaries and libraries from the old, system-provided ssl installation, so I guess something is not right w/r to bacula's configure option for openssl. I'd be grateful for any hints on how to fix this. I'm aware I'll need to update the bacula server eventually to Ubuntu 22.04 but for now it seems a bit overkill just because it fails to talk to a single client of among 50 others that are still ticking along nicely. All the best, Uwe -- Uwe Schürkamp // email: ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
