Re: [Bacula-users] Which OS is best for bacula ?

[Sven Hartge]

On 10.07.21 00:54, Heitor Faria wrote:


That said,
I would be very happy to run Bacula on any version of Debian -- the
Bacula packagers for Debian work closely with the Bacula project --
I would be a lot happier if they would learn to install it in
/opt/bacula instead of spreading it all over the filesystem though. 


This will probably never happen due to the FHS rules pointed by Sven. I 
even spoke with him about that topic in the past.
*Maybe* with a very special agreement with the Debian Community such as 
the one they made with RedHat (I heard of, couldn't find it) to make a 
few things standard (such as the systemd services).


How would such a special agreement with Debian even look? "Bacula is 
allowed to be installed under /opt/bacula"?


Trying to get such a thing past the policy editors, the DM and the rest 
of Debian will either just be a very quick "No." or an endless 
discussion, with the final result being a "No." again.


To be in Debian proper, all packages have to adhere to the FHS and there 
are no exceptions. Make a special exception for one package and you will 
have to allow this for every other package as well.


And with that precedence set once, I believe the only road to the future 
would then be utter chaos.


And from the sysadmin side I really do appreciate that with Debian 
packages I know that binaries (and other immutable stuff) will be in 
/usr, logs will be in /var/log, volatile stuff will be in /var/cache and 
the configuration will be in /etc.


On the other hand for some commercial software getting installed 
somewhere in /opt, I really don't know where all the stuff is. Does the 
software log to /var/log/NAME or /opt/NAME/var/log? Where are the 
configuration files? etc. etc.


Note: I am not a DD or a DM, but I have been part of the wider Debian 
community for over 20 years by now, so I believe I know how it "ticks".


Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Which OS is best for bacula ?

[Sven Hartge]

On 09.07.21 14:22, Kern Sibbald wrote:

I would be a lot happier if they would learn to install it in 
/opt/bacula instead of spreading it all over the filesystem though.


Sorry, no can do, the Debian Policy clearly forbids this, the FHS has to 
be adhered to.


Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Release 11.0.5

[Sven Hartge]

On 04.06.21 17:18, Dan Langille wrote:

On Fri, Jun 4, 2021, at 8:19 AM, Sven Hartge wrote:

On 04.06.21 08:46, Eric Bollengier via Bacula-users wrote:



If something is wrong, a new release is made and tagged as well.



Same goes for the provided archives. Please don't remove existing ones
and replace them with other archives with the same version.



A project should never do this.

As a packager, you have now made my job much bigger than it needs to be.
This is a non-trivial situation. If there is a problem with the release,
create another release. Your downstream will have much more respect for you
than if you do otherwise.

Please, never do this.


You *can* remove releases, if there are broken or dangerous, I have no 
problems with that.


But please, please, please, do not reuse the version when you create the 
next unbroken release.


Also please tag the exact point that the released archives where made in 
GIT immediately. There may be a time where we need to examine the 
contents of the archives and compare them to the code in GIT.


Grüße,
Sven.



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Release 11.0.5

[Sven Hartge]

On 04.06.21 14:27, Radosław Korzeniewski wrote:
pt., 4 cze 2021 o 14:20 Sven Hartge <mailto:s...@svenhartge.de>> napisał(a):


Yes, it looks bad when you have to release several minor version over a
few days,


I think it is more "patch level" and not "minor version". IMVHO, YMMV.


Yes, of course. My points still remain.

Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Release 11.0.5

[Sven Hartge]

On 04.06.21 08:46, Eric Bollengier via Bacula-users wrote:


It seems that the release process is very attractive these days,
the tags are usually pushed at the end of the procedure (after
few days or when preparing the next release. It's better to
be sure that everything is ok because we cannot overwrite tags
once they are cloned on other git repositories.

Of course, I can push them now, it seems that the release
is correct this time.


I am sorry to say, but that is really strange. Of all the projects I 
follow, Bacula is the only with that interpretation of tag usage.


Everyone else tags a release as soon as it is released and then the 
release it not changed afterwards.


If something is wrong, a new release is made and tagged as well.

Same goes for the provided archives. Please don't remove existing ones 
and replace them with other archives with the same version.


This makes life really difficult for distributions when you add a new 
version and then suddenly it is revoked and replaces by a new release 
with the same version number.


If you for example release 11.0.5 and we upload this to Debian and two 
days later you remove the release and replace it, we would then need to 
"invent" a version number like 11.0.5.1 to be able to upload the new 
version.


Yes, it looks bad when you have to release several minor version over a 
few days, but please think of the people downstream of you.


Grüße.
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Race condition creating volumes on two different NASes

[Sven Hartge]

On 13.05.21 08:36, Andrea Venturoli wrote:

12-May 22:45 jack-dir JobId 8096: Error: sql_create.c:439 Create DB 
Media record INSERT INTO Media 
(VolumeName,MediaType,MediaTypeId,PoolId,MaxVolBytes,VolCapacityBytes,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,VolStatus,Slot,VolBytes,InChanger,VolReadTime,VolWriteTime,VolType,VolParts,VolCloudParts,LastPartBytes,EndFile,EndBlock,LabelType,StorageId,DeviceId,LocationId,ScratchPoolId,RecyclePoolId,Enabled,ActionOnPurge,CacheRetention)VALUES 
('Inc4403','File',0,4,53687091200,0,1,7776000,0,1,0,'Append',0,0,0,0,0,0,0,0,'0',0,0,0,3,0,0,0,0,1,1,0) 
failed. ERR=ERROR:  duplicate key value violates unique constraint 
"media_volumename_id"

DETAIL:  Key (volumename)=(Inc4403) already exists.


In the end this seems to be only annoying, as jobs with "warnings" must 
be better checked.

Or am I missing something?


If you are compiling from source, better use the head of the Bacula-9.6 
branch from GIT instead of the published sources, as they miss some patches.


For your case in particular, you need to add this patch:

--- a/src/dird/dird.c   2021-01-19 15:25:16.233573546 -0500
+++ b/src/dird/dird.c   2021-01-19 15:26:23.884070798 -0500
@@ -1263,11 +1263,11 @@
  }
  if (catalog->db_driver) {
/* To copy dbdriver field into "CAT" catalog resource class 
(local)

 * from dbdriver in "BDB" catalog DB Interface class (global)
 */
-bstrncpy(catalog->db_driver, BDB_db_driver, db_driver_len);
+bstrncpy(catalog->db_driver, BDB_db_driver, db_driver_len+1);
  }
   }

   if (!db || !db_open_database(NULL, db)) {
  Pmsg2(000, _("Could not open Catalog \"%s\", database 
\"%s\".\n"),



Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Optimizing Backup Schedule and Storage Space on Backup System

[Sven Hartge]

On 26.02.21 00:47, J W wrote:


3. I would try Virtual backups.
Can I just run virtual full backups periodically after the first full 
backup? I already have full backups so I could just schedule virtual 
full backups instead of full ones.
Do I need separate media types or devices for Virtual Full backups? My 
ZFS partition is already at ~ 80 % so I do not have much room.


Are Virtual full backups sort of like pruning so that my oldest backup 
data is from when the last VirtualFull took place?


Important when doing Virtual Full Backups: You *have* to enable Accurate 
in your Incrementals and Differentials or your VirtualFull will grow and 
grow and grow because deleted files are never removed.


Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Fwd: bacula-fd errors on backupCatalog run

[Sven Hartge]

On 20.02.21 21:12, Robert Earl wrote:

If I create a zero-size file in the proper place on the client, the 
Catalog backup proceeds, but is of course null. Why is it even looking 
for a database??


The catalog backup is done in two steps:

1) A RunBeforeJob running on the host where the Catalog resides dumps 
the Catalog into a file.

2) This file is then backupped via the FD running on that host.

The FD in itself does not need any knowledge about the Catalog Database 
type.


In your case either the FileSet for the CatalogBackup is wrong (meaning 
the dump is in a different location) or the RunBeforeJob fails or is 
missing.


It seems the AfterJob is running, but either your log from the mail is 
truncated or the RunBeforeJob really is missing. Check the definition of 
the BackupCatalog job.


Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula-fd with ESXi 6.5

[Sven Hartge]

On 12.01.21 22:34, mau...@gmx.ch wrote:

Please to Backup with Bacula 9.4.x the VM’s are possible to install 
BaculaFD on my Free-Esxi?


No, you cannot install the FD onto you ESXi server, regardless of the 
version.


Also: To backup VMs directly you need a VMware License because the API 
needed is not available in the free version.


And: Using said API is a paid Bacula Enterprise feature.

But you can backup the contents of a VM by installing the FD *inside* 
the VM, just like with every other system.


Grüße,
Sven


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Deb packages for mariadb?

[Sven Hartge]

On 18.12.20 15:49, Daniel Rich wrote:

The bacula-director package that comes with Ubuntu 20.04, doesn’t 
include any database support as far as I can tell other than possibly 
sqlite. I couldn’t even get it to start with the database configs I 
currently have.


Yes, because you need the bacula-director-DBTYPE packages to select you 
SQL dialect.


But when installing the bacula-director package Postgres-Support is 
selected as default variant.


You need to manually install bacula-director-mysql if you want that variant.

Grüße,
Sven.



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Deb packages for mariadb?

[Sven Hartge]

On 17.12.20 22:49, Daniel Rich wrote:


The ones that come with Ubuntu 20.04 are nearly a year old (9.4.2)


That is not something we Debian Developers can directly influence. But 
you can take the Debian sources and rebuild them on a Ubuntu-System and 
it will work.



and don’t include mysql support as far as I can tell. I don’t really
want to have to covert my configs back to the debian-supplied version
since I’ve been running the bacula.org version for over a years.


Nobody uses MySQL anymore, every distribution has converted over to 
MariaDB by now. This will not go away.



Since I’m building a new server, I’m considering moving to 11.0, but
 there aren’t packages for that yet, so I would still need the debian
 package files to build my own.


I would hold back on 11 for a bit. The database transition from 9 to 11 
is a bit rocky at the moment. So far, the official word on 11 is "it is 
a beta".


Grüße,
Sven.



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Deb packages for mariadb?

[Sven Hartge]

On 17.12.20 07:22, Daniel Rich wrote:

Does anyone know where I can find the packaging files for bacula? I 
cloned the git repo, but while it has the source for building the 
software it doesn’t have any of the packaging files (i.e. the debian 
directory and assorted files).


Since I can’t install the current binary packages without removing 
MariaDB and installing MySQL, it looks like building my own from source 
is the only way to go. And I really don’t want to have to run a manual 
install if I can build debian packages instead.




Debian provides up-to-date Bacula packages working with MariaDB via 
Buster-Backports.


The only downside of those package is they don't support S3 and the 
Docker-Plugin.


Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Deb packages for mariadb?

[Sven Hartge]

On 10.12.20 18:05, Phil Stracchino wrote:


Hmm.  *Some* twerp somewhere appears to be harvesting this list for spam
- or possibly someone on the list has a compromised mail account or
Windows PC.  Y'all might want to check whether you have strange outgoing
mail.


Compromised Account or PC it is in this case.

There is a ZIP attached to the mail with an .xslb (Excel Workbook) file 
inside which contains the usual Trojan dropping Macros, quite possible 
Gootkit, Ryuk or Emotet.


I passed through some online virus scanners and at the time of test none 
recocgnized it.


https://virusscan.jotti.org/en
https://www.virustotal.com/gui/

But when using to sandbox the thing using 
https://www.hybrid-analysis.com/ it clearly showed it trojanity.


Be careful out there!

Grüße,
Sven.



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Baculum 9.6.6.1 with ubuntu 20

[Sven Hartge]

On 24.10.20 04:17, Marcin Haba wrote:


Please let know if it helped.


Bacula 9.6.5 in Ubuntu 20.04 would still be affected by LP:#1898006, right?

Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] ERR=Function not implemented

[Sven Hartge]

On 04.10.20 18:46, Marc Chamberlin via Bacula-users wrote:


04-Oct 03:05 bigbang-fd JobId 1782: Error: Read error on 
file/sys/kernel/slab/:d-0001024/alloc_calls. ERR=Function not implemented


You are trying to backup the virtual /sys filesystem. You can't do that 
and it also makes to sense to do that, as all this (and /proc) contains 
are run-time information of the running Kernel.


You should add "OneFS=yes" to your Fileset and then specify every real 
filesystem which contains data you want to backup.


Hint /dev, /sys, /proc and /run are all not worthy of being saved.

Grüße,
Sven.


OpenPGP_0x6986401191B2164B.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Cloud driver for OCI

[Sven Hartge]

(Sorry, I sent this via private-only mail first.)

On 23.06.20 18:38, Kern Sibbald wrote:

> libs3.git is currently available on www.bacula.org in exactly the same
> way that bacula.git is available.

Where? I don't see it on https://www.bacula.org/git/ and both
https://www.bacula.org/libs3 and https://www.bacula.org/libs3.git are
"404" and https://www.bacula.org/git/cgit.cgi/libs3/ returns "No
repositories found".

If there is a link to it somewhere it is not obvious or easy to find. At
least for me.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Cloud driver for OCI

[Sven Hartge]

On 23.06.20 17:26, kern wrote:

> What I would appreciate the most would be for a community to submit a
> patch to our current libs3 code base.

You having the bacula-libs3 code available via a public git repository
might be a first step in that direction.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 S3 module on Debian10.

[Sven Hartge]

r0...@nxlplyx.com  wrote:
> Thank you.  The patches have now solved the both the duplicate case
> statements and the strncat errors.

> HOWEVER,  I am now getting a missing stddef.h error.

> It is looking for it in a gcc 9 installation.   But Debian 10 does not
> have gcc 9 installed, it has only gcc 8 installed.

> stddef.h DOES exist in '/usr/lib/gcc/x86_64-linux-gnu/8/include/stddef.h'

> Might there be a patch for this? 

I can not reproduce this problem on a Debian 10 system.

Maybe your system isn't as clean as you think it is?

> -

> $ patch request.c < support-newer-curl.patch
> patching file request.c

> $ patch request.c < fix-buffer-sizes.patch
> patching file request.c

> $ make deb
> make: *** No rule to make target
> '/usr/lib/gcc/x86_64-linux-gnu/9/include/stddef.h', needed by
> 'build/obj/acl.do'.  Stop.

> -


Please do a 

 make VERBOSE=1 clean

and then retry with 

 make VERBOSE=1 deb

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 S3 module on Debian10.

[Sven Hartge]

On 31.05.20 14:06, r0...@nxlplyx.com wrote:

> Unfortunately there are now four(4) new errors, all appearing to be
> related to the strncat function.
> 
> I don't suppose there is a patch for this?
> 
> -
> 
> $ make deb
> build/obj/request.do: Compiling dynamic object
> src/request.c: In function ‘sort_and_urlencode_query_string’:
> src/request.c:865:9: error: ‘strncat’ specified bound 1 equals source
> length [-Werror=stringop-overflow=]
>  strncat(result, "&", 1);
>  ^~~
> In function ‘sort_and_urlencode_query_string.constprop’,
>     inlined from ‘canonicalize_query_string’ at src/request.c:884:9,
>     inlined from ‘setup_request.part.2’ at src/request.c:1519:5,
>     inlined from ‘setup_request’ at src/request.c:1477:17:
> src/request.c:822:5: error: ‘strncpy’ specified bound depends on the
> length of the source argument [-Werror=stringop-overflow=]
>  strncpy(tokenized, queryString, strlen(queryString) + 1);
>  ^~~~
> src/request.c: In function ‘setup_request’:
> src/request.c:822:37: note: length computed here
>  strncpy(tokenized, queryString, strlen(queryString) + 1);
>  ^~~
> In function ‘sort_and_urlencode_query_string.constprop’,
>     inlined from ‘canonicalize_query_string’ at src/request.c:884:9,
>     inlined from ‘setup_request.part.2’ at src/request.c:1519:5,
>     inlined from ‘setup_request’ at src/request.c:1477:17:
> src/request.c:863:13: error: ‘strncat’ output truncated before
> terminating nul copying as many bytes from a string as its length
> [-Werror=stringop-truncation]
>  strncat(result, appendage, strlen(appendage));
>  ^
> cc1: all warnings being treated as errors
> make: *** [GNUmakefile:223: build/obj/request.do] Error 1

Problem with that is the very very poor code quality of libs3 (which I
have lameted quite often) and newer compilers now warn or error out when
encountering those problems.

I hava another patch at
https://salsa.debian.org/hartge/libs3/-/raw/master/debian/patches/fix-buffer-sizes.patch,
please try if this fixes or at least works around those problems.

Note: no guarantee is made by me that this creates a working or even
safe and secure library.

Grüße,
Sven.





signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 S3 module on Debian10.

[Sven Hartge]

On 31.05.20 02:00, r0...@nxlplyx.com wrote:

> I am trying to compile the S3 module for Bacula 9.6.3 on a new install of 
> Debian 10.
> 
> That would be the source file:   'libs3-20181010.tar.gz'
> 
> I unzip it, it extracts to its own directory. I cd to the directory, and
> follow the instructions which say to type: 'make deb'.

That version will not compile on any system with curl>7.62.

You need the following patch to fix that problem:

https://salsa.debian.org/hartge/libs3/-/raw/master/debian/patches/support-newer-curl.patch


Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 S3 module on Debian10.

[Sven Hartge]

(Please don't Cc: me on mails.)

On 30.05.20 19:31, r0...@nxlplyx.com wrote:

> ---
> $ make deb
> build/obj/request.do: Compiling dynamic object
> src/request.c: In function ‘request_curl_code_to_status’:
> src/request.c:1709:5: error: duplicate case value
>  case CURLE_SSL_CACERT:
>  ^~~~
> src/request.c:1705:5: note: previously used here
>  case CURLE_PEER_FAILED_VERIFICATION:
>  ^~~~
> src/request.c: In function ‘sort_and_urlencode_query_string’:
> src/request.c:865:9: error: ‘strncat’ specified bound 1 equals source
> length [-Werror=stringop-overflow=]
>  strncat(result, "&", 1);
>  ^~~
> cc1: all warnings being treated as errors
> make: *** [GNUmakefile:223: build/obj/request.do] Error 1
> ---

If you could describe in a more complete manner what exactly you do, we
might be able to better follow and help.

For example it is totally unclear to me what sources you are trying to
compile and what you did in what environment when you where doing it.

Grüße,
Sven.
(Please don't Cc: me on mails.)



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Startup Scripts not Working

[Sven Hartge]

On 19.05.20 17:27, Chris Wilkinson wrote:

The correct permissions for a Debian/Ubuntu system are as follows:

> bacula-dir.conf 755 bacula:bacula

640 bacula:bacula

> bacula-sd.conf 755 bacula:bacula

640 bacula:bacula

> bacula-fd.conf 755 root:bacula

640 root:root

> /var/lib/bacula/ 755 root:root

700 bacula:bacula

It is imperative that every file containing passwords is not readable by
the whole systems but only by either the root or bacula user.

Als /var/lib/bacula my contain state files or database dumps which
should not be world accessible.

Grüße,
Sven,



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Startup Scripts not Working

[Sven Hartge]

On 18.05.20 18:25, Chris Wilkinson wrote:

> I upgraded my server to Debian Buster (10) and took the opportunity to
> upgrade Bacula to the repo version (9.4.2). I retained my existing
> /etc/bacula/*.conf files.
> 
> I had no luck getting the services to start (exited with error) 

What errors?

> Has anyone used these successfully with these ownerships?

Yes, I have.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Sven Hartge]

On 10.05.20 15:01, Kern Sibbald wrote:

> I agree with Sven, libs3 is a big disaster.  It works well but the
> author abandoned it, and many things have changed since then.  For the
> moment, we have a version that works with AWS (don't expect it to work
> with a number of other S3 implementations, which are not compatible with
> AWS).

Adding to that: Other than the horrendous possible security flaws
present in libs3 (try to compile with a recent GCC and see for yourself)
the nature of anything cloud-bases is inherently volatile.

The AWS-API may change at any given moment (and it has in the past),
making libs3 incompatible without updates.

And without an upstream author implementing those changes, your backups
are more or less gone.

My very pessimistic view on the situation is: Don't use any backup
solution using libs3 if you value your data.

But: YMMV.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[Sven Hartge]

On 09.05.20 22:48, r0...@nxlplyx.com wrote:

> It is the S3 modules that I need.  This may help explain why I have not
> been able to get the S3 module of Bacula 9.6.3 to work in for Ubuntu 18.04.

To get the S3 driver working, you need the special libs3 provided by
Bacula systems. The libs3 included in Ubuntu (and Debian) will not work.

(This is also why the Debian and Ubuntu packages don't include the S3
driver in the first place, because of the whole disaster that is libs3
to begin with.)

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Why bdirjson is not available bacula-director in repo Debian?

[Sven Hartge]

On 06.05.20 00:08, Jose Alberto wrote:

> Why bdirjson is not available in repo oficial Debian?    

bdirjson is available in the Debians official packages:

bacula-common: /usr/lib/bacula/bdirjson

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Community for latest Debian and Ubuntu versions

[Sven Hartge]

On 29.04.20 17:27, Markku Leiniö wrote:

> Hi, what is the recommended method to install Bacula Community version
> (latest 9.6.3) on Debian 10 Buster or Ubuntu 20.04? Neither of those
> have 9.6.x in the distributions' own repos (they have 9.4.2), and the
> community repo for Bacula does not have anything for those.

Version 9.6.3 is now available via buster-backports for all arches
besides mips64el/mipsel, which should folllow in a day or two.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula Community for latest Debian and Ubuntu versions

[Sven Hartge]

On 29.04.20 17:27, Markku Leiniö wrote:

> Hi, what is the recommended method to install Bacula Community version
> (latest 9.6.3) on Debian 10 Buster or Ubuntu 20.04? Neither of those
> have 9.6.x in the distributions' own repos (they have 9.4.2), and the
> community repo for Bacula does not have anything for those.
> 
> Or is it just best to get going with 9.4.2 at this point?

Debian will get 9.6.3 via buster-backports in the foreseeable future. I
can't speak for Ubuntu though.

Grüße,
Sven
(Co-Maintainer Bacula in Debian)



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Possible GPL licence violation via docker/baculatar/tar binary

[Sven Hartge]

On 27.02.20 17:42, Radosław Korzeniewski wrote:
> Hello,
> 
> czw., 27 lut 2020 o 17:38 Sven Hartge  <mailto:s...@svenhartge.de>> napisał(a):
> 
> On 27.02.20 15:57, Radosław Korzeniewski wrote:
> 
> > Does Debian distribute any other Docker container images as deb
> > packages? I do not know, so I'm curious.
> 
> I don't know either from the top of my head but I didn't check.
> 
> But the whole idea of shipping a Docker image inside a Debian package
> sounds strange to me, as you either pull the image from the Hub or build
> one yourself.
> 
> 
> Exactly. So the baculatar should not be the part of Debian packaging and
> build procedure. You should not bother yourself with it.

Which is what I am planning to do.

But shipping the directory inside (for example( the
/usr/share/doc/bacula-fd/examples directory, so any interested person
can use it to build the container locally is worthwhile, I think.

This means any components needed to use the FD plugin are available.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] packages for Debian buster available?

[Sven Hartge]

On 11.12.19 12:17, gregor.bu...@gmx.de wrote:

> I want to try bacula on an debian buster system. But there aren't
> packages for buster available now?

There are official Debian packages available:
https://packages.debian.org/buster/bacula

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.X run on Debian 10 Buster?

[Sven Hartge]

On 20.09.19 12:29, Jose Alberto wrote:

> Bacula 9.X  run  on  Debian 10 Buster?  

Bacula 9.4.4 is available from the normal Debian Buster repositories.

Newer versions will be available (when released) via the Debian
Backports repositories.

Grüße,
Sven
(Debian Bacula Co-Maintainer)



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Converting from Sqlite3

[Sven Hartge]

On 04.07.19 12:24, Axel Kittenberger wrote:

> I just upgraded my bacula dir/sd server to debian buster and the update
> messages told me, sqlite3 would no longer be supported by bacula and a
> conversation would be recommended.
> 
> PS: Since the official release of buster is imminent, I suppose there
> will be a bunch of people stumbling over this soon.

Bacula on sqlite3 will be supported for the lifetime of Buster.

Beyond Buster: nobody knows yet. It may very well be possible for
Carsten and me to decide the remove support for sqlite3 for Debian
11/Bookworm.

Grüße,
Sven (Debian Bacula Co-Maintainer)



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] cloud_dev could not open Cloud driver type=1 for Device=CloudStorage

[Sven Hartge]

On 01.07.19 13:11, Kern Sibbald wrote:

> Yes, this is a problem.  I remember we discussed libs3 some time ago,
> but I did not realize that it has a number of security issues.

I am no C/C++ wizard but just the fact that I need to disable about all
checks and warnings a modern compiler has to even get the code to
compile tells me as much as I need to know. Also looking at the commits
after December 2016 tells the same, as there are several commits fixing
memory leaks and buffer overflows.

> Do you see any other alternative for a C/C++ than to use libs3?

I'm sorry, unfortunately everybody seems to have forked and embedded
libs3 at some point in the past and just uses that version for their
projects, with all the problems it contains.

Everyone else seems to use Rust or Go for their S3-based projects. :)

> For other S3 vendors, Bacula Systems has resorted in using the vendor
> supplied command line tools to access the their clouds.  This gets
> around the incompatibility of S3 implementations problems, but it opens
> new problems in that the vendors typically supply binaries, and if they
> have problems or bugs there is no way to fix them.  So far, I have no
> good solution to the problem.   I would be interested in any of your
> suggestions.

I am afraid I really have none at the moment.

> In fact, if I thought there were enough Bacula users using AWS S3, I
> would even consider fixing and maintaining the libs3 package myself.  Of
> course that would be workable only if Debian and perhaps other vendors
> would adopt such a project.

The Debian policy allows for embedding libraries in special
circumstances, for example if the forked code diverges enough from the
library already in the Debian repository that using the existing one is
difficult or impossible.

(Besides, the current libs3 has no reverse dependencies and is
essentially useless and should be removed.)

There should be no problems if you fork libs3, fix it to meet modern
security and coding standards and just embed it into Bacula to be
statically linked to the SD or just the plugin.

But since I am not DD/DM, take my words with caution.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] cloud_dev could not open Cloud driver type=1 for Device=CloudStorage

[Sven Hartge]

On 30.06.19 16:57, Sven Hartge wrote:

> We would need to ship the special libs3 either as embedded code inside
> the Bacula source package or package it as a separate libs3-bacula
> package. Both will get an instant veto from the Security Team and the
> Release Managers. (Debian Policy §4.13)

The main problem here is that libs3 is already in Debian, but in the
ancient version 2.0 which doesn't even work with today's S3 anymore. (It
really should be removed from Debian, to be honest.)

After version 2.0, there have no new official releases been made by the
upstream developer and looking at the commit history on Github it seems
largely abandoned, aside from some merges PRs here and there.

When Bacula Systems implemented the Cloud driver in 2016.12.09 it used
the then git-HEAD of the library but it was still in flux back then, so
any version a bit older or a bit newer will not work with Bacula, so
even if Debian shipped a newer version, it would be incompatible with
Bacula.

Now, that special version from 2016.12.09 still contains some very
jarring problems including buffer overflows or memory leaks.

No distribution would want to support that code.

But we already went over this back when 9.4.0 was released and Carsten
and I tried to package the Cloud driver for Debian but gave up when it
dawned on us what an ordeal it would be to achieve this in the
constraints of Debian.

Grüße,
Sve.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] cloud_dev could not open Cloud driver type=1 for Device=CloudStorage

[Sven Hartge]

On 30.06.19 14:21, Kern Sibbald wrote:

> The Bacula project provides the correct libs3 package at
> 
> https://www.bacula.org/downloads/libs3-20181010.tar.gz
> 
> Normally when building, you download the .tar.gz file, detar it, build
> the package then make sure your packaging uses the special version
> rather than the one supplied on the system.

This is all fine and good, Kern, but forbidden by the Debian policy.

During build, not external downloads or even network connections are
allowed. Doing so would be an instant FTBFS and thus release-critical bug.

Debian Policy §4.9 cleary states:

"For packages in the main archive, no required targets may attempt
network access, except, via the loopback interface, to services on the
build host that have been started by the build."

We would need to ship the special libs3 either as embedded code inside
the Bacula source package or package it as a separate libs3-bacula
package. Both will get an instant veto from the Security Team and the
Release Managers. (Debian Policy §4.13)

So, unfortunately, it is impossible for Debian (and Ubuntu) to ship the
Cloud Driver in an official package at the current time.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] cloud_dev could not open Cloud driver type=1 for Device=CloudStorage

[Sven Hartge]

On 28.06.19 17:32, Antonino Balsamo wrote:

> I'm running bacula 9.4.2 on stretch with debian packages from
> stretch-backports. I've added the cloud plugin from the Bacula package
> and I got the following error:
> 
> JobId 2: Fatal error: cloud_dev.c:690 Could not open Cloud driver type=1
> for Device=CloudStorage
> 
> Then I removed all packages and installed 9.4.4 from Bacula archive
> including cloud plugin, the error remains the same.
> 
> Going to the source code, it seems that HAVE_LIBS3 always evaluate to
> false.
> 
> I do not think I have the talent to recompile the packages, but maybe
> I'm doing a mistake somewhere else?

The Cloud driver is not compiled and supported in the Debian packages
because it needs a very special, very old version of libs3, not present
in Debian and unfortunately it is also not possible to get that version
into Debian at the current moment.

So I am afraid Debian will not be able to provide Cloud-support in
Bacula for the foreseeable future.

Grüße,
Sven
(Debian Bacula Co-Maintainer)



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula and SQLite

[Sven Hartge]

On 29.04.19 20:57, Josip Deanovic wrote:

> It's not that SQLite is bad or does not have the needed capabilities
> but it simply adds to the complexity of the source and maintenance of
> bacula features.

Also besides Carsten Leonhardt and me from Debian nobody has been
testing or even maintaining the SQLite database scripts.

SQLite is only available still because we tested and submitted patches
to keep it working.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Persistent device name for autochanger

[Sven Hartge]

On 03.03.19 18:02, William Muriithi wrote:
> Hi Sven,

>> What version is your mtx?
> Its the default that is shipped with RHEL 7.
> 
> [root@eng-backup01 ~]# rpm -qa | grep mtx
> mtx-1.3.12-14.el7.x86_64

1.3.12 is the latest mtx version available.

The code triggering here is in scsi_linux.c:

#ifdef SG_IO
  /* It is prudent to check we have a sg device by trying an ioctl */
  if ((ioctl(DeviceFD, SG_GET_VERSION_NUM, ) < 0) || (k < 3))
  {
FatalError("%s is not an sg device, or old sg driver\n", DeviceName);
  }
#endif

So it does not check the device name (as I suspected earlier) but does
an ioctl against the device which then seems to fail in your case.

Why? Can't say, kernel internals is *way* beyond my expertise.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Persistent device name for autochanger

[Sven Hartge]

On 03.03.19 16:40, William Muriithi wrote:

> Thanks for the link.  I actually looked at it before Hartge responded and 
> funny enough came to the same conclusion.  The info maps the tape nicely but 
> I don't get enough info from udev to do the dame with autochanger.
> 
> I only get this:
> 
> [root@eng-backup01 etc]# udevadm info --name=/dev/sch0  --query=all
> P: 
> /devices/pci:40/:40:02.0/:42:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:1/scsi_changer/sch0
> N: sch0
> E: DEVNAME=/dev/sch0
> E: 
> DEVPATH=/devices/pci:40/:40:02.0/:42:00.0/host1/port-1:0/end_device-1:0/target1:0:0/1:0:0:1/scsi_changer/sch0
> E: MAJOR=86
> E: MINOR=0
> E: SUBSYSTEM=scsi_changer

At least in *your* case the system already recognizes the device as SCSI
changer and sets up the special device /dev/sch0 for you.

mtx complaining about it not being an /dev/sgX device is more of a bug
inside mtx clinging to the past device names instead of embracing the
new world.

What version is your mtx?

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Persistent device name for autochanger

[Sven Hartge]

On 03.03.19 16:00, Pedro Oliveira wrote:

> https://nonhazardo.us/tape/storage/udev/2016/03/14/udev-persistent-tape-drive-naming.html

This is all well and fine, but only talks about /dev/stX and /dev/nstX.
But persitently naming the tape devices is not the question here.

The real question is on how to peristently name the *generic* SCSI
device associated with the tape changer.

The values you get inside udev for scsi_generic are rather sparse:

P:
/devices/pci:00/:00:01.1/:02:00.0/:03:04.0/host6/target6:0:2/6:0:2:0/scsi_generic/sg5
N: sg5
L: 0
E:
DEVPATH=/devices/pci:00/:00:01.1/:02:00.0/:03:04.0/host6/target6:0:2/6:0:2:0/scsi_generic/sg5
E: DEVNAME=/dev/sg5
E: MAJOR=21
E: MINOR=5
E: SUBSYSTEM=scsi_generic
E: USEC_INITIALIZED=29531657


Nothing really helpful to base a rule on, IMHO.

Grüße,
Sven.



___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] systemd bacula-director.service masked

[Sven Hartge]

On 28.02.19 17:59, Sven Hartge wrote:
> On 28.02.19 17:17, Hodges wrote:
> 
>> When I try to start bacula in systemd I get a 'failed' message saying
>> unit bacula-director.service is masked
>>
>> Does this matter - I guess so. What to do about it? I have just
>> installed bacula 9.4.2 from the debian repository into Debian 10 and am
>> trying to get it working again
> 
> This is definitely not normal. But you provide not enough information to
> further pin-point the problem.

To provide some closure to this list here: Steve has possibly a broken
(or at least disordered) package system from doing a direct upgrade from
Jessie to Buster. This has nothing to do with Bacula or the Bacula
packages provided by Debian.

We will continue to diagnose the problem over at Debian-User.

Grüße,
Sven.





signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] systemd bacula-director.service masked

[Sven Hartge]

On 28.02.19 17:17, Hodges wrote:

> When I try to start bacula in systemd I get a 'failed' message saying
> unit bacula-director.service is masked
> 
> Does this matter - I guess so. What to do about it? I have just
> installed bacula 9.4.2 from the debian repository into Debian 10 and am
> trying to get it working again

This is definitely not normal. But you provide not enough information to
further pin-point the problem.

I know for certain that the Bacula 9.4.2 packages in Debian Sid/Testing
work out of the box, because a) I helped create them and b) I just
tested a fresh install today.

It would be interesting to know *exactly* what you did to end up in this
situation, because a package doesn't just get masked by itself.

Also since this is most likely a Debian-specific problem, it would be
better to move this discussion over to
https://lists.debian.org/debian-user/ to not overly annoy the Bacula
community with Debian talk.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Storage Daemon Service not working at start-up (after os update)

[Sven Hartge]

On 22.02.19 10:06, Yılmaz Bilgili via Bacula-users wrote:
> 22.02.2019 10:14 tarihinde Sven Hartge yazdı:

>> Why not try the Debian packages? bacula-9.4.2 is available via
>> stretch-backports.
> 
> I thought packages in the script are official Debian packages too. I
> never used backports but will check and try.

No, that page above references the official Bacula community packages
which are different than the official Debian Bacula packages.

The first ones are provided directly by Bacula whereas the latter are
provided by Debian.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Storage Daemon Service not working at start-up (after os update)

[Sven Hartge]

On 21.02.19 19:31, Yılmaz Bilgili via Bacula-users wrote:

> # service bacula-sd status
> ● bacula-sd.service - LSB: Start Bacula Storage daemon at boot time
>    Loaded: loaded (/etc/init.d/bacula-sd; generated; vendor preset:
> enabled)
>    Active: active (exited) since Thu 2019-02-21 10:17:45 +03; 10h ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 481 ExecStart=/etc/init.d/bacula-sd start (code=exited,
> status=0/SUCCESS)
>     Tasks: 0 (limit: 4915)
>    CGroup: /system.slice/bacula-sd.service
> 
> Feb 21 10:17:42 LinSrv systemd[1]: Starting LSB: Start Bacula Storage
> daemon at boot time...
> Feb 21 10:17:45 LinSrv bacula-sd[481]: Starting Bacula Storage Daemon:
> bacula-sd
> Feb 21 10:17:45 LinSrv systemd[1]: Started LSB: Start Bacula Storage
> daemon at boot time.


Unfortunately, your systems uses the legacy SysVinit-scripts to start
the SD. That way you don't get a whole lot of debugging output in the
journal.

Did you compile the SD yourself? Maybe you forgot to add
"--with-systemd=/lib/systemd/system" to enable systemd integration?

> I tried to reinstall bacula but no luck. The system is uptodate Debian
> Stretch 9.7, Bacula 9.4.2 installed with community setup script.

Why not try the Debian packages? bacula-9.4.2 is available via
stretch-backports.

bacula-sd  | 9.4.2-1~bpo9+1 | stretch-backports

Grüße,
Sven.


___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Pool for Linux vs Pool for Windows (linux best perfomance) why?

[Sven Hartge]

On 21.02.19 01:09, Jose Alberto wrote:

> The Pool A where only Linux or Unix are stored. arrives cap 6TB to be
> FULL, this seems fine. But the Pool B where only WindowsServers is saved
> only gets to 2TB to get FULL what I see is not normal.

Maybe your Windows systems don't deliver the data fast enough so the
tape drives insert null blocks to avoid shoe shining, filling the tape
with dummy data in the process.

Do you use spooling? If not, try to enable it and see if this changes
anything.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Error after upgrading to 9.4.1

[Sven Hartge]

On 08.01.19 14:45, Alípio Luiz wrote:

> 08-Jan 09:44 SRVBACKUP-dir JobId 3954: Error: bdb.h:140 bdb.h:140 update
> UPDATE Media SET
> VolJobs=1,VolFiles=0,VolBlocks=52001,VolBytes=3354668902,VolABytes=0,VolHoleBytes=0,VolHoles=0,VolMounts=1,VolErrors=0,VolWrites=52002,MaxVolBytes=0,VolStatus='Used',Slot=0,InChanger=0,VolReadTime=0,VolWriteTime=3970430,VolType=1,VolParts=0,VolCloudParts=0,LastPartBytes=0,LabelType=0,StorageId=1,PoolId=10,VolRetention=518400,VolUseDuration=0,MaxVolJobs=1,MaxVolFiles=0,Enabled=1,LocationId=0,ScratchPoolId=0,RecyclePoolId=0,RecycleCount=0,Recycle=1,ActionOnPurge=0,CacheRetention=0,EndBlock=-940298395
> WHERE VolumeName='Catalog.Vol_0585' failed:
> Out of range value for column 'EndBlock' at row 1

This bug has already been fixed in the GIT repository:

https://bacula.org/git/cgit.cgi/bacula/commit/?h=Branch-9.4=25164d42dbb8a238608dcc72c9c2ef99b73b2080

Just apply the one line fix, recompile and you should be good to go.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] "ERR=database or disk is full" while building directory tree for restore

[Sven Hartge]

On 31.12.18 20:24, Kern Sibbald wrote:

> Yes, MariaDB is supposed to be MySQL compatible, but it is not really. 
> The first time that I installed MariaDB over MySQL (with lots of
> problems -- best to remove MySQL and the DB first), I ran the Bacula
> regression tests and MariaDB failed with a false detection of a lock
> deadlock, which I reported.  It took awhile, but the project did fix the
> problem so it *might* now run Bacula with no problems.  That is to be seen.

I've been running Bacula on Debian for my Universities IT department
since Bacula 1.x, at first with Postgres, then with MySQL and then with
MariaDB once Debian switched to it.

Currently there are 350 Clients with ~30,000 jobs and
~6000,000,000 Files in the database, at a size of ~200GiB. (Which
reminds me to run dbcheck again, since its the new year and everything.)

So far I've never seen any problems with Bacula and the database. (Yes,
I do have a separate DB server with 128GiB RAM to run this on.)

I don't know how Postgres would work and how much resources it would
need (I have no doubt it would work perfectly now.) but I remember in
the very early days, we had massive problems with Postgres, as the
Vacuum process would soon take up all resources, never finish and block
the backup all together. Which is why we switched to MySQL back then.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.4 S3 plugin

[Sven Hartge]

On 31.12.18 20:47, Kern Sibbald wrote:

> Sven's libs3 is surely perfectly OK, but if you want the one that Bacula
> uses, please read the 9.4.1 release notes,
> as you might want to download the Bacula version which is in the
> downloads directory on bacula.org.  Link provided
> in the release notes.

The version in the salsa.debian.org repository *is* essentially the same
version you uploaded to bacula.org/downloads, with two additional
separate patches to get it to compile with a recent GCC and libcurl and
updated Debian packaging mechanisms.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.4 S3 plugin

[Sven Hartge]

On 28.12.18 19:07, Dante F. B. Colò wrote:

> Thanks for your reply,
> 
> In my case m using CentOS 7 , i tried compiled Bacula with libs3
> available on epel repository  which is even older than this branch you
> mencioned but it fails to build , i''l try with the version available on
> your repo. Thank you !

The version in RHEL/Centos7 is about 10 days too old.

A bit of warning though: The code in my repository comes without any
guarantee in any way.

I tried my best to adapt the needed commits from the upstream repository
to the older version, but since I only know C enough to be dangerous,
you should assume the version in the repository is a) broken,  b)
insecure and c) doesn't work at all.

It just passes the "compiles fine and the compiler doesn't complain too
much" phase, but I have not done any test or audit wrt. functionality or
security.

Please, for the love of $deity, don't use this in production for any
data you care about without doing an in-depth audit yourself.

I will not be responsible if by using this code you compromise your data
and open it to whatever third-party might be interested in it.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.4 S3 plugin

[Sven Hartge]

On 27.12.18 20:50, Dante F. B. Colò wrote:

> I'm trying to setup a s3 cloud storage on Bacula Storage Daemon, is
> there any extra dependencies necessary on the system to build Bacula
> with the S3 plugin ?   I already compiled and installed but the
> bacula-sd process dies when Bacula tries to connect and list a cloud
> volume from bconsole.

I dug into this extensivley while trying (note my wording here) to
enable this feature for Debian.

First, you need Bacula 9.4.1, because 9.4.0 was missing a crucial bit in
the configure script, skipping detection of libs3.

Then, as it turns out, you need a very specific version of libs3 for
this, namely the GIT version 06a4683 from 2016-12-14. Any older or newer
and Bacula won't even compile.

To get this ancient version to compile with todays compilers, you need
to add two patches, I've isolated them here
https://salsa.debian.org/hartge-guest/libs3/tree/master/debian/patches.
You need the fix-buffer-sizes.patch and support-newer-curl.patch.

Beware: I just tested successful compilation of Bacula with this version
of the library, I didn't test if it works at all and if it works, it
does so correctly.

There is a thread in bacula-devel going over the whole ordeal, if you
are interested, I suggest reading it as well.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula-sd.conf: permission denied

[Sven Hartge]

On 10.10.18 09:07, Miguel Gutiérrez Páez wrote:

> Hi, just only an idea; what about selinux?

Not on Debian.

Unless Thibault has done some very strange things to his system.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula-sd.conf: permission denied

[Sven Hartge]

On 10.10.18 08:35, krashoverr...@free.fr wrote:

> I've installed like 5/6 bacula solutions for now, and all of them worked as 
> you say, out of the box, all of them installed from Debian repository 
> I just don't understand where the problem is from, and have no idea where to 
> find more debug log (and i like to understand)
> 
> I've also tried to start bacula-sd with -d 99 in order to have debug, 
> everything is correct and the SD starts (but from CLI only)

Trying to debug Bacula itself won't help you here, because the error
lies outside of Bacula, namely in the permissions for /, /etc
/etc/bacula and /etc/bacula/bacula-sd.conf.

Unfortunately you haven't told us what the actual permissions look like
on your system so any help the list may provide is just guesswork.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula-sd.conf: permission denied

[Sven Hartge]

On 09.10.18 14:26, krashoverr...@free.fr wrote:

> I'm having a problem on a virtualized Debian 9 server where i want to install 
> bacula (7.4.4)
> I'm not able to start the SD, while FD and DIR are OK
> 
> When I try to start it with _systemd start bacula-sd_, i'm getting the 
> following
> 
> Oct  9 14:11:29  bacula-sd[6539]: Config error: Cannot open config file 
> "/etc/bacula/bacula-sd.conf": Permission denied
> Oct  9 14:11:29  bacula-sd[6539]: 09-Oct 14:11 bacula-sd: ERROR TERMINATION 
> at parse_conf.c:919
> Oct  9 14:11:29  bacula-sd[6539]: Config error: Cannot open config file 
> "/etc/bacula/bacula-sd.conf": Permission denied
> Oct  9 14:11:29  systemd[1]: bacula-sd.service: Main process exited, 
> code=exited, status=1/FAILURE

How did you install bacula-sd on your system?

If you used the packages from the Debian repository it should just work
out of the box, at least it does in my tests.

/etc/bacula/bacula-sd.conf should be owned by bacula:bacula and have
permissions of 640 (-rw-r-).

The systemd unit starts bacula-sd as user bacula, and this user has
bacula as main and tape as secondary group, it is able to read the
configuration file.

Unless you did something to your system you are not describing here, I
can't see how above error can happen with the Debian packages.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9 and clients 5

[Sven Hartge]

On 10/6/18 5:42 PM, Welington R. Braga wrote:

> Can anyone the same scenery to help me?

Older versions of the FD will always work with newer SDs and DIRs, so
you will be fine.

Some special features do not work with older FDs but backup and restore
will work in all cases.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7+mysql

[Sven Hartge]

Um 16:40 Uhr am 26.05.18 schrieb Dan Langille:

>> On May 23, 2018, at 1:02 PM, Chris Wilkinson  wrote:
 
>> This will seem a dumb question to the experienced Bacula user. I would
>> prefer to use mysql rather than the default sqlite. During installation
>> (Debian Stretch repo, Bacula v7.4.4) I said no to configuring sqlite
>> expecting to be offered the opportunity to configure mysql instead.
>> That didn't happen. I have created an empty bacula database with the
>> appropriate user/permissions but can't figure out how to make Bacula
>> populate it or connect.
 
> That sounds like a Debian packaging problem.

Full disclosure: I am part of the Debian team packaging Bacula, so my
opinion is biased.

I don't think this is a problem with the packages per se.

If you install the correct meta packages for the MySQL variant of Bacula
it will install the needed database and tables in it.

But if you opt out of configuring a database and then later change the
database backend, the system does nothing, as per your selection.

This is clearly stated as caveat on the README.Debian file present:

,
| CHANGING DATABASE BACKEND
| =
|
| This is NOT RECOMMENDED and NOT SUPPORTED FOR LIVE DATA.
|
| Your current database IS NOT transferred to the new database
| backend. The new database backend will have an EMPTY database. Your
| /etc/bacula/bacula-dir.conf file WILL NOT be automatically adapted to
| function with the new database backend, YOU need to do the necessary
| changes to the Catalog{} section YOURSELF.
|
| If you want to go ahead anyway, you change the database backend by
| installing a different bacula-director-DBTYPE package. This will pull
| in the needed dependencies for the new database backend and remove the
| ones from the old one.
`

One nitpick one might have about the Debian Stretch meta-packages of
Bacula 7.4.4 is its default database dependency being SQLite3.

This has since been rectified in the Buster and Stretch-Backports packages
which select PostgreSQL as default database if you install the
bacula-server meta-package.

Grüße,
Sven.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Debian 9 Repo

[Sven Hartge]

On 23.05.2018 11:52, Chris Wilkinson wrote:

> What version of Bacula is currently provided through apt-get?

Debian provides 7.4.4 in the native Stretch repository and 9.0.7 via
stretch-backports:

https://packages.debian.org/source/stable/bacula
https://packages.debian.org/source/stretch-backports/bacula
https://tracker.debian.org/pkg/bacula

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Missing jsons

[Sven Hartge]

On 17.05.2018 22:05, Chris Wilkinson wrote:

> I have installed Bacula and Baculum on Debian wheezy but seem to be
> missing the jsons (/usr/sbin/bsdjson etc.).

Debian Wheezy will be out of Long Term Support in a few days (End of
May). You really really should upgrade all the way to Debian Stretch and
then install Bacula from Stretch-Backports, which contains 9.0.7 and
will work with Baculum.

Grüße,
Sven.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] New Bacula web site

[Sven Hartge]

On 07.05.2018 07:07, Kern Sibbald wrote:

> FYI: Bacula Systems sponsored this new web site to help bring the
> project web site up to current "standards".
> 
> Looking forward to hearing from you.

Well, takes 8MB and ~8s to fully load (with another 6MB in the next 10
seconds) over a 1GBit/s connection from DFN in Germany.

A bit on the heavy side, no?

The biggest files being some included videos from googlevideos.com with
~1.2MB each.

Plus when the site is in focus, Chrome uses about 130% CPU on my system
(using a i7-7820HQ, so a 8-HT-Core system).

Do you really really need all those video-animated backgrounds, for
example in the "Testimonials" area? Removing those does not make the
site look any worse but dramatically cuts down on a) transferred bytes
and b) CPU and RAM usage.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Incorrect datetime value after Bionic Update

[Sven Hartge]

On 05.05.2018 21:07, Ken Mandelberg wrote:

> All is working now, By the way, I wonder if the sql-mode change was
> necessary, the update_mysql_table has a whole bunch of DROP DEFAULT for
> the time and date columns for Mysql 5.7.

All I can say is: the packages Ubuntu pulled in from Debian are not
prepared for MySQL 5.7 or MariaDB 10.2, because Debian does not ship
MySQL anymore and MariaDB is still on 10.1, the packages do nothing to
adapt themselves or the SQL server.

So no wonder you ran into trouble during the upgrade, if Ubuntu did
nothing to configure the database you use correctly for Bacula.

As soon as Debian decides to upgrade to MariaDB 10.2, the Bacula
maintainers in Debian (Carsten and me) need to evaluate on how to
proceed to avoid the problems you had with the database.

Hopefully Bacula itself will be adapted then, so we don't need to change
the global mode of the SQL server, which may be problematic if it is
shared with other databases instead of being exclusive for Bacula.

Grüße,
Sven.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula version 7 Server errors backing up Bacula 9 client

[Sven Hartge]

On 02.05.2018 02:07, Matt Weatherford wrote:

> Q:   Does the Bacula server version 7.4.4 support backing up a client
> running bacula client 9.0.7 ?

No.

> Q:   What else can I look for in order to debug this client?

Upgrade to the Bacula version 9.0.6 (soon 9.0.7) in stretch-backports.
This will solve your issue.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Errors compiling bacula-fd 9.0.6

[Sven Hartge]

On 20.02.2018 10:28, jesus moreno wrote:

> I have compiled bacula client 7.4.7. in Debian Squeeze, without problem.

Bacula-7.4 is not a problem, but Bacula 9.0.6 will not work, because the
support for OpenSSL <1.0.0 was removed between 9.0.5 and 9.0.6.

Grüße,
Sven.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Errors compiling bacula-fd 9.0.6

[Sven Hartge]

On 13.02.2018 13:13, jesus moreno wrote:

> I have a Debian squeeze server with bacula-fd 5.0.3. If I try upgrade to
> bacula-fd 9.0.6, the system show the next errors, when i run "make":

openssl in Squeeze is *way* to old for Bacula 9.0.6. You need at least
openssl-1.0.0.

Debian Wheezy is the oldest Debian you will be able to use Bacula 9.0.6
with.

Besides: Debian Squeeze is out of official support for some time now.

Grüße,
Sven.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Warnings in Debian 9 Stretch when I compile bacula-fd

[Sven Hartge]

On 12.01.2018 18:47, Kern Sibbald wrote:

> I am not sure who's makefile you are referring to, but the Bacula
> project has never used the -Wdeprecated option in any of its makes or
> builds.

No, but it uses "-Wall".

Grüße,
Sven.






signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4.4 - Debian - Free Esxi Virtual Machines

[Sven Hartge]

On 04.01.2018 12:21, Radosław Korzeniewski wrote:
> 2017-12-30 1:40 GMT+01:00 Sven Hartge <s...@svenhartge.de 
> <mailto:s...@svenhartge.de>>:
> On 30.12.2017 00:53, Tilman Schmidt wrote:

> > I use both ways, (a) and (b), in parallel. I use a product called Veeam
> > which specializes in VM backup for snapshot based image backups mainly
> > for disaster recovery. I also do file level backups of important data
> > from within the VMs to be able to recover individual files or records.
> 
> Same here.
> 
> While Veeam B does allow for file level restores,
> 
> 
> Really? Or it is a limitation of the very ancient Veeam versions?

I started with Veeam B 8.0 and this feature was present. So: depends
on your definition of "ancient".

Grüße,
Sven.






signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4.4 - Debian - Free Esxi Virtual Machines

[Sven Hartge]

On 30.12.2017 00:53, Tilman Schmidt wrote:

> I use both ways, (a) and (b), in parallel. I use a product called Veeam
> which specializes in VM backup for snapshot based image backups mainly
> for disaster recovery. I also do file level backups of important data
> from within the VMs to be able to recover individual files or records.

Same here.

While Veeam B does allow for file level restores, doing this via
Bacula is more convenient, especially for Linux/BSD systems.

Also it is good practice to have at least two backups in different
places of important data.

Grüße,
Sven.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4.4 - Debian - Free Esxi Virtual Machines

[Sven Hartge]

On 29.12.2017 23:22, Maurizio Caloro wrote:

> I mount me Free ESXI 6.5 Server, to /mnt/vmware/ but it seem that
> Bacula can't backup running machines, it's this true?

Yes, but this is no limitation of Bacula but a restriction imposed by
ESX. Files of running VMs are locked and can't be accessed directly.

> please how do you made any backup from living machines?

I personally use a tool designed for this use-case: Veeam
Backup (But it does not work with the Free ESX, more on
that later.)

> or you use the Bacula Enterprise Version?

Bacula Enterprise has a plugin to backup virtual machines from
vSphere/ESX
,
but it will also not work with the Free ESX.

This is a licence limitation built in by VMware which restricts access
to the needed backup APIs in the Free ESX and there is no way around this.

> it's possible i have here any understanding mismatch? or i need to
> shutdown the VMWare Machines befor Bacula do his Backup job ?

This would be needed, yes.

> if you made any Backup from your Virtual machines, you shutdown this before
> Backup will make his job?? can you give me any information how you save
> your Virtual machines?

I have a fully licensed vSphere environment, so I can use any tool
designed for that task. If you only have a Free ESX, you are severely
limited.

I'd suggest that you don't backup the VMs externally but instead backup
the contents of the VM the same way you'd backup a physical server. You
can of course use Bacula for that or any other tool.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4.4 openSUSE packages: bad libbaccats symlink

[Sven Hartge]

On 24.12.2017 18:43, Dimitri Maziuk wrote:

> There's nothing private about it, it is installed by the RPM that way.

By "private" I meant: it isn't really a library to be used by external
3rd party tools like for example libcrypto or libmysqlclient is but
rather a library only used internally by bacula itself.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4.4 openSUSE packages: bad libbaccats symlink

[Sven Hartge]

On 24.12.2017 14:34, Tilman Schmidt wrote:
> Am 24.12.2017 um 13:51 schrieb Sven Hartge:
>> On 20.12.2017 21:26, Tilman Schmidt wrote:

>>> libbaccats.so -> /usr/lib64/libbaccats-mysql.so
>>> libbaccats-7.4.4.so -> /usr/lib64/libbaccats-mysql-7.4.4.so
>>
>> Why are the libraries in the system library path? They are private to
>> bacula and should be (to my understandig) in a directory like
>> /usr/lib/bacula/.
> 
> The RPM package installs them there:
> 
> ts@xenon:~> rpm -ql bacula-mysql
> /usr/lib/bacula/create_mysql_database
> /usr/lib/bacula/drop_mysql_database
> /usr/lib/bacula/drop_mysql_tables
> /usr/lib/bacula/grant_mysql_privileges
> /usr/lib/bacula/make_mysql_tables
> /usr/lib/bacula/update_mysql_tables
> /usr/lib64/libbaccats-mysql-7.4.4.so
> /usr/lib64/libbaccats-mysql.so

Hmm. I will go out on a limb a bit here by saying the packaging seems
broken to me then.

But I am biased because I contribute to the Debian packaging and we
deliberately install those libraries into /usr/lib/bacula to avoid such
problems you have here. (Also the Debian Policy forbids the installation
of private libraries or plugins into the system library paths.)

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 7.4.4 openSUSE packages: bad libbaccats symlink

[Sven Hartge]

On 20.12.2017 21:26, Tilman Schmidt wrote:

> libbaccats.so -> /etc/alternatives/libbaccats.so
> libbaccats-7.4.4.so -> /etc/alternatives/libbaccats-7.4.4.so
> libbaccats-mysql.so -> libbaccats-mysql-7.4.4.so
> libbaccats-stub.so -> libbaccats-stub-7.4.4.so
> 
> which allows the symlinks in /etc/alternatives:
> 
> libbaccats.so -> /usr/lib64/libbaccats-mysql.so
> libbaccats-7.4.4.so -> /usr/lib64/libbaccats-mysql-7.4.4.so

Why are the libraries in the system library path? They are private to
bacula and should be (to my understandig) in a directory like
/usr/lib/bacula/.

Grüße,
Sven.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Storage Daemon crashes on Debian 9 with Bacula release 7.4.4+dfsg-6

[Sven Hartge]

On 30.08.2017 15:19, christian.garl...@cg-networks.de wrote:

> We never had such a problem before the upgrade, so we are wondering what
> could be the reason for that.


Could you please add

deb http://deb.debian.org/debian-debug/ stretch-debug main contrib non-free

to your source.list and install the packages bacula-sd-dbgsym and
bacula-common-dbgsym. This should make the backtrace a bit more readable.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.0.3 on Debian 9.1 with OpenSSL-1.0.2l doubts

[Sven Hartge]

On 27.08.2017 14:42, Heitor Faria wrote:
> Hello, Carsten,
> 
 So, is it possible install Bacula 9.0.3 in Debian 9.1 or similar SO with
 newers OpenSSL versions using this way, or this is not possible?
>>>
>>> I just checked and the current in-development version of the
>>> Debian-official packages of 9.0.3 compile in a Jessie-Backports chroot()
>>> for me.
>>>
>>> So after the release of Bacula 9.0.3 in Debian (soonish, I hope)
>>
>> Before I can release Bacula 9.0.3 to Debian unstable, bugs 2305 and 2306
>> about sqlite3 database creation/update need to be addressed.
> 
> SQLite isn't supported anymore by the Bacula developers.
> This was widely advertised in previous threads and changelog.

We know. But the code is still in (for now) and it can at least serve
for a non-production mini-installation or for a quick evaluation setup.

The Debian packages document the state of SQLite in Bacula as
unsupported and to not use them for anything mildly serious.

Grüße,
Sven.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula 9.0.3 on Debian 9.1 with OpenSSL-1.0.2l doubts

[Sven Hartge]

On 23.08.2017 18:20, Wanderlei Huttel wrote:

> So, is it possible install Bacula 9.0.3 in Debian 9.1 or similar SO with
> newers OpenSSL versions using this way, or this is not possible?

I just checked and the current in-development version of the
Debian-official packages of 9.0.3 compile in a Jessie-Backports chroot()
for me.

So after the release of Bacula 9.0.3 in Debian (soonish, I hope) and the
transition to Testing, I may be able to convince Carsten to also release
a version for jessie-backports-sloppy.

Or you can fetch the Debian-patched sources yourself and do the backport
on your own, it is not really difficult to do so.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] [Bacula-devel] Bacula Release 9.0.0

[Sven Hartge]

On 10.07.2017 13:41, Kern Sibbald wrote:

> If the Debian release supports installation of older OpenSSLs, please
> that as a solution, otherwise, I suspect that it will take some time --
> unless someone comes up with a patch, in which case, I will attempt to
> hire that person :-)

Debian 8/Jessie contains OpenSSL 1.0.1t (or a backported 1.0.2l if
needed) so everything is fine there.

Debian 9/Stretch contains both OpenSSL 1.0.2l and 1.1.0f. Bacula is
compiled and linked with the 1.0-variant of OpenSSL.

Debian 10/Buster (to be released in mid 2019) will only contain one
OpenSSL release, version 1.1+.

Somewhere between now and the end of 2018 there will be a moment where
OpenSSL-1.0.x will be removed from Debian and every software not adapted
will fail to compile and be subsequently removed from Debian Testing,
the next release-to-be, until it is patched or updated to compile with
the newer OpenSSL.

There is already a Bug in the Debian BTS
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850895 and Bacula
Bugtracker http://bugs.bacula.org/view.php?id=2247

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Can't run bacula any more.

[Sven Hartge]

On 12.03.2017 17:57, Richard wrote:
> Date: Sunday, March 12, 2017 17:33:40 +0100 From: "Erik P. Olsen" 
> <epod...@gmail.com>
>> On 2017-03-12 at 15:31:35 Sven Hartge wrote:

>>> First step should be to fix the database so that the director
>>> daemon starts correctly and _then_ see if this automagically fixes
>>> the problem with bconsole (I think it will).

>> Yes. The big thing is how to fix it. I have reinstall mariadb,
>> dropped the database and reran the scripts from /usr/libexec/bacula
>> to no avail. Last efford will be to remove mariadb and install
>> mysqld instead.

> I don't believe that this is a mysql/mariadb issue as they are
> basically interchangeable. 

I would really be surprised if it is. I am running Bacula on MariaDB
myself with no problems at all. (But I am using Debian, so there may be
a difference on how the RPM packages integrate the different flavors of
MySQL/MariaDB.)

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Can't run bacula any more.

[Sven Hartge]

On 12.03.2017 14:54, Richard wrote:

> Looking back through all the messages in this thread, it appears that
> you have two problems. One is that you can't connect to the director
> daemon:

> The other is your db setup/access:

Both problems will be related. He cannot connect to the director with
bconsole because the director dies because the database is not reachable
or not setup correctly.

First step should be to fix the database so that the director daemon
starts correctly and _then_ see if this automagically fixes the problem
with bconsole (I think it will).

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
--
Announcing the Oxford Dictionaries API! The API offers world-renowned
dictionary content that is easy and intuitive to access. Sign up for an
account today to start using our lexical data to power your apps and
projects. Get started today and enter our developer competition.
http://sdm.link/oxford___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bconsole can't talk to bacula-dir

[Sven Hartge]

Um 12:03 Uhr am 02.10.16 schrieb Jan Martin:

> Well, if not Debian, maybe we can interest Ubuntu in fixing the 7.0.5 
> bacula in their 16.04 distribution, since it's an LTS version.  That 
> would help those distros that inherit from Ubuntu, like Mint, maybe?

No need to do this, there is already a fixed package in proposed-updates 
for Xenial:

https://launchpad.net/ubuntu/+source/bacula/7.0.5+dfsg-4ubuntu0.1

>From the Changelog:

"d/rules: do not use -Bsymoblic-functions when linking. Closes LP: 
#1553563, LP: #1567824."

Also: Looking at the build logs from Debian, it seems that the problematic 
linker flags are specific to Ubuntu, which would explain why Debian is 
unaffected.

Grüße,
Sven.

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bconsole can't talk to bacula-dir

[Sven Hartge]

On 02.10.2016 09:08, Hankins, Jonathan wrote:

> Even though it's fixed in the 7.4.x from Ubuntu (probably in debian
> too), if it's indeed broken in debian, I'm going to ask if they can
> release an update to their 7.0.5 package in testing, so that people who
> track that, or distros that are derived from it, don't get a broken
> bacula out of the box.

Testing no longer has 7.0.5 (since 2016-06-09), so there is no need to
release any fixed package. Any other derivative distribution using 7.0.5
will have to fix their package on their own.

Grüße,
Sven.




signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bconsole can't talk to bacula-dir

[Sven Hartge]

On 01.10.2016 16:51, Hankins, Jonathan wrote:

> It seems weird that the bacula package in Debian and Ubuntu, et al, is
> broken and no one has noticed (checked Debian bug database). I know
> Debian has been on 5.x in the stable release for years (still is). It's
> possible that 7.0.5 got packaged for their testing release and maybe
> Ubuntu xenial picked it up and thus Mint 18. My guess is most folks
> using bacula on a Debian distro are on Debian stable, and not Ubuntu or
> mint (workstation oriented releases...if anything, may be using
> bacula-fd) and thus no one has noticed. I'll do a little digging and
> talk to the person who packages bacula for Debian and see if I figure it
> out.

I don't know about Bacula being broken on Debian.

I've been using Bacula at work on Debian since version 1.34 back in 2004
and had it never not work. Right now I am up to 7.4.3 on Jessie from
backports, running backups for about 250 systems.

Privately I run in Debian Unstable, backuping 10 systems to disk and
tape. Again, never experienced the problems you have.

If Bacula was unusable and broken on Debian, there would be bug reports
in the BTS.

Grüße,
Sven.



signature.asc
Description: OpenPGP digital signature
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Windows fd unable to communicate with linux sd

[Sven Hartge]

On 26.09.2016 00:09, Hodges wrote:

> Just a version problem. My linux box has version 5.2.6 (latest debian
> version apparently) and the 7.4.3 windows version does not like it. Wind
> the windows version back to 5.2.6. and it works OK.
> 
> Anyone know why the Debian stable version is stuck at 5.2.6?

Debian Stable never gets new upstream versions after release (with the
exception of some special packages). This is the Debian Release
philosophy (which is not very different from other Enterprise-Class
distributions).

But you can get a very recent version (7.4.3) of Bacula from the
backports archive.

Grüße,
Sven Hartge.




signature.asc
Description: OpenPGP digital signature
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] bacula 5.0.3 backport for debian lenny?

[Sven Hartge]

On 14.09.2010 18:02, Rory Campbell-Lange wrote:
 On 14/09/10, Ralf Gross (ralf-li...@ralfgross.de) wrote:

 Thanks, I know this version from backports, and if there is no other
 deb available, I'll give it a try.

 From http://www.bacula.org/en/?page=news (and from the mails I
 received from the bacula-bugs list) I had the feeling that 5.0.3 fixed
 some important issues.
 
 Sorry, I mis-read your intention to skip 5.0.2 (I read it as skip to).
 
 You may wish to contact the backports maintainer (rhonda at deb.at) to
 see if there is a plan to update the backport to 5.0.3. The backports
 maintaners were very helpful to me when I wished to do a custom
 packaging of 5.0.2.

I am not affiliated with backports.debian.org so I cannot speak for
them, but since there is no 5.0.3 in neither Debian unstable nor Debian
testing, the backport will not get updated to 5.0.3

You (Ralf) need to contact the maintainer of Bacula in Debian (John
Goerzen) and ask if he is willing to package 5.0.3 and willing to ask
the release managers to let this version migrate to testing.

Only after all this has happened there will be a backport of 5.0.3.

Grüße,
Sven.

--
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] IBM TS3100 autochanger

[Sven Hartge]

On 29.05.2010 05:13, masker wrote:

 I install a DELL PERC H200 SAS HBA + IBM ULTRIUM-HH5 in my DEBIAN
 system, but fail to install driver for tape drive, lin-tape (ver.
 1.38.0) . Could you  please tell me how to make it ?

A special driver should not be needed, Linux supports SCSI tapes since
the middle ages.

Grüße,
Sven.

--

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] LTO-4 Drive issues

[Sven Hartge]

On 26.05.2010 01:55, skipunk wrote:

 The nic's in the server are Broadcom's netextreme II's. I would
 assume that they would support checksum offload and large tcp packet
 offload, but I really I'm not sure.

They do support all offload options.

But those options don't boost you from 40MByte/s to 100MByte/s, they
help servers which are already very loaded and your local memory and CPU
throughput is limiting you.

If your CPU is mostly idle, then offloading won't buy you much. (At
least with 1GB NICs. With 10GB NICs this is a whole different picture.)

But beware: some Linux versions had problems with offloading, so while
benchmarking your network with netio and iperf it may be worthwhile to
toggle some offloading options to see if you get any changes in
throughput and/or CPU load.

Grüße,
Sven.

--

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] LTO-4 Drive issues

[Sven Hartge]

On 24.05.2010 22:31, skipunk wrote:

 What would it take to clear up the network bottleneck.  I was looking
 at another server that came with our gaming system. Same server
 (memory, hd, etc) and tape library, running on win2k3 and netbackup
 with no issues. The only difference is, it's running 4 nic's. So it's
 leaving me a bit baffled that the only real difference is OS and 2
 more nics and my system is experiencing a bottle neck.

You do know under Linux attaching more than one NIC to a LAN does not
increase the throughput, do you?

You have to use bonding in either 802.3ad- or ALB-mode to achieve this.
The first one uses LACP and needs a switch which is specially configured
while the last one does not need any configuration in the switch, you
can even connect both NICs to different switches, as long as the (V)LAN
you connect your server to is available on both.

Grüße,
Sven.

--

___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula SSL Support

[Sven Hartge]

On 13.02.2010 02:26, Jon Schewe wrote:
 On 02/12/2010 08:30 AM, Prashant Ramhit wrote:

 Ia there a possibility to add PKI Encryption into Bacula Encryption on 
 Ubuntu Bacula Clients.
 As it is not compiled in.

 It's there, you may need to rebuild to get it. I know that Debian (which
 Ubuntu is based on) doesn't ship bacula with SSL support due to
 licensing issues.

Since version 3.0.0-1 uploaded on 30 Apr 2009 Bacula is compiled with
SSL support in Debian. Unfortunately, the version in Debian Lenny is
without SSL support, since back then Bacula lacked the necessary
exception in its license to be linked with OpenSSL.

But you can install a SSL-enabled version 3.0 from backports.org for
Debian Lenny. Maybe you can install this version into Ubuntu.

Grüße,
Sven.

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] status storage freezes at Used Volume Status

[Sven Hartge]

Ralf Gross wrote:
 Bob Hetzel schrieb:

 My suggestion is to try upgrading your server to 3.0.2.  You won't need to 
 upgrade all your FD's.  Since I went through that, the things that used to 
 hang bacula in my environment (at exactly the same place you describe) are 
 fixed.

 3.0.2 is not yet available in debian. I just switched from self
 compiling to debian pakets last years. Hm...

The new 3.0.2 packages in Sid are easily backportable to Lenny, I expect
them on backports.org as soon as they hit Testing.

Or you could setup cowbuilder/pbuilder yourself and recompile them for
Lenny.

Grüße,
Sven.

--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users