[Bacula-users] Fw: read this

[ed]

Hello!

 

New message, please read 

 

e...@gurski.com

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

[Bacula-users] Fedora/CentOS/RHEL Bacula 7.2.0 status and backports repository

[Simone Caronni]

Hello,

Bacula 7.2.0 is now in rawhide (Fedora 24) and pending update in Fedora 23,
the idea is to have Fedora 23 already shipping with Bacula 7.2.x.

I'm planning to delete the Bacula 5.x repository on fedorapeople [1] and
just leave the one that contains Bacula 7.0.x [2] for CentOS/RHEL 5/6/7.

While the COPR repository [3] will always contain the latest Bacula package
(currently 7.2.x), that means you can have an eterogeneous infrastructure
with supported (non EOL) releases of Fedora/CentOS/RHEL all running the
same Bacula daemon versions.

Summing up, this is the current status in the distributions:

- el5 (through EPEL) - Bacula 2.4
- el6 - Bacula 5.0.0
- el7 - Bacula 5.2.13
- f21/f22 - Bacula 7.0.5
- f23/rawhide - Bacula 7.2.0

With the addition of one of the two repositories, users will have the
choice of installing version 7.0.5 or 7.2.0 for ALL supported
distributions, including RHEL 7. That means, the same Fedora 23 versions
down to CentOS/RHEL 5.

Any questions, requests, comments, regarding RHEL/CentOS/Fedora packages
and repositories are welcome.

Regards,
--Simone

[1] http://repos.fedorapeople.org/repos/slaanesh/bacula/
[2] http://repos.fedorapeople.org/repos/slaanesh/bacula7/
[3] https://copr.fedoraproject.org/coprs/slaanesh/Bacula/


-- 
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).

http://xkcd.com/229/
http://negativo17.org/
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Issue with second writing to tape

[Radosław Korzeniewski]

Hello,

Again: Did you tested your tape drive with btape utility? For me it is a
misconfigured storage device.

best regards

2015-09-24 19:54 GMT+02:00 ADCD Support :

> I use 64bits system.
> I tried with other version of file daemon but still the same, stopped
> after 20GB
>
> 24-Sep 18:46 buffer-bacula-sd JobId 121: Fatal error: Unable to write EOF.
> ERR=dev.c:1551 ioctl MTWEOF error on "DTL01" (/dev/nst0). ERR=Input/output
> error.
>
> 24-Sep 18:46 buffer-bacula-sd JobId 121: Error: Error writing final EOF to
> tape. This Volume may not be readable.
> dev.c:1551 ioctl MTWEOF error on "DTL01" (/dev/nst0). ERR=Input/output
> error.
> 24-Sep 18:46 buffer-bacula-sd JobId 121: Job write elapsed time =
> 03:19:49, Transfer rate = 1.666 M Bytes/second
> 24-Sep 18:49 cow-fd JobId 121: Error:
> /home/kern/bacula/k/bacula/src/lib/bsock.c:389 Write error sending 65536
> bytes to Storage daemon:192.168.0.70:9103: ERR=Input/output error
> 24-Sep 18:49 cow-fd JobId 121: Fatal error:
> /home/kern/bacula/k/bacula/src/filed/backup.c:1144 Network send error to
> SD. ERR=Input/output error
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "System
> Writer", State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "MSDEWriter",
> State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "IIS Metabase
> Writer", State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "Registry
> Writer", State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "COM+ REGDB
> Writer", State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "Event Log
> Writer", State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:49 cow-fd JobId 121: VSS Writer (BackupComplete): "WMI Writer",
> State: 0x1 (VSS_WS_STABLE)
> 24-Sep 18:48 buffer-bacula-dir JobId 121: Error: Bacula buffer-bacula-dir
> 5.2.5 (26Jan12):
> Build OS: x86_64-pc-linux-gnu ubuntu 12.04
> JobId: 121
> Job: cow-bj.2015-09-24_15.26.32_04
> Backup Level: Full
> Client: "cow" 5.2.1 (30Oct11) Microsoft Windows Home ServerStandard
> Edition Service Pack 2 (build 3790),Cross-compile,Win32
> FileSet: "cow" 2015-09-07 02:00:04
> Pool: "Main" (From Job resource)
> Catalog: "MyCatalog" (From Client resource)
> Storage: "HPTapeLibrary" (From Job resource)
> Scheduled time: 24-Sep-2015 15:26:29
> Start time: 24-Sep-2015 15:26:34
> End time: 24-Sep-2015 18:48:16
> Elapsed time: 3 hours 21 mins 42 secs
> Priority: 10
> FD Files Written: 186,596
> SD Files Written: 186,596
> FD Bytes Written: 19,947,109,995 (19.94 GB)
> SD Bytes Written: 19,980,349,784 (19.98 GB)
> Rate: 1648.2 KB/s
> Software Compression: None
> VSS: yes
> Encryption: no
> Accurate: no
> Volume name(s): TAPE05L5
> Volume Session Id: 1
> Volume Session Time: 1443100511
> Last Volume Bytes: 19,998,720,000 (19.99 GB)
> Non-fatal FD errors: 1
> SD Errors: 2
> FD termination status: Error
> SD termination status: Error
> Termination: *** Backup Error ***
>
> On Tue, 22 Sep 2015 20:17:07 +0300, Ana Emília M. Arruda <
> emiliaarr...@gmail.com> wrote:
>
> Hello,
>
> The recommendation for Bacula versions are:
>
> director = storage daemon >= file daemon
>
> It seems you have your director and storage daemon running 5.2.5 version
> and client running 5.2.10. Also, is your system 32 or 64 bits?
>
> Best regards,
> Ana
>
> On Tue, Sep 22, 2015 at 2:48 AM, Radosław Korzeniewski <
> rados...@korzeniewski.net> wrote:
>
>> Hello
>>
>> Did you tested your tape drive with btape utility? What was a result of
>> the test?
>>
>> best regards
>>
>> 2015-09-20 18:00 GMT+02:00 ADCD IT :
>>
>>> Hi Everyone,
>>>
>>> I have issue writing to my tapes.
>>>
>>> I have an HP tape library connected to ubuntu 12.04 with bacula 5.2.5
>>> installed.
>>> when I am running a full backup job on any client or with any tape (tapes
>>> are new, so its not tape issue)
>>> the job stops in the middle after the SD wrote about 20GB than mark the
>>> tape as FULL and throw those errors:
>>>
>>> 19-Sep 16:53 buffer-bacula-dir JobId 108: Start Backup JobId 108,
>>> Job=cow-bj.2015-09-19_16.53.18_08
>>> 19-Sep 16:53 buffer-bacula-dir JobId 108: Using Device "DTL01"
>>> 19-Sep 16:53 buffer-bacula-sd JobId 108: Wrote label to prelabeled Volume
>>> "TAPE05L5" on device "DTL01" (/dev/nst0)
>>> 19-Sep 16:55 cow-fd JobId 108: Generate VSS snapshots. Driver="Win32
>>> VSS",
>>> Drive(s)="CD"
>>> 19-Sep 20:22 buffer-bacula-sd JobId 108: Fatal error: Unable to write
>>> EOF.
>>> ERR=dev.c:1551 ioctl MTWEOF error on "DTL01" (/dev/nst0).
>>> ERR=Input/output
>>> error.
>>>
>>> 19-Sep 20:22 buffer-bacula-sd JobId 108: Error: Error writing final EOF
>>> to
>>> tape. This Volume may not be readable.
>>> dev.c:1551 ioctl MTWEOF error on "DTL01" (/dev/nst0). ERR=Input/output
>>> error.
>>> 19-Sep 20:22 buffer-bacula-sd JobId 108: Job write elapsed time =
>>> 03:29:04, Transfer rate = 1.990 M 

[Bacula-users] Bacula Windows binaries

[Egoitz Aurrekoetxea]

Good morning,

Does bacula windows binaries exist available for buying for the 5.2 branch 
newer than the 5.2.10 ?.

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

Re: [Bacula-users] Bacula Windows binaries

[Kern Sibbald]

Yes, see the right of the three boxes on the first page of www.bacula.org

On 15-09-29 07:47 AM, Egoitz Aurrekoetxea wrote:
> Good morning,
>
> Does bacula windows binaries exist available for buying for the 5.2 branch 
> newer than the 5.2.10 ?.
>
> Best regards,
> --
> ___
> 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 Windows binaries

[Egoitz Aurrekoetxea]

Hi Kern,

Yep I have that read but as when talking about current release in 
http://www.baculasystems.com/windows-binaries-for-bacula-community-users 
 it 
talks about 
7.0.5 I was wondering if perhaps a bacula-fd 5.2.13 existed.

So then yes isn’t it?,

Thank you so much,
Regards,


> El 29/9/2015, a las 17:04, Kern Sibbald  escribió:
> 
> Yes, see the right of the three boxes on the first page of www.bacula.org
> 
> On 15-09-29 07:47 AM, Egoitz Aurrekoetxea wrote:
>> Good morning,
>> 
>> Does bacula windows binaries exist available for buying for the 5.2 branch 
>> newer than the 5.2.10 ?.
>> 
>> Best regards,
>> --
>> ___
>> 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] Question about bacula and tls

[Ana Emília M . Arruda]

On Mon, Sep 28, 2015 at 6:20 PM, Egoitz Aurrekoetxea 
wrote:

> Good night,
>

​Good night Egoitz. Sorry for my late reply.​


>
> First of all thanks a lot for your time :)
>

​Thank you for this thread :)​


>
> El 28/9/2015, a las 21:46, Ana Emília M. Arruda 
> escribió:
>
> Hello,
>
> The TLS enable do not force the use of TLS. For example, if you configure
> your director with TLS enable = yes and TLS require = no, clients can
> communicate with your director with or without TLS. But if you configure
> your director with both TLS enable and TLS require = yes, then all your
> clients and storage daemons will only be able to communicate with your
> director with TLS.
>
>
> Yes, this is clear
>
>
> If you do not set TLS Verify Peer or TLS Allowed CN, then you can use any
> Certificate File or Directory. The certificate CN will not be checked
> against the Certificate File or Directory configured.
>
>
> what do you mean? any ca or ca path for each side cert? I could use
> certificates from different ca in each side?. Even having the proper cn,
> this doesn’t worked in my testing env (which doesn’t use tis verify peer or
> tls allowed cn) … you mean the certificate won’t be checked if it was
> created by the ca_certificate file's ca? Sorry can’t understand this...
>

​Yes, you can have certificates from different CA in each side, you just
need to inform the CA correctly for peer verification. How did you
generated your certificates? Do you have a CA and signed them properly?


>
>
> If TLS Verify Peer is enabled, then the peer´s hostname is verified
> against the subjectAltName (alternative name) and commonName attributes.
> This way, a certificate issued for myclient2.example.com cannot be used,
> for example, by a host named myclient1.example.com. Even if they are
> issued by your own CA (not a trusted root CA), you have the CN of the
> certificate file checked against the hostname (director, client or storage
> daemon host) that is using it.
>
>
> Are you sure? this config parameter requires to specify ca cert file or ca
> path.. and the code seems to be doing a check of the remote side cert to be
> issued by the ca listed in ca cert or ca path…..
>
> This just means the tls verify peer?. You can for instance use different
> ca for bacula-dir and bacula-fd mean while one cert with one ca has as cn
> the server name and the other one the bacula-fd’s daemon hostname?. Even
> when the ca is not trusted?? will it work?. Sorry but this doesn’t work to
> me…. are you really sure Ana?
>
>
​If you have certificates signed by different CA's, you just need to inform
them through the "TLS CA Certificate File" or ​"TLS CA Certificate Dir" to
the other peer. For example, if you have director's certificate signed by
CA1 and you have client1's certificate signed by CA2, then your director
will need to know about the CA2 certificate to verify the client1
certificate.


>
> If TLS Allowed CN is enabled, then in addition to the peer´s hostname
> being verified, just that ones listed in the "TLS Allowed CN" directives
> are permited.
>
>
> So each part to have it’s proper cert (matching cn with the connecting
> name and so) and if this last is ok… to be in tls allowed cn too… do you
> mean this?
>

Yes, but I misunderstood here. I was having a look into the code and now I
understand this: if TLS Allowed CN is specified, then the CN's listed here
will be verified against ​​the cn present in the certifcate provided by the
peer. If no TLS Allowed CN is specified then a simple host and certificate
common name comparision takes place.


>
> If TLS Verify Peer is not enabled and a client uses a "false" certificate
> (myclient2 using the myclient1 certificate and myclient1 is in the allowed
> CN list, for example) from a host in the allowed CN list of allowed hosts,
> it will work.
>
>
> I see… so the cert can be both from the same ca or not..or… isn’t it?
>
>
> Openssl functions are used for certificate manipulation (including
> validation and verification).
>
>
> Yep I’ve seen in the code…
>
>
> So, it will depend of what you want to have in you TLS communication, even
> if using your own CA for the PKI infrastructure used in your bacula TLS
> environment. You can have your own CA (a virtual machine for this purpose),
> that will be your trusted CA for your environment. And let all your daemons
> trust in each other by setting properly the TLS Verify Peer and TLS Allowed
> CN directives. I think this should work fine for what you want.
>
>
> I could use tls verify peer in the director and in bacula-fd (dir and sd
> are the same machine and to use loopback)…
>
> I wanted each director and each fd, to only be able to be accesed by just
> those remote daemons who own a certificate allowing them to do so…
>
> could you please paste an example config?
>

​Sure. For example, this worked fine for me:

bconsole.conf:

Director {
  Name = director.example.com-dir
  DIRport = 9101
  address 

[Bacula-users] bacula listening on ipv6?

[Thing]

>From the messages below I suspect its a problem due to bacula listening on
the ipv6 interface, can ipv6 support be turned off for bacula?


==

Hi,


trying to set up bacula on a RaspberryPi and I have this error,


=

bconsole: bsock.c:223 Socket open error. proto=10 port=9101. ERR=Address
family not supported by protocol

=

root@raspberrypi:/bacula/backup# bconsole -d10
Connecting to Director localhost:9101
bconsole: bsock.c:223 Socket open error. proto=10 port=9101. ERR=Address
family not supported by protocol
bconsole: authenticate.c:150-0 >dird: 1000 OK auth
bconsole: authenticate.c:157-0 dird: 1000 OK auth
bconsole: authenticate.c:157-0 --
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users