[Bacula-users] Bacula configuration for non-amazon s3 providers.

[r0...@nxlplyx.com]

Hi,

I am trying to setup Bacula 9.6.3  to run on an ubuntu 18.04 laptop. 

The intent is to use Bacula community as my backup program to cloud,
primarily because the data are encrypted before it leaves the laptop,
and Bacula can minimize the cost.

I am using a non-amazon s3 provider: netdepot.com

s3fs works with netdepot.com, with no problems.  I copied and pasted
files into and out of the same bucket to which I am trying to connect
Bacula.

Bacula has no problem backing up to, and restoring from a directory, but
when I try to use the cloud storage pointed at netdepot.com, it cannot
make the connection.

This is the message I get:

You have messages.
*messages
23-Apr 17:29 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 3: No prior
Full backup Job record found.
23-Apr 17:29 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 3: No prior or
suitable Full backup found in catalog. Doing FULL backup.
23-Apr 17:29 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 3: Start
Backup JobId 3, Job=BackupClient1-to-Cloud.2020-04-23_17.29.45_04
23-Apr 17:29 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 3: Using
Device "dev.nd1" to write.
23-Apr 17:29 user1-Standard-PC-i440FX-PIIX-1996-fd JobId 3: Fatal error:
job.c:3013 Comm error with SD. bad response to Append Data. ERR=No data
available
*

I am pretty sure that I don't understand how to configure the dir and sd
config files properly.  

Here is the relevant part of what I have for the bacula-dir.conf file:

Job {
  Name = "BackupClient1-to-Cloud"
  JobDefs = "DefaultJob"
  Storage = nd1_storage
}


Here is what I have for the sd config file:

Device {
  Name = dev.nd1
  Device Type = Cloud
  Cloud = S3Cloud
  Archive Device = /home/user1/dirNFS/bu/bacula_cloudstorage_test
  Maximum Part Size = 1000
  Media Type = CloudType
  LabelMedia = yes;
  Random Access = Yes;
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
}

Cloud {
  Name = S3Cloud
  Driver = "S3"
  HostName = "us-central-1-s3.netdepot.com"
  BucketName = "test_bucket"
  Access Key = 
  Secret Key = 
  Protocol = HTTPS
  UriStyle = VirtualHost
  Truncate Cache = No
  Upload = EachPart
  Region = "us-central-1"
  MaximumUploadBandwidth = 5MB/s
}


Might someone lend a hand?

Al




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

[Bacula-users] S3 backup

[r0...@nxlplyx.com]

Hi,

I am trying to backup Ubuntu 18.04 on to a non-amazon S3 service,

At first I thought it was my configuration, because Bacula backs up to
and from NFS drives with no problem, and s3fs mounts a drive to the S3
service with no problem.

However I kept getting an error each time I tried.

I ran wireshark on the and machine watched for any attempt to
communicate with the S3 service.  There was none.  For some reason
Bacula is not even attempting to communicate with the S3 service.

Below are the output by bconsole, as well as ther relevant
bacula-dir.conf and bacula-sd.conf entries.

I'd sure appreciate any help on this.

Al

==

./bconsole output:

The defined Job resources are:
 1: BackupClient1
 2: BackupClient1-to-Cloud
 3: BackupCatalog
 4: RestoreFiles
Select Job resource (1-4): 2
Run Backup job
JobName:  BackupClient1-to-Cloud
Level:    Incremental
Client:   user1-Standard-PC-i440FX-PIIX-1996-fd
FileSet:  Full Set
Pool: File (From Job resource)
Storage:  dev_nd1_storage (From Job resource)
When: 2020-05-02 11:45:49
Priority: 10
OK to run? (yes/mod/no): yes
Job queued. JobId=21
You have messages.
*messages
02-May 11:45 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 21: No prior
Full backup Job record found.
02-May 11:45 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 21: No prior
or suitable Full backup found in catalog. Doing FULL backup.
02-May 11:45 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 21: Start
Backup JobId 21, Job=BackupClient1-to-Cloud.2020-05-02_11.45.53_03
02-May 11:45 user1-Standard-PC-i440FX-PIIX-1996-dir JobId 21: Using
Device "dev_nd1" to write.
02-May 11:45 user1-Standard-PC-i440FX-PIIX-1996-fd JobId 21: Fatal
error: job.c:3013 Comm error with SD. bad response to Append Data.
ERR=No data available
*

===

relevant bacula-dir.conf enties:

Storage {
    Name = dev_nd1_storage
    Address = user1-Standard-PC-i440FX-PIIX-1996
    SD Port = 9103
    Password = 
    Device = dev_nd1
    Media Type = CloudType
}


Job {
  Name = "BackupClient1-to-Cloud"
  JobDefs = "DefaultJob"
  Storage = dev_nd1_storage
  Client = user1-Standard-PC-i440FX-PIIX-1996-fd
}




relevant bacula-sd.conf entries:


Device {
  Name = dev_nd1
  Device Type = Cloud
  Cloud = S3Cloud
  Archive Device = /home/user1/dirNFS/bu/bacula_cloudstorage_test
  Maximum Part Size = 1000
  Media Type = CloudType
  LabelMedia = yes;
  Random Access = Yes;
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
}


Cloud {
  Name = S3Cloud
  Driver = "S3"
  HostName = us-central-1-s3.netdepot.com
 # HostName = netdepot.com
  BucketName = "test_bucket"
  Access Key = 
  Secret Key = 
  Protocol = HTTPS
  UriStyle = VirtualHost
  Truncate Cache = No
  Upload = EachPart
  Region = "us-central-1"
  MaximumUploadBandwidth = 5MB/s
}


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

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

[r0...@nxlplyx.com]

Hi,

I am attempting to compile Bacula 9.6.3 on Ubuntu 18.04, but am getting
the following errors.  Can anyone help out?

---

$ make

..

..

make[1]: Leaving directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/findlib'
==>Entering directory
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed
make[1]: Entering directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed'
Compiling filed.c
Compiling authenticate.c
Compiling backup.c
Compiling crypto.c
Compiling win_efs.c
Compiling estimate.c
Compiling fdcollect.c
Compiling fd_plugins.c
Compiling accurate.c
Compiling filed_conf.c
Compiling heartbeat.c
Compiling hello.c
Compiling job.c
Compiling fd_snapshot.c
Compiling restore.c
Compiling status.c
Compiling suspend.c
Compiling verify.c
Compiling verify_vol.c
Compiling bacl.c
bacl.c: In member function ‘bRC_BACL BACL::restore_acl(JCR*, int, char*,
u_int32_t)’:
bacl.c:431:15: error: ‘STREAM_BACL_AFS_TEXT’ was not declared in this scope
  case STREAM_BACL_AFS_TEXT:
   ^~~~
bacl.c:431:15: note: suggested alternative: ‘STREAM_XACL_AFS_TEXT’
  case STREAM_BACL_AFS_TEXT:
   ^~~~
   STREAM_XACL_AFS_TEXT
bacl.c: In member function ‘bRC_BACL BACL::afs_backup_acl(JCR*, FF_PKT*)’:
bacl.c:694:19: error: ‘BUFSIZE’ was not declared in this scope
    vip.out_size = BUFSIZE;
   ^~~
bacl.c:694:19: note: suggested alternative: ‘BUFSIZ’
    vip.out_size = BUFSIZE;
   ^~~
   BUFSIZ
bacl.c:705:32: error: ‘STREAM_BACL_AFS_TEXT’ was not declared in this scope
    return send_acl_stream(jcr, STREAM_BACL_AFS_TEXT);
    ^~~~
bacl.c:705:32: note: suggested alternative: ‘STREAM_XACL_AFS_TEXT’
    return send_acl_stream(jcr, STREAM_BACL_AFS_TEXT);
    ^~~~
    STREAM_XACL_AFS_TEXT
bacl.c: In member function ‘bRC_BACL BACL::afs_restore_acl(JCR*, int)’:
bacl.c:724:23: error: ‘ff_pkt’ was not declared in this scope
    if (jcr == NULL || ff_pkt == NULL){
   ^~
bacl.c:724:23: note: suggested alternative: ‘io_pkt’
    if (jcr == NULL || ff_pkt == NULL){
   ^~
   io_pkt
Makefile:177: recipe for target 'bacl.o' failed
make[1]: *** [bacl.o] Error 1
make[1]: Leaving directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed'


  == Error in
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/filed ==


Makefile:148: recipe for target 'all' failed
make: *** [all] Error 1


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

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

[r0...@nxlplyx.com]

Hi Radoslaw,

Thank you for the reply.  I disabled AFS in the configuration and
avoided the AFS variable compilation errors. 

Unfortunately, I am now getting S3 driver compilation errors.

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.

Can anyone help?

-

LT Compiling tape_dev.c
LT Compiling vtape_dev.c
Making libbacsd.la ...
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/libtool --silent
--tag=CXX --mode=link /usr/bin/g++    -o libbacsd.la \
   acquire.lo ansi_label.lo askdir.lo autochanger.lo block.lo
block_util.lo butil.lo dev.lo device.lo ebcdic.lo init_dev.lo label.lo
lock.lo match_bsr.lo mount.lo null_dev.lo os.lo parse_bsr.lo read.lo
read_records.lo record_read.lo record_util.lo record_write.lo reserve.lo
scan.lo sd_plugins.lo spool.lo tape_alert.lo tape_worm.lo vol_mgr.lo
wait.lo fifo_dev.lo file_dev.lo tape_dev.lo vtape_dev.lo \
  -export-dynamic -rpath /opt/bacula/lib -release 9.6.3
LT Compiling cloud_dev.c
LT Compiling cloud_parts.c
LT Compiling cloud_transfer_mgr.c
LT Compiling s3_driver.c
s3_driver.c: In member function 'virtual bool s3_driver::init(JCR*,
cloud_dev*, DEVRES*)':
s3_driver.c:561:10: error: 'S3BucketContext {aka struct
S3BucketContext}' has no member named 'authRegion'
    s3ctx.authRegion = cloud->region;
  ^~
Makefile:211: recipe for target 's3_driver.lo' failed
make[1]: *** [s3_driver.lo] Error 1
make[1]: Leaving directory
'/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/stored'


  == Error in
/home/user1/dirNFS/sw/bacula_9.6.3/bacula-9.6.3/src/stored ==

-


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

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

[r0...@nxlplyx.com]

Hi Sven,

I retrieved the S3 module from the link you
provided: www.bacula.org/downloads/libs3-20181010.tar.gz

However I have been unable to compile the module in Ubuntu 18.04:



$ ls
archlinux  ChangeLog  debian    GNUmakefile    GNUmakefile.osx 
INSTALL LICENSE  README  test
build  COPYING    doxyfile  GNUmakefile.mingw  inc 
libs3.spec  mswin    src TODO
$ make deb
make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

-

I have also noticed that in the 'libs3.spec' file, there exist the
following lines.  But I have installed everything remotely similar to
these, to no avail.

=

# Want to include curl dependencies, but older Fedora Core uses curl-devel,
# and newer Fedora Core uses libcurl-devel ... have to figure out how to
# handle this problem, but for now, just don't check for any curl libraries
# Buildrequires: curl-devel
Buildrequires: libxml2-devel
Buildrequires: openssl-devel
Buildrequires: make
# Requires: libcurl
Requires: libxml2
Requires: openssl

=

Does anyone have any ideas on how to make this work in Ubuntu 18.04?


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

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

[r0...@nxlplyx.com]

Hi Radoslaw,

I believe I have tried every kind of library combination, to no avail.




___
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

[r0...@nxlplyx.com]

Hi Radoslaw,

I still get the same results.  Judging by the error message, I am
guessing that it finds them, but doesn't know what to do with them
because there is no rule for them.

===

$ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb

make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

===

Thanks for the attempt to help.

Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
can give a hand?

Regards,

Al

On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
> Hello,
>
> Hi Radoslaw,
>
> I believe I have tried every kind of library combination, to no avail.
>
> Your compilation requires a following header file to be
> available: curl/curl.h
> In my development machine (Debian) it is available with the following
> package:
> # dpkg -S curl.h
> libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
>
> So, I suggested that it should be available in a similar package in
> Ubuntu (and it seems it is the exact package).
> You have to check where this header file is installed and what package
> provides it. If it does not fit then you should alter your compilation
> flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
>
> I hope it helps.
>
> Radek
> -- 
> 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] Compilation Errors of Bacula 9.6.3 on Ubuntu 18.04

[r0...@nxlplyx.com]

Hi Martin,

Thank you.  But I got the same result.

---

$ make CFLAGS=-I/usr/include/x86_64-linux-gnu  deb

make: *** No rule to make target 'curl/curl.h', needed by
'build/obj/acl.do'.  Stop.

---

and just for consistency, I ran Radoslaw's command and got the results
below:

=

$ dpkg -S curl.h
libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h

=


Well, if anyone can help I'd appreciate it.

Regards,

Al.


On 5/21/20 12:55 PM, Martin Simmons wrote:
> If you were trying to set CFLAGS to -I/usr/include/x86_64-linux-gnu then you
> must remove the space after CFLAGS=, i.e. use
>
> make CFLAGS=-I/usr/include/x86_64-linux-gnu deb
>
> __Martin
>
>
>> On Wed, 20 May 2020 20:40:23 -0400, r0002@nxlplyx com said:
>> Hi Radoslaw,
>>
>> I still get the same results.  Judging by the error message, I am
>> guessing that it finds them, but doesn't know what to do with them
>> because there is no rule for them.
>>
>> ===
>>
>> $ make CFLAGS= -I/usr/include/x86_64-linux-gnu  deb
>>
>> make: *** No rule to make target 'curl/curl.h', needed by
>> 'build/obj/acl.do'.  Stop.
>>
>> ===
>>
>> Thanks for the attempt to help.
>>
>> Has anyone actually gotten the S3 module  to work in Ubuntu 18.04 that
>> can give a hand?
>>
>> Regards,
>>
>> Al
>>
>> On 5/20/20 4:38 AM, Radosław Korzeniewski wrote:
>>> Hello,
>>>
>>> Hi Radoslaw,
>>>
>>> I believe I have tried every kind of library combination, to no avail.
>>>
>>> Your compilation requires a following header file to be
>>> available: curl/curl.h
>>> In my development machine (Debian) it is available with the following
>>> package:
>>> # dpkg -S curl.h
>>> libcurl4-openssl-dev:amd64: /usr/include/x86_64-linux-gnu/curl/curl.h
>>>
>>> So, I suggested that it should be available in a similar package in
>>> Ubuntu (and it seems it is the exact package).
>>> You have to check where this header file is installed and what package
>>> provides it. If it does not fit then you should alter your compilation
>>> flags, i.e. CFLAGS and CPPFLAGS to provide a correct header file location.
>>>
>>> I hope it helps.
>>>
>>> Radek
>>> -- 
>>> Radosław Korzeniewski
>>> rados...@korzeniewski.net 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

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

[r0...@nxlplyx.com]

Hi,

I have given up trying to get the S3 module to compile  on Ubuntu
20.04.   No suggestions have worked thus far.

I switched operating systems and am trying to compile the S3 module on
Debian 10.

The missing curl.h error disappeared I was getting in Ubuntu.

Unfortunately the following now occurs.  Does anyone have any suggestions?

---

$ 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

---

Al.







___
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.

[r0...@nxlplyx.com]

Hi Sven,

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'.

Is that what you wanted to know?

Al



>> ---
>> $ 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.)
___
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.

[r0...@nxlplyx.com]

HI Sven,

Thank you. The duplicate case statement problem was eliminated with that
patch.

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

-

Regards,

Al



On 5/31/20 4:04 AM, Sven Hartge wrote:
> 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.
>
>


___
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.

[r0...@nxlplyx.com]

Hi Sven,

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? 

-

$ 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.

-

Al

On 5/31/20 8:29 AM, Sven Hartge wrote:

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.





___
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 Debian10.

[r0...@nxlplyx.com]

Hi Sven,

The make clean did work for the S3 module.  Oddly, it tried to replace
the amazon S3 module that can be installed from synaptic.  So I removed
the amazon S3 module and replaced it with the Bacula S3 module.

However,  I tried to compile the main program 9.6.3. That is not
working so well.  I am getting a number of errors like the following. 
Can someone tell me if I am missing something?

Are there patches involved?

===

htable.c: In member function 'void htable::grow_table()':
htable.c:230:36: warning: 'void* memcpy(void*, const void*, size_t)'
writing to an object of non-trivially copyable type 'class htable'; use
copy-assignment or copy-initialization instead [-Wclass-memaccess]
    memcpy(big, this, sizeof(htable));  /* start with original class data */
    ^
In file included from ../lib/tree.h:26,
 from ../lib/lib.h:59,
 from ../bacula.h:169,
 from htable.c:42:
../lib/htable.h:77:7: note: 'class htable' declared here
 class htable : public SMARTALLOC {
   ^~

==

Al

> Please do a 
>
>  make VERBOSE=1 clean
>
> and then retry with 
>
>  make VERBOSE=1 deb
>
> Grüße,
> Sven.
>
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Fwd: Compilation Errors of Bacula 9.6.3 on Debian10.

[r0...@nxlplyx.com]

I tried to compile the main program 9.6.3. That is not
working so well.  I am getting a number of errors like the following. 
Can someone tell me if I am missing something?

Are there patches involved?

Can anyone help?

===

htable.c: In member function 'void htable::grow_table()':
htable.c:230:36: warning: 'void* memcpy(void*, const void*, size_t)'
writing to an object of non-trivially copyable type 'class htable'; use
copy-assignment or copy-initialization instead [-Wclass-memaccess]
    memcpy(big, this, sizeof(htable));  /* start with original class data */
    ^
In file included from ../lib/tree.h:26,
 from ../lib/lib.h:59,
 from ../bacula.h:169,
 from htable.c:42:
../lib/htable.h:77:7: note: 'class htable' declared here
 class htable : public SMARTALLOC {
   ^~

==

Al

> Please do a 
>
>  make VERBOSE=1 clean
>
> and then retry with 
>
>  make VERBOSE=1 deb
>
> Grüße,
> Sven.
>

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

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

[Bacula-users] Bacula 9.6.5 compilation: How to set the value of PREFIX = /opt/bacula ?

[r0...@nxlplyx.com]

This is a noob question.

I believe, the ./configure script uses the PREFIX value to set the
installation directory.

I am concerned that I may set PREFIX as a system-wide setting that is
used by other computer programs I try to compile.

Can anyone tell me how and where, in the Bacula 9.6.5 compilation
system, can I set the value of PREFX = /opt/bacula , so that it only
affects the Bacula 9.6.5 compilation?

Regards,

Al.


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

Re: [Bacula-users] Bacula 9.6.5 compilation: How to set the value of PREFIX = /opt/bacula ?

[r0...@nxlplyx.com]

Ah, so that's how it works.

Some of the website postings said to look for '.pro' files, etc. I was
getting lost.

Thank you Gary.

Al

On 6/13/20 8:40 AM, Gary R. Schmidt wrote:
> On 13/06/2020 22:26, r0...@nxlplyx.com wrote:
>> This is a noob question.
>>
>> I believe, the ./configure script uses the PREFIX value to set the
>> installation directory.
>>
>> I am concerned that I may set PREFIX as a system-wide setting that is
>> used by other computer programs I try to compile.
>>
>> Can anyone tell me how and where, in the Bacula 9.6.5 compilation
>> system, can I set the value of PREFX = /opt/bacula , so that it only
>> affects the Bacula 9.6.5 compilation?
>>
> ./configure --prefix=/opt/bacula
>
> The "--prefix" flag is a default autoconf/automake option.
>
> Cheers,
>     Gary    B-)
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users


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

Re: [Bacula-users] Bacula 9.6.5 compilation: How to set the value of PREFIX = /opt/bacula ?

[r0...@nxlplyx.com]

I spoke too soon. 

This is a Debian 10 install with postgres.

I compiled and installed the S3 module with no errors or warnings.

But the main Bacula 9.6.5 program was different:

It configured with no errors or warnings.

It compiled with no errors or warnings.

However, even with the modified configure with --prefix=/opt/bacula ,
'make install'  installed stuff elsewhere.

What's worse, after the installation, I get a flurry of  "cannot open
mtab" error windows that pop up.

My configure file is:

CFLAGS="-g -O2 -Wall" \
./configure --prefix=/opt/bacula \
--sbindir=${PREFIX}/bin \
--sysconfdir=${PREFIX}/etc \
--docdir=${PREFIX}/html \
--htmldir=${PREFIX}/html \
--with-working-dir=${PREFIX}/working \
--with-pid-dir=${PREFIX}/working \
--with-scriptdir=${PREFIX}/scripts \
--with-plugindir=${PREFIX}/plugins \
--libdir=${PREFIX}/lib \
--enable-smartalloc \
--enable-conio \
--disable-bat \
--with-postgresql \
--with-dump-email=user1@localhost \
--with-job-email=user1@localhost \
--with-smtp-host=mail.localhost \
--with-baseport=9101 \
--with-openssl

Can anyone tell me what I am doing wrong?

Al

On 6/13/20 12:55 PM, r0...@nxlplyx.com wrote:
> Ah, so that's how it works.
>
> Some of the website postings said to look for '.pro' files, etc. I was
> getting lost.
>
> Thank you Gary.
>
> Al
>
> On 6/13/20 8:40 AM, Gary R. Schmidt wrote:
>> On 13/06/2020 22:26, r0...@nxlplyx.com wrote:
>>> This is a noob question.
>>>
>>> I believe, the ./configure script uses the PREFIX value to set the
>>> installation directory.
>>>
>>> I am concerned that I may set PREFIX as a system-wide setting that is
>>> used by other computer programs I try to compile.
>>>
>>> Can anyone tell me how and where, in the Bacula 9.6.5 compilation
>>> system, can I set the value of PREFX = /opt/bacula , so that it only
>>> affects the Bacula 9.6.5 compilation?
>>>
>> ./configure --prefix=/opt/bacula
>>
>> The "--prefix" flag is a default autoconf/automake option.
>>
>> Cheers,
>>     Gary    B-)
>>
>>
>> ___
>> Bacula-users mailing list
>> Bacula-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users


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

Re: [Bacula-users] Bacula 9.6.5 compilation: How to set the value of PREFIX = /opt/bacula ?

[r0...@nxlplyx.com]

Hi Gary,

It almost worked.  

It seems to have dumped all the scripts into the /opt/bacula/etc  directory.

Al



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

Re: [Bacula-users] Bacula 9.6.5 compilation: How to set the value of PREFIX = /opt/bacula ?

[r0...@nxlplyx.com]

Hi Phil,

> If you don't want that and want them in system /etc, you could add
> --sysconfdir=/etc or --sysconfdir=/etc/bacula.
>
I am trying to get everything installed into the appropriate
/opt/bacula/ (etc, bin, sbin, scripts,..)

However, the suggested configure file below dumped EVERYTHING into the
/opt/bacula/etc directory on a 'make install'.

Nor did it configure the postgres database. I will likely have to do
that manually after I figure out how to get this thing to 'make install' .

./configure CFLAGS="-g -O2 -Wall" \
--prefix=/opt/bacula \
--enable-smartalloc \
--enable-conio \
--disable-bat \
--with-postgresql \
--with-dump-email=user1@localhost \
--with-job-email=user1@localhost \
--with-smtp-host=mail.localhost \
--with-openssl

Any help would be greatly appreciated.

Al



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

[Bacula-users] 9.6.5 compiles on Debian 10, but does not run

[r0...@nxlplyx.com]

Thank you everyone for helping me get Bacula 9.6.5 to compile without
error or warning on Debian 10.

It has been a many-week long game of "whack-a-mole", starting with
version 9.6.3 on Ubuntu, struggling with the S3 module, then
reinstalling my system with Debian 10 to make it work and it not
compiling without errors or warnings, then moving to Bacula 9.6.5 and
finally getting Bacula to compile without error on Debian 10.   In the
process I had the ./configure file incorrect, so I kept wiping out my
O/S with 'make install', and had to reinstall the O/S several times.  

NOTE:  I discovered the scripts directory that was in 9.6.3 is no longer
in 9.6.5, and all the scripts in 9.6.5 get put into the etc directory. 
At least that is what happened when I deleted the entire /opt/bacula
directory and re-ran 'make install'.

But now that Bacula 9.6.5 compiled without errors, it will not run. 
Note: 9.6.3 ran right out of 'make install' with postgres, but no S3
capability.

./bconsole tries to connect to the director on port 9101.   But it hangs
for a while, and the director daemon process then dies.

I ran the scripts to create the postgres directory, tables and set
permissions.  But no configuration of director, with or without
passwords for the postgres account, will make it work.  Even with the
identical setup that did work with Bacula 9.6.3.

I tried configuring the director with what the manual says on page 399,
and that does not work.

Can anyone help?

The log says:

==

20-Jun 00:05 bacula-dir JobId 0: Fatal error: Could not open Catalog
"MyCatalog", database "bacula".
20-Jun 00:05 bacula-dir JobId 0: Fatal error: postgresql.c:332 Unable to
connect to PostgreSQL server. Database=bacula User=bacula
Possible causes: SQL server not running; password incorrect;
max_connections exceeded.
20-Jun 00:05 bacula-dir ERROR TERMINATION
Please correct configuration file: /opt/bacula/etc/bacula-dir.conf

==


Al


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

Re: [Bacula-users] 9.6.5 compiles on Debian 10, but does not run

[r0...@nxlplyx.com]

Hi Rad,

It did not work.  The only thing that occurs to me is what user should I
be launching things as?


Logging into Postgres from command line.

1. /etc$ psql -h 127.0.0.1 -U bacula -W bacula
Password:
psql (12.3 (Debian 12.3-1.pgdg100+1))
SSL connection (protocol: TLSv1.3, cipher: TLS_AES_256_GCM_SHA384, bits:
256, compression: off)
Type "help" for help.

bacula=> \q
could not save history to file "/opt/bacula/.psql_history": No such file
or directory
/etc$

2. Testing all four of the configuration files with a script:
"/opt/bacula/sbin/bacula-dir -t -c /opt/bacula/etc/bacula-dir.conf"...

/etc$ ./test_conf
=
Testing bacula-dir.conf
=
Testing bacula-fd.conf
=
Testing bacula-sd.conf
=
Testing bconsole.conf
=

(no output from any of them)


3. Starting Bacula

bacula@debian:~/etc$ ./bacula start
Starting the Bacula Storage daemon
Starting the Bacula File daemon
Starting the Bacula Director daemon

4. Launching bconsole

bacula@debian:~/etc$ ./bconsole
Connecting to Director debian:9101
bacula@debian:~/etc$

5. bacula-dir process is now dead.


6. bacula.log



23-Jun 15:11 bacula-dir JobId 0: Fatal error: Could not open Catalog
"MyCatalog", database "bacula".
23-Jun 15:11 bacula-dir JobId 0: Fatal error: postgresql.c:332 Unable to
connect to PostgreSQL server. Database=bacula User=bacula
Possible causes: SQL server not running; password incorrect;
max_connections exceeded.
23-Jun 15:11 bacula-dir ERROR TERMINATION
Please correct configuration file: /opt/bacula/etc/bacula-dir.conf

---



Al

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

Re: [Bacula-users] 9.6.5 compiles on Debian 10, but does not run

[r0...@nxlplyx.com]

Hi Rad,

Apparently Bacula does not like localhost, changing it to 127.0.0.1 worked.

THANK YOU!!!

Just so I get it right as to which user should I be (regular user,
bacula, postgres, or root):

  * To run the create_bacula_database script?
  * To run the make_bacula_tables script?
  * To run the grant_bacula_privileges?
  * To run the ./bconsole start script?

(Some of these seem simple, but I had gone as far as to make the bacula
user the postgres administrator to get it to work.)

- Al


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

[Bacula-users] Bacula 9.6.5, Debian 10, how to determine if encyrption is working?

[r0...@nxlplyx.com]

Hi everyone,

I am having difficulty determining if the backup volume is encrypted.

Using a hex editor, or any editor, I see the file names of the files
that were backed up in plaintext in the backup volume.

I am not a cryptographer, and so I cannot determine if the rest of the
backup volume binary is encrypted or not. (I tend to think not because I
can see plaintext file names.)

Can someone tell me how to determine if the backup volume is encrypted?

- Al
==
relevant part of  bacula-fd.conf file: (the key files were generated per
the manual, exist and no errors were given)

FileDaemon {  # this is me
  Name = debian-fd
  FDport = 9102  # where we listen for the director
  WorkingDirectory = /opt/bacula/working
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 20
  Plugin Directory = /opt/bacula/lib
 
  PKI Signatures = Yes  # Enable Data
  PKI Encryption = Yes  # Enable Data
  PKI Keypair = "/opt/bacula/etc/e156-bac963-fd.pem"    # Public
and Private Keys
  PKI Master Key = "/opt/bacula/etc/e156-bac963-master.cert"    # ONLY
the Public Key
  PkiCipher = AES256   
}



Backup report:
Build OS:   x86_64-pc-linux-gnu debian 10.4
  JobId:  1
  Job:    BackupClient1.2020-06-25_15.49.18_03
  Backup Level:   Full (upgraded from Incremental)
  Client: "debian-fd" 9.6.5 (11Jun20)
x86_64-pc-linux-gnu,debian,10.4
  FileSet:    "Full Set" 2020-06-25 15:49:18
  Pool:   "File" (From Job resource)
  Catalog:    "MyCatalog" (From Client resource)
  Storage:    "File1" (From Job resource)
  Scheduled time: 25-Jun-2020 15:49:16
  Start time: 25-Jun-2020 15:49:20
  End time:   25-Jun-2020 15:49:24
  Elapsed time:   4 secs
  Priority:   10
  FD Files Written:   29
  SD Files Written:   29
  FD Bytes Written:   394,637,072 (394.6 MB)
  SD Bytes Written:   394,657,841 (394.6 MB)
  Rate:   98659.3 KB/s
  Software Compression:   None
  Comm Line Compression:  None
  Snapshot/VSS:   no
  Encryption: yes
  Accurate:   no
  Volume name(s): Vol-0001
  Volume Session Id:  1
  Volume Session Time:    1593114524
  Last Volume Bytes:  394,952,849 (394.9 MB)
  Non-fatal FD errors:    0
  SD Errors:  0
  FD termination status:  OK
  SD termination status:  OK
  Termination:    Backup OK



Compile config:

   Large file support:    yes
   Bacula conio support:  yes -ltinfo
   readline support:  no
   TCP Wrappers support:  no
   TLS support:   yes
   Encryption support:    yes
   ZLIB support:  yes
   LZO support:   yes
   S3 support:    yes
   enable-smartalloc: yes
   enable-lockmgr:    no
   bat support:   no
   client-only:   no
   build-dird:    yes
   build-stored:  yes
   Plugin support:    yes
   AFS support:   no
   ACL support:   yes
   XATTR support: yes
   systemd support:   no
   Batch insert enabled:  PostgreSQL

   Plugins:
   - Docker:  no

===

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

[Bacula-users] file: bacula-sd-cloud-driver-9.6.5.so ?

[r0...@nxlplyx.com]

Hi,

I tried to backup to an S3 provider with a shiny new 9.6.5 compilation
on Debian 10, but I got this message:

===

25-Jun 16:36 debian-sd JobId 2: Fatal error: init_dev.c:462 [SF0020]
dlopen of SD driver=cloud at
/opt/bacula/lib/bacula-sd-cloud-driver-9.6.5.so failed:
ERR=/opt/bacula/lib/bacula-sd-cloud-driver-9.6.5.so: cannot open shared
object file: No such file or directory.

===

I compiled the S3 library distribution, I did not get any errors. 

I searched the distribution and build directories, but nothing
resembling this was there.

Where did I go wrong?

- Al


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

Re: [Bacula-users] file: bacula-sd-cloud-driver-9.6.5.so ?

[r0...@nxlplyx.com]

bacula-sd-cloud-driver-9.6.5.so 
is no where to be found on the entire system.  I put several searchers
on it starting at "/", all turned up nothing.

I recompiled and reinstalled it.  Still no 
bacula-sd-cloud-driver-9.6.5.so . 

It is no where to be found.

Does anyone have any ideas?

- Al

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

[Bacula-users] S3 Configuration for Bacula 9.6.5 on Debian 10

[r0...@nxlplyx.com]

I have compiled Bacula 9.6.5 on Debian 10, with a lot of help from the
folks here.

Now I cannot get S3 to work, probably my own lack of knowledge.

I can back up and restore to local directories, that is no problem.

However I am unable to get th S3 module to backup to an S3 server.  I
can use Fuse S3 to mount the S3 storage and move files back and forth.

===

>From ./bconsole

The defined Storage resources are:
 1: storage_dev_S3_nd1
 2: File1
 3: File2
Select Storage resource (1-3): 1
Connecting to Storage daemon storage_dev_S3_nd1 at debian:9103 ...

(hangs and no log is produced)

I can't figure out what else to do. Can anyone help?

=

bacula_sd.conf

Device {
  Name = dev_S3_nd1
  Device Type = Cloud
  Cloud = S3Cloud
  Archive Device = /home/user1/dirNFS/bu/bacula_cloudstorage_test
  Maximum Part Size = 1000
  Media Type = CloudType
  LabelMedia = yes;
  Random Access = Yes;
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
}


Cloud {
  Name = S3Cloud
  Driver = "S3"
  HostName = 
  Secret Key = 
  Protocol = HTTPS
  UriStyle = VirtualHost
  Truncate Cache = No
  Upload = EachPart
  Region = "us-central-1"
  MaximumUploadBandwidth = 5MB/s
}

==

bacula_dir.conf

Storage {
    Name = storage_dev_S3_nd1
    Address = debian
    SD Port = 9103
    Password = 
    Device = dev_S3_nd1
    Media Type = CloudType
}


Job {
  Name = "BackupClient1-to-Cloud"
  JobDefs = "DefaultJob"
  Storage = storage_dev_S3_nd1
  Client = debian-fd
}

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

Re: [Bacula-users] S3 Configuration for Bacula 9.6.5 on Debian 10

[r0...@nxlplyx.com]

Thanks sruckh,  But still no luck getting S3 to work.  The configure
files flag no errors when tested.

I have wireshark on the connection, Bacula is not even trying to get to
the network.  A ping to the S3 provider shows it can connect if it
wants.  I can even fuse S3 mount the S3 bucket and move files back and
forth with the service.

Below is what I tried  to run.  The bacula.log file, though created, had 0B.

Can anyone tell me what I am missing.

#===
*status dev:

==

Device Cloud: "dev_S3_nd1"
(/home/user1/dirNFS/bu/bacula_cloudstorage_test) is not open.
   Available Cache Space=1.071 TB
==

*run all
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
Job "all" not found
The defined Job resources are:
 1: BackupClient1
 2: BackupCatalog
 3: RestoreFiles
 4: BackupClient1-to-Cloud
Select Job resource (1-4): 4
Run Backup job
JobName:  BackupClient1-to-Cloud
Level:    Incremental
Client:   debian-fd
FileSet:  Full Set
Pool: File (From Job resource)
Storage:  dev_S3_nd1 (From Job resource)
When: 2020-07-04 08:16:45
Priority: 10
OK to run? (yes/mod/no): yes
Job queued. JobId=11
You have messages.
*messages
04-Jul 08:16 debian-dir JobId 11: No prior Full backup Job record found.
04-Jul 08:16 debian-dir JobId 11: No prior or suitable Full backup found
in catalog. Doing FULL backup.
04-Jul 08:16 debian-dir JobId 11: Start Backup JobId 11,
Job=BackupClient1-to-Cloud.2020-07-04_08.16.48_03
04-Jul 08:16 debian-dir JobId 11: Using Device "dev_S3_nd1" to write.
04-Jul 08:16 debian-fd JobId 11: Fatal error: job.c:3008 Comm error with
SD. bad response to Append Data. ERR=No data available


#===
bacula-fd.conf:

FileDaemon {  # this is me
  Name = debian-fd
  FDport = 9102  # where we listen for the director
  WorkingDirectory = /opt/bacula/working
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 20
  Plugin Directory = /opt/bacula/lib
  PKI Signatures = Yes  # Enable Data
  PKI Encryption = Yes  # Enable Data
  PKI Keypair = "/opt/bacula/etc/e156-bac963-fd.pem"    # Public
and Private Keys
  PKI Master Key = "/opt/bacula/etc/e156-bac963-master.cert"    # ONLY
the Public Key
  PkiCipher = AES256   
}

#===

bacula-dir.conf:

Job {
  Name = "BackupClient1-to-Cloud"
  JobDefs = "DefaultJob"
  Storage = dev_S3_nd1
  Client = debian-fd
}

Autochanger{
    Name = dev_S3_nd1
    Address = debian
    SDPort = 9103
    Password = 
    Device = dev_S3_nd1
    Media Type = CloudType
    Autochanger = dev_S3_nd1   
    Maximum Concurrent Jobs = 10
}

Pool{
    Name = dev_S3_nd1_pool
    Pool Type = Backup
    Recycle = yes
    AutoPrune = yes
    Volume Retention = 365 days
    Maximum Volume Bytes = 268435456
    Maximum Volumes = 8192
    Storage = dev_S3_nd1
    CacheRetention = 30 days
    LabelFormat = "S3_nd1_Vol-"
}

#===

bacula-sd.conf:


Device {
  Name = dev_S3_nd1
  Device Type = Cloud
  Cloud = S3Cloud
  Archive Device = /home/user1/dirNFS/bu/bacula_cloudstorage_test
  Maximum Part Size = 1000
  Media Type = CloudType
  LabelMedia = yes;
  Random Access = Yes;
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
}


Cloud {
  Name = S3Cloud
  Driver = "S3"
  HostName = 
  BucketName = "test_bucket"
  Access Key = 
  Secret Key = 
  Protocol = HTTPS
  Truncate Cache = No
  Upload = EachPart
  Region = "us-central-1"
 }



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

Re: [Bacula-users] S3 Configuration for Bacula 9.6.5 on Debian 10

[r0...@nxlplyx.com]

Atill no luck getting S3 to work.  The configure files flag no errors
when tested.

I have wireshark on the connection, Bacula is not even trying to get to
the network.  A ping to the S3 provider shows it can connect if it
wants.  I can even fuse S3 mount the S3 bucket and move files back and
forth with the service.

Below is what I tried  to run.  The bacula.log file, though created, had 0B.

Can anyone tell me what I am missing?

#===
*status dev:

==

Device Cloud: "dev_S3_nd1"
(/home/user1/dirNFS/bu/bacula_cloudstorage_test) is not open.
   Available Cache Space=1.071 TB
==

*run all
Automatically selected Catalog: MyCatalog
Using Catalog "MyCatalog"
Job "all" not found
The defined Job resources are:
 1: BackupClient1
 2: BackupCatalog
 3: RestoreFiles
 4: BackupClient1-to-Cloud
Select Job resource (1-4): 4
Run Backup job
JobName:  BackupClient1-to-Cloud
Level:    Incremental
Client:   debian-fd
FileSet:  Full Set
Pool: File (From Job resource)
Storage:  dev_S3_nd1 (From Job resource)
When: 2020-07-04 08:16:45
Priority: 10
OK to run? (yes/mod/no): yes
Job queued. JobId=11
You have messages.
*messages
04-Jul 08:16 debian-dir JobId 11: No prior Full backup Job record found.
04-Jul 08:16 debian-dir JobId 11: No prior or suitable Full backup found
in catalog. Doing FULL backup.
04-Jul 08:16 debian-dir JobId 11: Start Backup JobId 11,
Job=BackupClient1-to-Cloud.2020-07-04_08.16.48_03
04-Jul 08:16 debian-dir JobId 11: Using Device "dev_S3_nd1" to write.
04-Jul 08:16 debian-fd JobId 11: Fatal error: job.c:3008 Comm error with
SD. bad response to Append Data. ERR=No data available


#===
bacula-fd.conf:

FileDaemon {  # this is me
  Name = debian-fd
  FDport = 9102  # where we listen for the director
  WorkingDirectory = /opt/bacula/working
  Pid Directory = /var/run
  Maximum Concurrent Jobs = 20
  Plugin Directory = /opt/bacula/lib
  PKI Signatures = Yes  # Enable Data
  PKI Encryption = Yes  # Enable Data
  PKI Keypair = "/opt/bacula/etc/e156-bac963-fd.pem"    # Public
and Private Keys
  PKI Master Key = "/opt/bacula/etc/e156-bac963-master.cert"    # ONLY
the Public Key
  PkiCipher = AES256   
}

#===

bacula-dir.conf:

Job {
  Name = "BackupClient1-to-Cloud"
  JobDefs = "DefaultJob"
  Storage = dev_S3_nd1
  Client = debian-fd
}

Autochanger{
    Name = dev_S3_nd1
    Address = debian
    SDPort = 9103
    Password = 
    Device = dev_S3_nd1
    Media Type = CloudType
    Autochanger = dev_S3_nd1   
    Maximum Concurrent Jobs = 10
}

Pool{
    Name = dev_S3_nd1_pool
    Pool Type = Backup
    Recycle = yes
    AutoPrune = yes
    Volume Retention = 365 days
    Maximum Volume Bytes = 268435456
    Maximum Volumes = 8192
    Storage = dev_S3_nd1
    CacheRetention = 30 days
    LabelFormat = "S3_nd1_Vol-"
}

#===

bacula-sd.conf:


Device {
  Name = dev_S3_nd1
  Device Type = Cloud
  Cloud = S3Cloud
  Archive Device = /home/user1/dirNFS/bu/bacula_cloudstorage_test
  Maximum Part Size = 1000
  Media Type = CloudType
  LabelMedia = yes;
  Random Access = Yes;
  AutomaticMount = yes
  RemovableMedia = no
  AlwaysOpen = no
}


Cloud {
  Name = S3Cloud
  Driver = "S3"
  HostName = 
  BucketName = "test_bucket"
  Access Key = 
  Secret Key = 
  Protocol = HTTPS
  Truncate Cache = No
  Upload = EachPart
  Region = "us-central-1"
 }


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

[Bacula-users] Bacula backup to S3 (help)

[r0...@nxlplyx.com]

Hi everyone.

I have been trying for six months to the day, to get bacula to backup to
an S3 storage.

I have tried compiling various versions, on various operating systems,
to no avail.  The results are always the same.  I can backup and restore
from a local disk, but cannot backup to an S3 service.

I can mount the S3 storage drive with s3fs, and copy to, copy from and
delete from it.

This last round I downloaded the .deb files for 9.6.6.1 and installed
them on a clean debian 10 install.  Same results.

If anyone can help, I would sure appreciate it.

Here are the results of starting bacula-sd with -d200 on:

=

Starting the Bacula Storage daemon
root@debian:/opt/bacula/scripts# bacula-sd: address_conf.c:274-0
Initaddr 0.0.0.0:9103
debian-sd: jcr.c:131-0 read_last_jobs seek to 192
debian-sd: jcr.c:138-0 Read num_items=2
debian-sd: plugins.c:97-0 load_plugins
debian-sd: plugins.c:133-0 Rejected plugin: want=-sd.so
name=bacula-sd-cloud-driver-9.6.6.so len=31
debian-sd: plugins.c:133-0 Rejected plugin: want=-sd.so
name=bacula-sd-aligned-driver-9.6.6.so len=33
debian-sd: plugins.c:133-0 Rejected plugin: want=-sd.so name=bpipe-fd.so
len=11
debian-sd: plugins.c:121-0 Failed to find any plugins in /opt/bacula/plugins
=

Here is what is in the plugin directory:

=

# pwd
/opt/bacula/plugins
# ls -al
total 644
drwxr-xr-x  2 root root   4096 Nov 26 14:07 .
drwxr-xr-x 10 root root   4096 Nov 26 14:05 ..
-rw-r--r--  1 root root  60112 Oct  7 06:43
bacula-sd-aligned-driver-9.6.6.so
-rw-r--r--  1 root root 524440 Oct  7 06:38 bacula-sd-cloud-driver-9.6.6.so
-rw-r--r--  1 root root  58096 Oct  7 06:42 bpipe-fd.so
=

Regards,

Al

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

Re: [Bacula-users] Offsite S3 backup

[r0...@nxlplyx.com]

Hi Satvinder,

I have tried for over 6 months to get an S3 bucket working, with
multiple operating  systems, multiple versions of bacula community
edition, all to no avail.

I have scoured the docs for help, or just a set of conf file entries
that will work.  The one how-to that purports to work is with bacula
enterprise edition which jumps to the enterprise edition GUI screen
instead of showing the actual conf file entries.

Bacula seems to work fine with attached devices, such as disks, and nfs
mounted disks.

Regards

Al


On 12/17/20 12:42 PM, Satvinder Singh wrote:
> Hi,
>
> Has anyone tested doing offsite backups to an S3 bucket? If yes, can someone 
> point me in the right direction on how to?
>
> Thanks
>
>  
>
>
> Satvinder Singh / Operations Manager
> ssi...@celerium.com / Cell: 703-989-8030
>
> Celerium
> Office: 703-418-6315
> www.celerium.com 
>
>       
>  
>
>
> Disclaimer: This message is intended only for the use of the individual or 
> entity to which it is addressed and may contain information which is 
> privileged, confidential, proprietary, or exempt from disclosure under 
> applicable law. If you are not the intended recipient or the person 
> responsible for delivering the message to the intended recipient, you are 
> strictly prohibited from disclosing, distributing, copying, or in any way 
> using this message. If you have received this communication in error, please 
> notify the sender and destroy and delete any copies you may have received.
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[r0...@nxlplyx.com]

Hi Struckh,

I have tried for weeks to get the S3 module to work on the Community
edition of Bacula, to no avail.

Are you working with the community edition, or the paid edition?

Regards,

Al

On 5/2/21 1:17 PM, sruckh--- via Bacula-users wrote:
>
> On 2021-04-30 09:23, Heitor Faria wrote:
>
>> Hello,
>>
>> If you read the email thread, I was not asking for technical
>> help. I was simply asking if anyone has had success with the S3
>> plugin. With the lack of responses, I can only assume nobody has
>> got it working.
>>
>> Of course. After less than 20 hours from the original post that was
>> the only possible assumption. I guess everyone have to, voluntarily
>> and promptly, provide the answers that you need.
>>
>> Which means the plugin does not work, so it should be removed
>> from the repo.
>>
>> I personally know at least 10 administrators that use the CBacula
>> 9/11 version Cloud driver in different sectors. It also works in one
>> of my lab machines:
>  
> I am running bacula 9.6.7 on CentOS 7 where the packages came
> from https://bacula.org/packages/x/rpms/9.6.7/el7/x86_64/
>  . 
> In my case the S3 drivers seemed to stop working after 9.6.5 (if I
> remember correctly.  It was a couple of versions ago when it stopped
> working).
>  
> With the current packages, bacula-mysql-9.6.7-1.el7.x86_64,
> bacula-aligned-9.6.7-1.el7.x86_64,
> bacula-cloud-storage-9.6.7-1.el7.x86_64, and
> bacula-libs-9.6.7-1.el7.x86_64, the S3LIB files (discussed in this
> thread earlier) are provided by package bacula-cloud-storage. The
> libs3.so.4 file gets installed in /opt/bacula/lib64/.  The problem
> being that if you do a ldd on
> /opt/bacula/plugins/bacula-sd-cloud-driver-9.6.7.so it shows it uses,
> libs3.so.4, but that it is missing.  So I tried to create the file
> /etc/ld.so.conf.d/bacula.conf and added /opt/bacula/lib64 path to the
> file and ran ldconfig to rebuild the cache.  By doing this, running
> ldd on bacula-sd-cloud-driver-9.6.7.so now shows libs3.so.4 coming
> from /opt/bacula/lib64.
>  
> Unfortunately, even with this change, a configuration that used to
> work fine in older versions of bacula, no longer work in the current
> version installed.  The S3 drivers seems to load, but I ultimately end
> up with this error:  3999 Error with the upload:
> ERR=RequestTorrentOfBucketError .
>  
> On a hunch, I went ahead and built an RPM package from the link
> provided earlier in the thread for the libs3 library.  I went ahead
> and installed this RPM after building it and the libs3.so.4 file is
> now in /usr/lib/ .  I went ahead and removed the
> /etc/ld.so.conf.d/bacula.conf, and again rebuilt the cache with
> ldconfig.  Now when running ldd on bacula-sd-cloud-driver-9.6.7.so the
> libs3.so.4 now shows to be coming from /usr/lib/ .
>  
> Unfortunately, I get the same error as before.  This time, I just went
> into bconsole, and tried to use the cloud command to upload the
> volume.  After a few minutes the bconsole command times out with the
> exact error mentioned above that is received when trying to perform a
> backup.
>  
> This exact configuration used to work going straight to S3 cloud
> bucket, and also when using minio as a middle-man to go to Backblaze
> storage before they supported native S3 commands.
>  
> So, in my experience, the S3 cloud plugin has not worked for me after
> something changed from an older version.
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2

[r0...@nxlplyx.com]

Hi Reiner,

I believe what you are sensing is the frustration of wasting many hours
attempting to install the community version of the S3 driver, only to
find that it does not work.

This aggravation is compounded by suggestions made in this forum
regarding the S3 driver, without indication that they are only
applicable to the paid version of the software - the only version of the
S3 driver that is rumored to work.

Perhaps clear documentation on the community version of the S3 driver
stating that it does not work would:

1.  Prevent the wasting of people's time trying to install inoperative
software?

2.  Result in sales of the commercial version - if the S3 driver is the
purchase reason?

3.  Draw open source developers to effectively reinvent the wheel, that
is the S3 driver that is rumored to already work in the paid version of
the software?

Al


On 5/5/21 5:12 AM, Reiner Jung via Bacula-users wrote:
> Do you think shouting around here will help anybody? When there is a
> problem, I am sure someone will pick it up. When you don’t want wait
> or you want get nearly real time support, then you still have the
> option to use Bacula enterprise. 
>
> I assume you are a good software developer, are you? Then you are free
> to fork the project and create your own new project or debug and fix
> the problem.  
>
> You are talking about the community wasting time. I am sure you are
> not an Open Source developer and you maybe never contributed to any
> Open Source project … 
>
> Regards
> Reiner
>
>> Am 05.05.2021 um 03:55 schrieb Jim Joyce > >:
>>
>> As you can see, nobody except imaginary super admins have been able
>> to load the S3 plug-in. IT DOES NOT WORK. I implore the community to
>> demand the code & package be rescinded from the repo until somebody
>> with magical coding prowess can get it to work. Community users are
>> wasting their time and energy on something that will not work unless
>> you fork the darn thing and start all over again!
>>
>> bacula.org  package versions you are trying to
>> install.
>>  9.6.7 debs
>> libs3 version and installation commands
>>     cd libs3-20200523
>>     make deb
>>     cd build/pkg
>>     dpkg -i libs3_4.1.bac_amd64.deb
>>     root@backup:~/libs3-20200523/build/pkg# apt show libs3
>>    Package: libs3
>>    Version: 4.1.bac
>>    Status: install ok installed
>> operating system exact version
>>    cat /etc/debian_version 
>>    10.9
>> bacula-sd -d 200 loading  debug output
>> root@backup:/opt/bacula/bin# ./bacula-sd -d 200
>> root@backup:/opt/bacula/bin# bacula-sd: address_conf.c:274-0 Initaddr
>> 0.0.0.0:9103
>> backup-sd: jcr.c:131-0 read_last_jobs seek to 192
>> backup-sd: jcr.c:138-0 Read num_items=2
>> backup-sd: plugins.c:97-0 load_plugins
>> backup-sd: plugins.c:133-0 Rejected plugin: want=-sd.so
>> name=bpipe-fd.so len=11
>> backup-sd: plugins.c:133-0 Rejected plugin: want=-sd.so
>> name=bacula-sd-cloud-driver-9.6.7.so len=31
>> backup-sd: plugins.c:121-0 Failed to find any plugins in
>> /opt/bacula/plugins
>> ...
>> root@backup:/opt/bacula/plugins# ls
>> bacula-sd-cloud-driver-9.6.7.so  bpipe-fd.so
>>
>> steps to reproduce the error.
>> Install 9.6.7, install S3 lib hack, define a storage device using the
>> S3 driver in bacula-sd.conf. Volia! Get the dreaded "driver not
>> loaded" error.
>>
>>
>> 
>> *From:* Heitor Faria mailto:hei...@bacula.com.br>>
>> *Sent:* Monday, May 3, 2021 7:09 PM
>> *To:* sruckh mailto:sru...@gemneye.org>>
>> *Cc:* bacula-users > >
>> *Subject:* Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2
>>  
>>
>> Despite of the not-working testimonials in this thread, until
>> now I see no related bug reports in the Bacula bug
>> tracker: https://bugs.bacula.org/view_all_bug_page.php
>> 
>> IMHO it would be of great help if you could make the bug
>> reports with the maximum details, such as:
>>  
>> - bacula.org  package versions you are
>> trying to install.
>> - libs3 version and installation commands
>> - operating system exact version
>> - bacula-sd -d 200 loading  debug output
>> - steps to reproduce the error.
>>  
>> I believe this is the fastest way of the bacula.org
>>  team to address this problem properly.
>>  
>> Regards,
>>
>> Problem has been reported.
>>
>> Hello Sruckh: the error you reported is different from the OP.
>> For everyone also having the: "Apr 27 20:59:59 backup bacula-sd[498]:
>> cloud_dev.c:1001 Could not open Cloud driver type=1 for
>> Device=.", you are encouraged also to full a bug report.
>>
>> Thank You.
>>
>> Regards,
>> -- 
>>
>> MSc Heitor Faria (Miami/USA)
>> Bacula LATAM CEO
>> mobile1: + 1 

Re: [Bacula-users] S3 "Driver" Doesn't Work 11.0.2 - You may not want to!

[r0...@nxlplyx.com]

Kern,

You may not want to!  Specifically, retirement may be hazardous to your
health.  See the link below:

https://www.worldlifeexpectancy.com/do-retired-people-live-longer

Al


On 5/7/21 12:59 PM, Kern Sibbald wrote:
> Hello,
>
> Yes, I guess I should stay retired :-)
>
> Best regards,
> Kern
>
> On 5/7/21 12:39 PM, Martin Simmons wrote:
>>> On Thu, 6 May 2021 18:01:41 +0200, Kern Sibbald said:
>>> Your fundamental problem in making the S3 plugin work is that plugin
>>> has the wrong name -- this can be seen from the -D200 debug output
>>> you supplied.  The Bacula SD is looking for plugins named:
>>> xxx-sd.so, and your plugin is named xxx.so, so Bacula is not finding
>>> it.
>> I think that is wrong.  The files named xxx-sd.so are SD plugins, not
>> drivers.
>>
>> __Martin
>>
>
>
>
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users