Re: [Bacula-users] areas for improvement?

[Dmitri Maziuk]

On 6/12/2020 12:39 PM, David Brodbeck wrote:


None of this, of course, is an issue when backing up always-on servers with
static IPs -- which is Bacula's focus.


Not really: what's happening is if an intermediate node goes down, IP 
will find a different route -- *at the network layer*.


We normally run backups over non-routed links. "Always-on servers with 
static IPs" would normally be on the same (V)LAN. A VPN is a direct 
point-to-point link at Data Link Layer, even if it's tunneled over TCP/IP.


When a switch or NAT router or a virtual interface goes down at link 
layer, there's nothing IP can do about it.


The problem is time: as data size goes up, it takes longer to complete 
the backup, and with that the chances of a link-level disruption go up too.


Dima


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

Re: [Bacula-users] areas for improvement?

[Heitor Faria]

Hello David, 

> It's fair to argue that both NAT routers and VPNs are a corruption of TCP/IP's
> design intent, but it doesn't seem likely we'll be rid of them any time soon.
> Bacula doesn't work very well with either. Besides the connection drop issues,
> I haven't yet gotten client-initiated backups to work from behind a NAT, and I
> haven't found anyone who's confirmed they have it working, either.

It is painful, requires tray-monitor and console configurations on the 
client-side, but I was able to make it work 
.
 
However, as for Firewall Transversing, the Enterprise Bacula Edition has now a 
proper better solution 

 that eventually could be ported to the Community version, but I have no 
information on that. 

> --
> David Brodbeck
> System Administrator, Department of Mathematics
> University of California, Santa Barbara

Regards, 
-- 

MSc Heitor Faria 
Bacula LATAM CEO 

mobile1: + 1 909 655-8971 
mobile2: + 55 61 98268-4220 
[ https://www.linkedin.com/in/msc-heitor-faria-5ba51b3 ] 
[ http://www.bacula.com.br/ ] 

América Latina 
[ http://bacula.lat/ | bacula.lat ] | [ http://www.bacula.com.br/ | 
bacula.com.br ] 
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] areas for improvement?

[David Brodbeck]

On Wed, Jun 10, 2020 at 8:41 AM Josh Fisher  wrote:

> I still feel that Bacula's design is correct. Yes, 802.3az changes the
> always-on nature of a connection, allowing either side to temporarily
> power down its transmitter to save energy, but the standard itself
> doesn't change the original goal of a persistent connection. It is the
> switch firmware and/or NIC device drivers that claim to support it, but
> do not. It makes sense for Bacula to be as robust as possible, but this
> is not a Bacula design flaw. It is a work-around for buggy hardware.
>

I've also run into this when trying to back up over a VPN. The backup time
can easily exceed the VPN's maximum session time.

It's fair to argue that both NAT routers and VPNs are a corruption of
TCP/IP's design intent, but it doesn't seem likely we'll be rid of them any
time soon. Bacula doesn't work very well with either. Besides the
connection drop issues, I haven't yet gotten client-initiated backups to
work from behind a NAT, and I haven't found anyone who's confirmed they
have it working, either.

None of this, of course, is an issue when backing up always-on servers with
static IPs -- which is Bacula's focus. The problems come in when it's used
to back up endpoints. Unfortunately I haven't yet found anything else to
use for that that lets me control my own data and isn't a subscription
model. (In academic departments, it's much easier to find money for
one-time expenses than it is to find a consistent source of it.)

-- 
David Brodbeck
System Administrator, Department of Mathematics
University of California, Santa Barbara
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

[Bacula-users] Bacula Release 9.6.5

[Kern Sibbald]

Hello,

Unfortunately due to a Enterprise backport of code to the Community
version, three files were released to version 9.6.4 with Enterprise
copyrights.  In addition there were apparently several missing image
files in the documentation.  Thus we have withdrawn version 9.6.4
and replaced it with version 9.6.5.  If either of the just mentioned
problems worry you, please update to version 9.6.5.  Otherwise versions
9.6.4 and 9.6.5 are identical. I regret any inconvenience.

This is to announce that we have released Bacula version 9.6.5 to
Source Forge and to www.bacula.org.  This is a major security and
bug fix release. We suggest everyone to upgrade as soon as possible,
especially if you are using or want to use the S3 cloud driver. Note: I have
done some significant testing on building and running the S3 cloud drive
with Amazon cloud.  In doing so, I found and fixed a significant bug that
caused the cloud driver (and possibly other drivers) that caused memory
loss (orphaned buffers).

One significant improvement is for the AWS S3 cloud driver. First the
code base has been brought much closer to the Enterprise version (still
a long ways to go). Second is that the community code now uses the latest
version of libs3 as maintained by Bacula Systems.  The libs3 code is
available as a tar file for Bacula version 9.6.5 at:

   www.bacula.org/downloads/libs3-20200523.tar.gz

Version 9.6.5 and later must be compiled with the above libs3 version or 
later.

To build libs3:
- Remove any libs3 package loaded by your OS
- Download above link
- tar xvfz libs3-20200523.tar.gz
- cd libs3-20200523
- make  # should have no errors
- sudo make install

Then when you do your Bacula ./configure  it should automatically
detect and use the libs3. The output from the ./configure will show
whether or not libs3 was found during the configuration. E.g.
   S3 support:    yes
in the output from ./configure.

The binary files should be released within the next week or two.

For your convenience, I have included some more of the details from the 
ReleaseNotes file below.


Thanks for using Bacula.

Be happy,

Kern

=== Additional details from the Release Notes.

11Jun20
 - Add configure variables to baculabackupreport. Patch from bug #2538
 - Fix orphaned buffers in cloud by adding truncate argument to 
end_of_job()
 - Improve clarity of Cloud part mismatches and make it an INFO message 
rather

   than a WARNING since it corrects the catalog.
 - Small trivial change to check_parts
 - Backport more Enterprise cloud parts changes
 - Backport cloud upload code from Enterprise
 - Update s3_driver.c to new libs3 API calling sequence
 - Fix tray-monitor installation
 - Recompile ./configure
 - Add ./configure code to check for and enable/disable S3 support
 - win32: Fix org#2547 About possible NULL pointer dereference in 
get_memory_in

 - Ensure cloud driver loaded when listing cloud volumes
 - baculum: Request #2546 support for full restore when file records 
for backup

   job are pruned
 - baculum: Fix problem with authorization error after upgrade
 - baculum: Add UPGRADE file
 - baculum: Fix returning value in TStyleDiff - generated notice with PHP
   7.4
 - baculum: Remove execute bit for framework scripts
 - baculum: Fix displaying empty column button in table column 
visibility menu

  reported by Wanderlei Huttel
 - baculum: Update Polish translations
 - baculum: Update Portuguese translations
 - baculum: New user management. LDAP support. Role-based access control.
 - Fix new compiler warnings + always use bstrncpy not strncpy to 
ensure EOS at

   end of string
 - Return smartalloc buffers zeroed -- future performance improvement
 - Improve scanning data/time, fixes bug #2472
 - Make ABORT mention segfault to clarify non-bug #2528
 - Make reading a short block a warning rather than error
 - baculum: Fix validators in run job modal window
 - Remove unused -t option in dbcheck.c -- fixes bug #2453
 - Fix bug 2523 -- spurious extra linking
 - Fix bug #2534 possible double free in error case
 - Fix possible sscanf overflows
 - Fix overflow from malicious FD reported by Pasi Saarinen
 - baculum: Add option to show time in job log - idea proposed by Wanderlei
   Huttel
 - baculum: Add show log time parameter to job log endpoint
 - baculum: Add tip about using table row selection
 - Fix bug #2525 seg fault when doing estimate with accurate and MD5
 - baculum: Fix issues with SELinux support reported by Neil MacGregor
 - Correct some copyrights
 - Add Docker plugin rpm spec files

Bugs fixed/closed since last release:
2453 2472 2525 2528 2534 2538 2546 2547





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



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