Re: [Bacula-users] Bacula version 7.2.0 released
On 14.08.2015 16:18, Wanderlei Huttel wrote: Hi Alex This is a feature already included in previous version (7.0.5) Very true at least concerning the directives. I am not 100% sure, but I think that we added the ability to "dynamically" modify the bandwidth limitation from the command line. Of course it is possible that was already in version 7.0.5. Best regards, Kern Best Regards Wanderlei 2015-08-14 10:55 GMT-03:00 Alex Domoradov: > Job Bandwidth Limitations I have been waiting this feature for a few years. And finally I got it. Thanks a lot! On Fri, Aug 14, 2015 at 4:01 PM, Kern Sibbald wrote: Hello Wanderlei, I am pleased to hear that it is working well for you. There are many new features and additions nice things like binaries that the project (thanks to help from Bacula Systems) should be supplying in the future -- some great features are a bit longer term, but binaries I hoping for in the near future. Thanks the encouragement and for using Bacula. Best regards, Kern On 14.08.2015 14:58, Wanderlei Huttel wrote: Hi Kern Thank you for having released this new version and congratulations for the excellent work! I've upgraded my system in this morning and I've made some operations of backup and restore and everything is working fine! Best Regards Wanderlei 2015-08-14 9:23 GMT-03:00 Kern Sibbald : Hello, Our Bacula Systems gnome gurus have been working hard in the Swiss mountains, and their work is now released as Bacula version 7.2.0. You can find the source code at Source Forge as usual. This version has quite a number of difficult and important bug fixes over version 7.0.5 as well as a good number of new features. I won't attempt to list all the new features here, but suggest that you look at the New Features chapter of the manual. Please note that there may be a few new features documented in the 7.2. section of the manual that were actually in 7.0.5 -- I just ran out of time at the end, so rather than miss a feature, I took the risk to include some already released.
Re: [Bacula-users] bacula-fd cannot access files from the system still getting [permission denied]
Hello Jing, I misunderstood the issue. You are able to start the client file daemon. Could you post the “permission denied” error messages you are getting? Best regards, Ana On Fri, Aug 14, 2015 at 9:00 PM, JING YANG wrote: > Dear Ana, >It is like this, > > -rw-r- 1 bacula bacula 5 Aug 14 02:19 bacula-sd.9103.pid > > -rw-r- 1 root root 5 Aug 14 02:19 bacula-fd.9102.pid > > -rw-r- 1 bacula bacula 5 Aug 14 11:05 bacula-dir.9101.pid > > anything wrong here? > > Thanks, > > Jing > > On Fri, Aug 14, 2015 at 2:58 PM, Ana Emília M. Arruda < > emiliaarr...@gmail.com> wrote: > >> Hello Jing, >> >> Have you checked the write permissions on your Pid Directory? >> >> PIDFILE=/var/run/bacula/$NAME.$PORT.pid >> >> Best regards, >> Ana >> >> Em sex, 14 de ago de 2015 às 14:07, Jing At Penn >> escreveu: >> >>> Dear Josip, >>> I really appreciate your help. I am using archlinux. I figured >>> the system daemon configuration file is running under >>> /use/lib/systemd/system/bacula-fd.service. So I changed the user and group >>> in there. Now, I checked "ps aux | grep bacula-fd" it's running as root. >>> However, I still get the permission error. I am running out of ideas >>> right. Desperate for your help >>> >>> Thanks, >>> Jing >>> >>> >>> > On Aug 13, 2015, at 7:15 AM, Josip Deanovic < >>> djosip+n...@linuxpages.net> wrote: >>> > >>> >> On Tuesday 2015-08-11 17:40:17 Jing Yang wrote: >>> >> Here is my init.d script file, i did not see the -u option …. BUSER >>> and >>> >> BGROUP are the two things some other mailing list user told me to put >>> >> there, however, that does not work either. >>> > >>> > Hi! >>> > >>> > I am not sure what OS you are using so my advice here could probably >>> > be improved if you use the solution more suitable for your system. >>> > >>> > If you just want to start the bacula-fd daemon using that init script >>> > and see how it works you can modify this line: >>> > ARGS="-c /etc/bacula/${NAME}.conf" >>> > so that it looks like this: >>> > ARGS="-c /etc/bacula/${NAME}.conf -u root -g root" >>> > >>> > The content of the ARGS variable is later in the function do_start() >>> > passed to the command which will execute the bacula-fd daemon. >>> > >>> > After starting bacula-fd using that modified init script, bacula-fd >>> > should run as root. You can check the process list as before to >>> > ensure that. >>> > >>> > Again, most systems support some procedure that can be used to >>> > source (include) additional file with additional options and >>> > variables. >>> > >>> > I would suggest that you find the best way to supply additional >>> > parameters to the init scripts on your system because modified >>> > init scripts are likely to be overwritten during the update of >>> > the related package. >>> > >>> > >>> >> #!/bin/sh >>> >> ### BEGIN INIT INFO >>> >> # Provides: bacula-fd >>> >> # Required-Start:$remote_fs $syslog >>> >> # Required-Stop: $remote_fs $syslog >>> >> # Should-Start: bacula-sd >>> >> # Should-Stop: bacula-sd >>> >> # Default-Start: 2 3 4 5 >>> >> # Default-Stop: 0 1 6 >>> >> ### END INIT INFO >>> >> # >>> >> # bacula-fd SysV init script for Bacula-FD. >>> >> # >>> >> # Written by Miquel van Smoorenburg . >>> >> # Modified for Debian GNU/Linux by Ian Murdock >>> >> . # Customized for Bacula by Jose Luis >>> >> Tallon # >>> >> >>> >> . /lib/lsb/init-functions >>> >> >>> >> NAME="bacula-fd" >>> >> DESC="Bacula File daemon" >>> >> PATH=/sbin:/bin:/usr/sbin:/usr/bin >>> >> DAEMON=/usr/sbin/${NAME} >>> >> BUSER=root >>> >> BGROUP=root >>> >> PORT=9102 >>> >> ARGS="-c /etc/bacula/${NAME}.conf" >>> >> >>> >> test -f $DAEMON || exit 0 >>> >> >>> >> set -e >>> >> >>> >> if [ -n "`getent services bacula-fd`" ]; then >>> >>PORT=`getent services bacula-fd | awk '{ gsub("/tcp","",$2); >>> >> print $2; }'` fi >>> >> >>> >> . /lib/lsb/init-functions >>> >> . /usr/share/bacula-common/common-functions >>> >> create_var_run_dir >>> >> >>> >> PIDFILE=/var/run/bacula/$NAME.$PORT.pid >>> >> >>> >> do_start() >>> >> { >>> >>start-stop-daemon --start --quiet --pidfile $PIDFILE \ >>> >>--exec $DAEMON -- $ARGS >>> >> } >>> >> >>> >> do_stop() >>> >> { >>> >>start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \ >>> >>--exec $DAEMON >>> >> } >>> >> >>> >> case "$1" in >>> >> start) >>> >>if [ -f /etc/bacula/do_not_run ]; then >>> >>log_failure_msg "Not starting $DESC: disabled via >>> >> /etc/bacula/do_not_run" exit 0 >>> >>fi >>> >> >>> >>log_daemon_msg "Starting $DESC..." >>> >>if do_start ; then >>> >>log_end_msg 0 >>> >>else >>> >>log_end_msg 1 >>> >>fi >>> >>;; >>> >> stop) >>> >>log_daemon_msg "Stopping $DESC..." >>> >>if do_stop ; then >>> >>log_end_msg 0 >>> >>else >>> >>log_end_msg
Re: [Bacula-users] bacula-fd cannot access files from the system still getting [permission denied]
Dear Ana, It is like this, -rw-r- 1 bacula bacula 5 Aug 14 02:19 bacula-sd.9103.pid -rw-r- 1 root root 5 Aug 14 02:19 bacula-fd.9102.pid -rw-r- 1 bacula bacula 5 Aug 14 11:05 bacula-dir.9101.pid anything wrong here? Thanks, Jing On Fri, Aug 14, 2015 at 2:58 PM, Ana Emília M. Arruda < emiliaarr...@gmail.com> wrote: > Hello Jing, > > Have you checked the write permissions on your Pid Directory? > > PIDFILE=/var/run/bacula/$NAME.$PORT.pid > > Best regards, > Ana > > Em sex, 14 de ago de 2015 às 14:07, Jing At Penn > escreveu: > >> Dear Josip, >> I really appreciate your help. I am using archlinux. I figured >> the system daemon configuration file is running under >> /use/lib/systemd/system/bacula-fd.service. So I changed the user and group >> in there. Now, I checked "ps aux | grep bacula-fd" it's running as root. >> However, I still get the permission error. I am running out of ideas >> right. Desperate for your help >> >> Thanks, >> Jing >> >> >> > On Aug 13, 2015, at 7:15 AM, Josip Deanovic >> wrote: >> > >> >> On Tuesday 2015-08-11 17:40:17 Jing Yang wrote: >> >> Here is my init.d script file, i did not see the -u option …. BUSER and >> >> BGROUP are the two things some other mailing list user told me to put >> >> there, however, that does not work either. >> > >> > Hi! >> > >> > I am not sure what OS you are using so my advice here could probably >> > be improved if you use the solution more suitable for your system. >> > >> > If you just want to start the bacula-fd daemon using that init script >> > and see how it works you can modify this line: >> > ARGS="-c /etc/bacula/${NAME}.conf" >> > so that it looks like this: >> > ARGS="-c /etc/bacula/${NAME}.conf -u root -g root" >> > >> > The content of the ARGS variable is later in the function do_start() >> > passed to the command which will execute the bacula-fd daemon. >> > >> > After starting bacula-fd using that modified init script, bacula-fd >> > should run as root. You can check the process list as before to >> > ensure that. >> > >> > Again, most systems support some procedure that can be used to >> > source (include) additional file with additional options and >> > variables. >> > >> > I would suggest that you find the best way to supply additional >> > parameters to the init scripts on your system because modified >> > init scripts are likely to be overwritten during the update of >> > the related package. >> > >> > >> >> #!/bin/sh >> >> ### BEGIN INIT INFO >> >> # Provides: bacula-fd >> >> # Required-Start:$remote_fs $syslog >> >> # Required-Stop: $remote_fs $syslog >> >> # Should-Start: bacula-sd >> >> # Should-Stop: bacula-sd >> >> # Default-Start: 2 3 4 5 >> >> # Default-Stop: 0 1 6 >> >> ### END INIT INFO >> >> # >> >> # bacula-fd SysV init script for Bacula-FD. >> >> # >> >> # Written by Miquel van Smoorenburg . >> >> # Modified for Debian GNU/Linux by Ian Murdock >> >> . # Customized for Bacula by Jose Luis >> >> Tallon # >> >> >> >> . /lib/lsb/init-functions >> >> >> >> NAME="bacula-fd" >> >> DESC="Bacula File daemon" >> >> PATH=/sbin:/bin:/usr/sbin:/usr/bin >> >> DAEMON=/usr/sbin/${NAME} >> >> BUSER=root >> >> BGROUP=root >> >> PORT=9102 >> >> ARGS="-c /etc/bacula/${NAME}.conf" >> >> >> >> test -f $DAEMON || exit 0 >> >> >> >> set -e >> >> >> >> if [ -n "`getent services bacula-fd`" ]; then >> >>PORT=`getent services bacula-fd | awk '{ gsub("/tcp","",$2); >> >> print $2; }'` fi >> >> >> >> . /lib/lsb/init-functions >> >> . /usr/share/bacula-common/common-functions >> >> create_var_run_dir >> >> >> >> PIDFILE=/var/run/bacula/$NAME.$PORT.pid >> >> >> >> do_start() >> >> { >> >>start-stop-daemon --start --quiet --pidfile $PIDFILE \ >> >>--exec $DAEMON -- $ARGS >> >> } >> >> >> >> do_stop() >> >> { >> >>start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \ >> >>--exec $DAEMON >> >> } >> >> >> >> case "$1" in >> >> start) >> >>if [ -f /etc/bacula/do_not_run ]; then >> >>log_failure_msg "Not starting $DESC: disabled via >> >> /etc/bacula/do_not_run" exit 0 >> >>fi >> >> >> >>log_daemon_msg "Starting $DESC..." >> >>if do_start ; then >> >>log_end_msg 0 >> >>else >> >>log_end_msg 1 >> >>fi >> >>;; >> >> stop) >> >>log_daemon_msg "Stopping $DESC..." >> >>if do_stop ; then >> >>log_end_msg 0 >> >>else >> >>log_end_msg 1 >> >>fi >> >>;; >> >> >> >> restart|force-reload) >> >>$0 stop >> >>sleep 1 >> >>$0 start >> >>;; >> >> status) >> >>status_of_proc -p $PIDFILE $DAEMON $NAME >> >>;; >> >> *) >> >>N=/etc/init.d/$NAME >> >>echo "Usage: $N {start|stop|restart|force-reload|status}" >&2 >> >>exit 1 >> >>;; >> >> esac >> >> >> >> exit 0 >> > >
Re: [Bacula-users] bacula-fd cannot access files from the system still getting [permission denied]
Hello Jing, Have you checked the write permissions on your Pid Directory? PIDFILE=/var/run/bacula/$NAME.$PORT.pid Best regards, Ana Em sex, 14 de ago de 2015 às 14:07, Jing At Penn escreveu: > Dear Josip, > I really appreciate your help. I am using archlinux. I figured > the system daemon configuration file is running under > /use/lib/systemd/system/bacula-fd.service. So I changed the user and group > in there. Now, I checked "ps aux | grep bacula-fd" it's running as root. > However, I still get the permission error. I am running out of ideas > right. Desperate for your help > > Thanks, > Jing > > > > On Aug 13, 2015, at 7:15 AM, Josip Deanovic > wrote: > > > >> On Tuesday 2015-08-11 17:40:17 Jing Yang wrote: > >> Here is my init.d script file, i did not see the -u option …. BUSER and > >> BGROUP are the two things some other mailing list user told me to put > >> there, however, that does not work either. > > > > Hi! > > > > I am not sure what OS you are using so my advice here could probably > > be improved if you use the solution more suitable for your system. > > > > If you just want to start the bacula-fd daemon using that init script > > and see how it works you can modify this line: > > ARGS="-c /etc/bacula/${NAME}.conf" > > so that it looks like this: > > ARGS="-c /etc/bacula/${NAME}.conf -u root -g root" > > > > The content of the ARGS variable is later in the function do_start() > > passed to the command which will execute the bacula-fd daemon. > > > > After starting bacula-fd using that modified init script, bacula-fd > > should run as root. You can check the process list as before to > > ensure that. > > > > Again, most systems support some procedure that can be used to > > source (include) additional file with additional options and > > variables. > > > > I would suggest that you find the best way to supply additional > > parameters to the init scripts on your system because modified > > init scripts are likely to be overwritten during the update of > > the related package. > > > > > >> #!/bin/sh > >> ### BEGIN INIT INFO > >> # Provides: bacula-fd > >> # Required-Start:$remote_fs $syslog > >> # Required-Stop: $remote_fs $syslog > >> # Should-Start: bacula-sd > >> # Should-Stop: bacula-sd > >> # Default-Start: 2 3 4 5 > >> # Default-Stop: 0 1 6 > >> ### END INIT INFO > >> # > >> # bacula-fd SysV init script for Bacula-FD. > >> # > >> # Written by Miquel van Smoorenburg . > >> # Modified for Debian GNU/Linux by Ian Murdock > >> . # Customized for Bacula by Jose Luis > >> Tallon # > >> > >> . /lib/lsb/init-functions > >> > >> NAME="bacula-fd" > >> DESC="Bacula File daemon" > >> PATH=/sbin:/bin:/usr/sbin:/usr/bin > >> DAEMON=/usr/sbin/${NAME} > >> BUSER=root > >> BGROUP=root > >> PORT=9102 > >> ARGS="-c /etc/bacula/${NAME}.conf" > >> > >> test -f $DAEMON || exit 0 > >> > >> set -e > >> > >> if [ -n "`getent services bacula-fd`" ]; then > >>PORT=`getent services bacula-fd | awk '{ gsub("/tcp","",$2); > >> print $2; }'` fi > >> > >> . /lib/lsb/init-functions > >> . /usr/share/bacula-common/common-functions > >> create_var_run_dir > >> > >> PIDFILE=/var/run/bacula/$NAME.$PORT.pid > >> > >> do_start() > >> { > >>start-stop-daemon --start --quiet --pidfile $PIDFILE \ > >>--exec $DAEMON -- $ARGS > >> } > >> > >> do_stop() > >> { > >>start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \ > >>--exec $DAEMON > >> } > >> > >> case "$1" in > >> start) > >>if [ -f /etc/bacula/do_not_run ]; then > >>log_failure_msg "Not starting $DESC: disabled via > >> /etc/bacula/do_not_run" exit 0 > >>fi > >> > >>log_daemon_msg "Starting $DESC..." > >>if do_start ; then > >>log_end_msg 0 > >>else > >>log_end_msg 1 > >>fi > >>;; > >> stop) > >>log_daemon_msg "Stopping $DESC..." > >>if do_stop ; then > >>log_end_msg 0 > >>else > >>log_end_msg 1 > >>fi > >>;; > >> > >> restart|force-reload) > >>$0 stop > >>sleep 1 > >>$0 start > >>;; > >> status) > >>status_of_proc -p $PIDFILE $DAEMON $NAME > >>;; > >> *) > >>N=/etc/init.d/$NAME > >>echo "Usage: $N {start|stop|restart|force-reload|status}" >&2 > >>exit 1 > >>;; > >> esac > >> > >> exit 0 > > > > > > -- > > Josip Deanovic > > > > > -- > > ___ > > 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:/
Re: [Bacula-users] bacula-fd cannot access files from the system still getting [permission denied]
Dear Josip, I really appreciate your help. I am using archlinux. I figured the system daemon configuration file is running under /use/lib/systemd/system/bacula-fd.service. So I changed the user and group in there. Now, I checked "ps aux | grep bacula-fd" it's running as root. However, I still get the permission error. I am running out of ideas right. Desperate for your help Thanks, Jing > On Aug 13, 2015, at 7:15 AM, Josip Deanovic > wrote: > >> On Tuesday 2015-08-11 17:40:17 Jing Yang wrote: >> Here is my init.d script file, i did not see the -u option …. BUSER and >> BGROUP are the two things some other mailing list user told me to put >> there, however, that does not work either. > > Hi! > > I am not sure what OS you are using so my advice here could probably > be improved if you use the solution more suitable for your system. > > If you just want to start the bacula-fd daemon using that init script > and see how it works you can modify this line: > ARGS="-c /etc/bacula/${NAME}.conf" > so that it looks like this: > ARGS="-c /etc/bacula/${NAME}.conf -u root -g root" > > The content of the ARGS variable is later in the function do_start() > passed to the command which will execute the bacula-fd daemon. > > After starting bacula-fd using that modified init script, bacula-fd > should run as root. You can check the process list as before to > ensure that. > > Again, most systems support some procedure that can be used to > source (include) additional file with additional options and > variables. > > I would suggest that you find the best way to supply additional > parameters to the init scripts on your system because modified > init scripts are likely to be overwritten during the update of > the related package. > > >> #!/bin/sh >> ### BEGIN INIT INFO >> # Provides: bacula-fd >> # Required-Start:$remote_fs $syslog >> # Required-Stop: $remote_fs $syslog >> # Should-Start: bacula-sd >> # Should-Stop: bacula-sd >> # Default-Start: 2 3 4 5 >> # Default-Stop: 0 1 6 >> ### END INIT INFO >> # >> # bacula-fd SysV init script for Bacula-FD. >> # >> # Written by Miquel van Smoorenburg . >> # Modified for Debian GNU/Linux by Ian Murdock >> . # Customized for Bacula by Jose Luis >> Tallon # >> >> . /lib/lsb/init-functions >> >> NAME="bacula-fd" >> DESC="Bacula File daemon" >> PATH=/sbin:/bin:/usr/sbin:/usr/bin >> DAEMON=/usr/sbin/${NAME} >> BUSER=root >> BGROUP=root >> PORT=9102 >> ARGS="-c /etc/bacula/${NAME}.conf" >> >> test -f $DAEMON || exit 0 >> >> set -e >> >> if [ -n "`getent services bacula-fd`" ]; then >>PORT=`getent services bacula-fd | awk '{ gsub("/tcp","",$2); >> print $2; }'` fi >> >> . /lib/lsb/init-functions >> . /usr/share/bacula-common/common-functions >> create_var_run_dir >> >> PIDFILE=/var/run/bacula/$NAME.$PORT.pid >> >> do_start() >> { >>start-stop-daemon --start --quiet --pidfile $PIDFILE \ >>--exec $DAEMON -- $ARGS >> } >> >> do_stop() >> { >>start-stop-daemon --oknodo --stop --quiet --pidfile $PIDFILE \ >>--exec $DAEMON >> } >> >> case "$1" in >> start) >>if [ -f /etc/bacula/do_not_run ]; then >>log_failure_msg "Not starting $DESC: disabled via >> /etc/bacula/do_not_run" exit 0 >>fi >> >>log_daemon_msg "Starting $DESC..." >>if do_start ; then >>log_end_msg 0 >>else >>log_end_msg 1 >>fi >>;; >> stop) >>log_daemon_msg "Stopping $DESC..." >>if do_stop ; then >>log_end_msg 0 >>else >>log_end_msg 1 >>fi >>;; >> >> restart|force-reload) >>$0 stop >>sleep 1 >>$0 start >>;; >> status) >>status_of_proc -p $PIDFILE $DAEMON $NAME >>;; >> *) >>N=/etc/init.d/$NAME >>echo "Usage: $N {start|stop|restart|force-reload|status}" >&2 >>exit 1 >>;; >> esac >> >> exit 0 > > > -- > Josip Deanovic > > -- > ___ > 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 version 7.2.0 released
Hi Alex This is a feature already included in previous version (7.0.5) Best Regards Wanderlei 2015-08-14 10:55 GMT-03:00 Alex Domoradov : > > Job Bandwidth Limitations > I have been waiting this feature for a few years. And finally I got it. > Thanks a lot! > > On Fri, Aug 14, 2015 at 4:01 PM, Kern Sibbald wrote: > >> Hello Wanderlei, >> >> I am pleased to hear that it is working well for you. There are many new >> features and additions nice things like binaries that the project (thanks >> to help from Bacula Systems) should be supplying in the future -- some >> great features are a bit longer term, but binaries I hoping for in the near >> future. >> >> Thanks the encouragement and for using Bacula. >> >> Best regards, >> Kern >> >> >> On 14.08.2015 14:58, Wanderlei Huttel wrote: >> >> Hi Kern >> >> Thank you for having released this new version and congratulations for >> the excellent work! >> >> I've upgraded my system in this morning and I've made some operations of >> backup and restore and everything is working fine! >> >> >> >> Best Regards >> Wanderlei >> >> 2015-08-14 9:23 GMT-03:00 Kern Sibbald : >> >>> Hello, >>> >>> Our Bacula Systems gnome gurus have been working hard in the Swiss >>> mountains, and their work is now released as Bacula version 7.2.0. You >>> can find the source code at Source Forge as usual. >>> >>> This version has quite a number of difficult and important bug fixes >>> over version 7.0.5 as well as a good number of new features. I won't >>> attempt to list all the new features here, but suggest that you look at >>> the New Features chapter of the manual. Please note that there may be a >>> few new features documented in the 7.2. section of the manual that were >>> actually in 7.0.5 -- I just ran out of time at the end, so rather than >>> miss a feature, I took the risk to include some already released. >>> >>> This version has not been tested in production yet, so please test it >>> carefully. That said, it is largely based on Bacula Enterprise version >>> 8.2, which is extremely stable and it also has a number of fixes and >>> features from the next, yet unreleased, Enterprise version as well as >>> *all* the Enterprise bug fixes. >>> >>> For certain of the new features, and a couple more yet to come, this >>> version has a new catalog layout, which means that you must do a catalog >>> upgrade (it is relatively simple). As always, please backup your >>> database prior to applying the upgrade procedure. >>> >>> Previously we supplied an update script for only one version. To avoid >>> the proliferation of upgrade scripts in the future, we have settled on a >>> single script (update_bacula_tables), which will upgrade from version >>> 3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format. So >>> the procedure much simpler. >>> As soon as we can update the bacula.org web site to have a sort of more >>> automated download area, we will move our source release to the >>> bacula.org web site and begin furnishing binaries. >>> >>> Many thanks to Bacula Systems for providing the bug fixes and new >>> features. Since the development process in Bacula Systems is going >>> faster (more programmers), we can expect even more features in future >>> versions. >>> >>> You may notice a few license/copyright changes, but these are all very >>> positive for the community version and its future. I will go into it in >>> more detail on this point in a Status Report that will follow this >>> announcement in a few days. >>> >>> Thanks for using Bacula. >>> >>> Best regards, >>> Kern >>> >>> >>> -- >>> ___ >>> 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 > > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Out of virtual tapes
On 8/14/2015 7:28 AM, Radosław Korzeniewski wrote: Hello Ana, 2015-08-03 23:40 GMT+02:00 Ana Emília M. Arruda mailto:emiliaarr...@gmail.com>>: Yes, I think so, for daily full backups. I'm just curious how did you check that Dimitri is making a daily full backups? I have 5 years retentions for my full backups, but they are full monthly backups. For daily and weekly backups, we use incremental and differential types. Well. Let's imagine I backup a single file every day. Every day this file is changing its contents, so what backup level I should use for it (I assume I do not use bacula delta plugin)? You could ask what single file, I can respond a virtual machine disk image. :) That is one reason I switched to installing Bacula client on the VM, rather than backing up the entire VM image on a daily basis. Another reason is that restoring a file to the VM is much quicker and easier with the Bacula client installed on the VM. For my purposes, VM image backups are only useful for archival / off-site backups. Even with the delta plugin, restoring a single file to the VM is still painful. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula version 7.2.0 released
> Job Bandwidth Limitations I have been waiting this feature for a few years. And finally I got it. Thanks a lot! On Fri, Aug 14, 2015 at 4:01 PM, Kern Sibbald wrote: > Hello Wanderlei, > > I am pleased to hear that it is working well for you. There are many new > features and additions nice things like binaries that the project (thanks > to help from Bacula Systems) should be supplying in the future -- some > great features are a bit longer term, but binaries I hoping for in the near > future. > > Thanks the encouragement and for using Bacula. > > Best regards, > Kern > > > On 14.08.2015 14:58, Wanderlei Huttel wrote: > > Hi Kern > > Thank you for having released this new version and congratulations for the > excellent work! > > I've upgraded my system in this morning and I've made some operations of > backup and restore and everything is working fine! > > > > Best Regards > Wanderlei > > 2015-08-14 9:23 GMT-03:00 Kern Sibbald : > >> Hello, >> >> Our Bacula Systems gnome gurus have been working hard in the Swiss >> mountains, and their work is now released as Bacula version 7.2.0. You >> can find the source code at Source Forge as usual. >> >> This version has quite a number of difficult and important bug fixes >> over version 7.0.5 as well as a good number of new features. I won't >> attempt to list all the new features here, but suggest that you look at >> the New Features chapter of the manual. Please note that there may be a >> few new features documented in the 7.2. section of the manual that were >> actually in 7.0.5 -- I just ran out of time at the end, so rather than >> miss a feature, I took the risk to include some already released. >> >> This version has not been tested in production yet, so please test it >> carefully. That said, it is largely based on Bacula Enterprise version >> 8.2, which is extremely stable and it also has a number of fixes and >> features from the next, yet unreleased, Enterprise version as well as >> *all* the Enterprise bug fixes. >> >> For certain of the new features, and a couple more yet to come, this >> version has a new catalog layout, which means that you must do a catalog >> upgrade (it is relatively simple). As always, please backup your >> database prior to applying the upgrade procedure. >> >> Previously we supplied an update script for only one version. To avoid >> the proliferation of upgrade scripts in the future, we have settled on a >> single script (update_bacula_tables), which will upgrade from version >> 3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format. So >> the procedure much simpler. >> As soon as we can update the bacula.org web site to have a sort of more >> automated download area, we will move our source release to the >> bacula.org web site and begin furnishing binaries. >> >> Many thanks to Bacula Systems for providing the bug fixes and new >> features. Since the development process in Bacula Systems is going >> faster (more programmers), we can expect even more features in future >> versions. >> >> You may notice a few license/copyright changes, but these are all very >> positive for the community version and its future. I will go into it in >> more detail on this point in a Status Report that will follow this >> announcement in a few days. >> >> Thanks for using Bacula. >> >> Best regards, >> Kern >> >> >> -- >> ___ >> 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] Duplicate Bacula Log Lines
Hello. If you have two Directors for the same FD then you will have duplicate job logs from this FD. There was a bug in messages handling runtime which caused this. I had the same issue at one of my customer. I do not know if it was fixed. The customer was migrating from Bacula Community into Bacula Enterprise and has two Dir for a short time. Best regards 14 sie 2015 3:02 PM "Wanderlei Huttel" napisał(a): > Hi Radoslaw > > I have 2 directors, but the duplication log lines just happen on machines > like servers that stay 24 hours power on > Users machine that are turned off every day this doesn't happen > > Best Regards > Wanderlei > > 2015-08-14 9:29 GMT-03:00 Radosław Korzeniewski >: > >> Hello, >> >> I see a duplication of logs only for messages generated from Bacula File >> Daemon. So please check you Bacula FD configuration, especially if you have >> more then one Bacula Director defined. >> >> best regards >> >> 2015-07-31 19:03 GMT+02:00 Wanderlei Huttel : >> >>> I've been noticed a few days ago that bacula is duplicating a lot of >>> lines in the log. >>> >>> What should this happening? >>> >>> Below my logs. >>> >>> >>> Thanks Wanderlei >>> >>> 30-Jul 21:30 bacula-dir JobId 1276: Start Backup JobId 1276, >>> Job=Backup_Servidor_Firewall.2015-07-30_21.30.00_16 >>> 30-Jul 21:30 bacula-dir JobId 1276: Using Device "DiscoLocal1" to write. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: DIR and FD clocks differ by 108 >>> seconds, FD automatically compensating. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: DIR and FD clocks differ by 108 >>> seconds, FD automatically compensating. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: shell command: run >>> ClientBeforeJob "/usr/local/bin/backup_mysql_bacula.sh" >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: shell command: run >>> ClientBeforeJob "/usr/local/bin/backup_mysql_bacula.sh" >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> information_schema... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> information_schema... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> cacti... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> cacti... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> curriculum... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> curriculum... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> db_admin... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> db_admin... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> db_qmail... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> db_qmail... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> iptables... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> iptables... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> msnproxy... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> msnproxy... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> mysql... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> mysql... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> squid... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> squid... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> squid_log... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> squid_log... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> squidaccess... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> squidaccess... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> website... Done. >>> 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up >>> website... Done. >>> 30-Jul 21:30 bacula-sd JobId 1276: Elapsed time=00:00:11, Transfer >>> rate=706.4 K Bytes/second >>> 30-Jul 21:30 bacula-sd JobId 1276: Sending spooled attrs to the >>> Director. Despooling 24,355 bytes ... >>> 30-Jul 21:30 bacula-dir JobId 1276: Bacula bacula-dir 7.0.5 (28Jul14): >>> Build OS: x86_64-unknown-linux-gnu debian 7.8 >>> JobId: 1276 >>> Job:Backup_Servidor_Firewall.2015-07-30_21.30.00_16 >>> Backup Level: Differential, since=2015-07-24 22:00:06 >>> Client: "srv_firewall-fd" 7.0.5 (28Jul14) >>> i686-pc-linux-gnu,debian,5.0 >>> FileSet:"FileSet_SRV_Firewall" 2015-07-03 22:00:00 >>> Pool: "Diaria" (From Run Pool override) >>> Catalog:"MyCatalog" (From Client resource) >>> Stora
Re: [Bacula-users] Out of virtual tapes
Hello Radoslow, I was talking about the configurations of the bacula user that originated this thread. And I based my opinion on his pool configuration and list media output. I agree with you that some files are always backed up regardless of whether or not you are using a full backup job. And this is the case of virtual machine disk images. In this case, IMHO there is a trade-off. Do I have enough space for keeping a 1 year retention backups of all my disk images? Is this really necessary for me? I have seen solutions that have a weekly or monthly full backups for VM disk images and daily backup for the data partitions of the virtual machines that are susceptible of changes dieting the week/month. Also, the most cases I had seen that needs a Virtual machine disk image restore are: 1) disaster recover: in this case, the last backup is what we need. Having this backup in more than one place is preferable than having later ones. 2) updates and/or upgrades in the virtual machine configuration do not work: in this case we need a backup immediately before the changes were made. In this case we can take care of always having a full backup before doing any software changes in the virtual machine. Finally, there is a large number of situations and in some of them maybe it could be necessary to have daily full backups. IMHO if we can avoid this, we can save space destined for backups. Best regards, Ana Em sex, 14 de ago de 2015 às 08:28, Radosław Korzeniewski < rados...@korzeniewski.net> escreveu: > Hello Ana, > > 2015-08-03 23:40 GMT+02:00 Ana Emília M. Arruda : > >> Yes, I think so, for daily full backups. >> > > I'm just curious how did you check that Dimitri is making a daily full > backups? > > >> I have 5 years retentions for my full backups, but they are full monthly >> backups. For daily and weekly backups, we use incremental and differential >> types. >> > > Well. Let's imagine I backup a single file every day. Every day this file > is changing its contents, so what backup level I should use for it (I > assume I do not use bacula delta plugin)? You could ask what single file, I > can respond a virtual machine disk image. :) > > best regards > -- > Radosław Korzeniewski > rados...@korzeniewski.net > -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Bacula version 7.2.0 released
Hello Wanderlei, I am pleased to hear that it is working well for you. There are many new features and additions nice things like binaries that the project (thanks to help from Bacula Systems) should be supplying in the future -- some great features are a bit longer term, but binaries I hoping for in the near future. Thanks the encouragement and for using Bacula. Best regards, Kern On 14.08.2015 14:58, Wanderlei Huttel wrote: Hi Kern Thank you for having released this new version and congratulations for the excellent work! I've upgraded my system in this morning and I've made some operations of backup and restore and everything is working fine! Best Regards Wanderlei 2015-08-14 9:23 GMT-03:00 Kern Sibbald: Hello, Our Bacula Systems gnome gurus have been working hard in the Swiss mountains, and their work is now released as Bacula version 7.2.0. You can find the source code at Source Forge as usual. This version has quite a number of difficult and important bug fixes over version 7.0.5 as well as a good number of new features. I won't attempt to list all the new features here, but suggest that you look at the New Features chapter of the manual. Please note that there may be a few new features documented in the 7.2. section of the manual that were actually in 7.0.5 -- I just ran out of time at the end, so rather than miss a feature, I took the risk to include some already released. This version has not been tested in production yet, so please test it carefully. That said, it is largely based on Bacula Enterprise version 8.2, which is extremely stable and it also has a number of fixes and features from the next, yet unreleased, Enterprise version as well as *all* the Enterprise bug fixes. For certain of the new features, and a couple more yet to come, this version has a new catalog layout, which means that you must do a catalog upgrade (it is relatively simple). As always, please backup your database prior to applying the upgrade procedure. Previously we supplied an update script for only one version. To avoid the proliferation of upgrade scripts in the future, we have settled on a single script (update_bacula_tables), which will upgrade from version 3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format. So the procedure much simpler. As soon as we can update the bacula.org web site to have a sort of more automated download area, we will move our source release to the bacula.org web site and begin furnishing binaries. Many thanks to Bacula Systems for providing the bug fixes and new features. Since the development process in Bacula Systems is going faster (more programmers), we can expect even more features in future versions. You may notice a few license/copyright changes, but these are all very positive for the community version and its future. I will go into it in more detail on this point in a Status Report that will follow this announcement in a few days. Thanks for using Bacula. Best regards, Kern -- ___ 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] Adding encryption support to an existing bacula installation?
> Hello Florian, > Could you give more details about what versions of Bacula, Ubuntu and Windows > are using?? > If you build bacula from source, you will just need to rebuild including the > --with-openssl option and then make the necessary configurations in your > director and file daemon files. All your configurations files will be kept. > This should cause no impact in your actual configuration. > Best regards, > Ana > Em sex, 14 de ago de 2015 às 05:47, Florian Splett < florian.spl...@web.de > > escreveu: >> Hello. >> I have a working installation of bacula that takes care of the backups >> in a small network. >> When I first started with bacula and learned how to set it up, I had a >> lot of trouble with including openssl, so I decided to build bacula >> without it. >> Now we want to prepare for storing backups off-site, meaning encryption >> becomes highly important. >> Here a short overview of the situation: >> Ubuntu Server with Director, SD, catalog on postgresql and FD >> 3 Windows machines with FD >> 1 Synology NAS as SD target (accessed via mount) >> new: 1 Synology NAS off-site planned as additional SD target (maybe for >> a second SD, not sure yet.) >> How can I add encryption support to my existing bacula installation? >> Is a rebuild needed? If yes, does it have an impact on the existing >> configurations? I assume you want to use Bacula Data Encryption feature since you are planning to deploy a storage off-site?: http://www.bacula.org/5.2.x-manuals/en/main/main/Data_Encryption.html It's easier to configure but causes more client CPU overhead and you can't loose all your private keys in anyway. Another option is to encrypt only the communication, probably between client and storage: http://www.bacula.org/5.1.x-manuals/en/main/main/Bacula_TLS_Communications.html Create certificates for the machines, configure Bacula to use them, etc. It's been largely discussed in prior posts and there are several tutorials in the internet. Like Ana said yes, your Bacula binaries should be built with Encryption support. Centos and Debian Repositories ones usually does. Regards === Heitor Medrado de Faria - LPIC-III | ITIL-F | Bacula Systems Certified Administrator II Do you need Bacula training? https://www.udemy.com/bacula-backup-software/?couponCode=bacula-list I do Bacula training and deploy in any city of the world. More information: http://bacula.us/ +55 61 8268-4220 Site: http://bacula.us FB: heitor.faria === >> Regards, >> Florian S. >> -- >> ___ >> 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 version 7.2.0 released
Hi Kern Thank you for having released this new version and congratulations for the excellent work! I've upgraded my system in this morning and I've made some operations of backup and restore and everything is working fine! Best Regards Wanderlei 2015-08-14 9:23 GMT-03:00 Kern Sibbald : > Hello, > > Our Bacula Systems gnome gurus have been working hard in the Swiss > mountains, and their work is now released as Bacula version 7.2.0. You > can find the source code at Source Forge as usual. > > This version has quite a number of difficult and important bug fixes > over version 7.0.5 as well as a good number of new features. I won't > attempt to list all the new features here, but suggest that you look at > the New Features chapter of the manual. Please note that there may be a > few new features documented in the 7.2. section of the manual that were > actually in 7.0.5 -- I just ran out of time at the end, so rather than > miss a feature, I took the risk to include some already released. > > This version has not been tested in production yet, so please test it > carefully. That said, it is largely based on Bacula Enterprise version > 8.2, which is extremely stable and it also has a number of fixes and > features from the next, yet unreleased, Enterprise version as well as > *all* the Enterprise bug fixes. > > For certain of the new features, and a couple more yet to come, this > version has a new catalog layout, which means that you must do a catalog > upgrade (it is relatively simple). As always, please backup your > database prior to applying the upgrade procedure. > > Previously we supplied an update script for only one version. To avoid > the proliferation of upgrade scripts in the future, we have settled on a > single script (update_bacula_tables), which will upgrade from version > 3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format. So > the procedure much simpler. > As soon as we can update the bacula.org web site to have a sort of more > automated download area, we will move our source release to the > bacula.org web site and begin furnishing binaries. > > Many thanks to Bacula Systems for providing the bug fixes and new > features. Since the development process in Bacula Systems is going > faster (more programmers), we can expect even more features in future > versions. > > You may notice a few license/copyright changes, but these are all very > positive for the community version and its future. I will go into it in > more detail on this point in a Status Report that will follow this > announcement in a few days. > > Thanks for using Bacula. > > Best regards, > Kern > > > -- > ___ > 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] Duplicate Bacula Log Lines
Hello, I see a duplication of logs only for messages generated from Bacula File Daemon. So please check you Bacula FD configuration, especially if you have more then one Bacula Director defined. best regards 2015-07-31 19:03 GMT+02:00 Wanderlei Huttel : > I've been noticed a few days ago that bacula is duplicating a lot of lines > in the log. > > What should this happening? > > Below my logs. > > > Thanks Wanderlei > > 30-Jul 21:30 bacula-dir JobId 1276: Start Backup JobId 1276, > Job=Backup_Servidor_Firewall.2015-07-30_21.30.00_16 > 30-Jul 21:30 bacula-dir JobId 1276: Using Device "DiscoLocal1" to write. > 30-Jul 21:31 srv_firewall-fd JobId 1276: DIR and FD clocks differ by 108 > seconds, FD automatically compensating. > 30-Jul 21:31 srv_firewall-fd JobId 1276: DIR and FD clocks differ by 108 > seconds, FD automatically compensating. > 30-Jul 21:31 srv_firewall-fd JobId 1276: shell command: run > ClientBeforeJob "/usr/local/bin/backup_mysql_bacula.sh" > 30-Jul 21:31 srv_firewall-fd JobId 1276: shell command: run > ClientBeforeJob "/usr/local/bin/backup_mysql_bacula.sh" > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > information_schema... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > information_schema... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > cacti... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > cacti... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > curriculum... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > curriculum... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > db_admin... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > db_admin... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > db_qmail... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > db_qmail... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > iptables... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > iptables... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > msnproxy... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > msnproxy... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > mysql... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > mysql... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > squid... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > squid... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > squid_log... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > squid_log... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > squidaccess... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > squidaccess... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > website... Done. > 30-Jul 21:31 srv_firewall-fd JobId 1276: ClientBeforeJob: Backing up > website... Done. > 30-Jul 21:30 bacula-sd JobId 1276: Elapsed time=00:00:11, Transfer > rate=706.4 K Bytes/second > 30-Jul 21:30 bacula-sd JobId 1276: Sending spooled attrs to the Director. > Despooling 24,355 bytes ... > 30-Jul 21:30 bacula-dir JobId 1276: Bacula bacula-dir 7.0.5 (28Jul14): > Build OS: x86_64-unknown-linux-gnu debian 7.8 > JobId: 1276 > Job:Backup_Servidor_Firewall.2015-07-30_21.30.00_16 > Backup Level: Differential, since=2015-07-24 22:00:06 > Client: "srv_firewall-fd" 7.0.5 (28Jul14) > i686-pc-linux-gnu,debian,5.0 > FileSet:"FileSet_SRV_Firewall" 2015-07-03 22:00:00 > Pool: "Diaria" (From Run Pool override) > Catalog:"MyCatalog" (From Client resource) > Storage:"StorageLocal1" (From Pool resource) > Scheduled time: 30-Jul-2015 21:30:00 > Start time: 30-Jul-2015 21:30:06 > End time: 30-Jul-2015 21:30:17 > Elapsed time: 11 secs > Priority: 10 > FD Files Written: 80 > SD Files Written: 80 > FD Bytes Written: 7,761,487 (7.761 MB) > SD Bytes Written: 7,770,554 (7.770 MB) > Rate: 705.6 KB/s > Software Compression: 3.5% 1.0:1 > VSS:no > Encryption: no > Accurate: no > Volume name(s): Volume-Diario-0001 > Volume Session Id: 5 > Volume Session Time:1438286880 > Last Volume Bytes: 1,800,774,445 (1.800 GB) > Non-fatal FD errors:0 > SD Errors: 0 > FD termination status: OK > SD termination status: OK > T
[Bacula-users] Bacula version 7.2.0 released
Hello, Our Bacula Systems gnome gurus have been working hard in the Swiss mountains, and their work is now released as Bacula version 7.2.0. You can find the source code at Source Forge as usual. This version has quite a number of difficult and important bug fixes over version 7.0.5 as well as a good number of new features. I won't attempt to list all the new features here, but suggest that you look at the New Features chapter of the manual. Please note that there may be a few new features documented in the 7.2. section of the manual that were actually in 7.0.5 -- I just ran out of time at the end, so rather than miss a feature, I took the risk to include some already released. This version has not been tested in production yet, so please test it carefully. That said, it is largely based on Bacula Enterprise version 8.2, which is extremely stable and it also has a number of fixes and features from the next, yet unreleased, Enterprise version as well as *all* the Enterprise bug fixes. For certain of the new features, and a couple more yet to come, this version has a new catalog layout, which means that you must do a catalog upgrade (it is relatively simple). As always, please backup your database prior to applying the upgrade procedure. Previously we supplied an update script for only one version. To avoid the proliferation of upgrade scripts in the future, we have settled on a single script (update_bacula_tables), which will upgrade from version 3.0.x to version 5.2.x (same as 7.0.x) and to the new 7.2.0 format. So the procedure much simpler. As soon as we can update the bacula.org web site to have a sort of more automated download area, we will move our source release to the bacula.org web site and begin furnishing binaries. Many thanks to Bacula Systems for providing the bug fixes and new features. Since the development process in Bacula Systems is going faster (more programmers), we can expect even more features in future versions. You may notice a few license/copyright changes, but these are all very positive for the community version and its future. I will go into it in more detail on this point in a Status Report that will follow this announcement in a few days. Thanks for using Bacula. Best regards, Kern -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Out of virtual tapes
Hello Ana, 2015-08-03 23:40 GMT+02:00 Ana Emília M. Arruda : > Yes, I think so, for daily full backups. > I'm just curious how did you check that Dimitri is making a daily full backups? > I have 5 years retentions for my full backups, but they are full monthly > backups. For daily and weekly backups, we use incremental and differential > types. > Well. Let's imagine I backup a single file every day. Every day this file is changing its contents, so what backup level I should use for it (I assume I do not use bacula delta plugin)? You could ask what single file, I can respond a virtual machine disk image. :) best regards -- Radosław Korzeniewski rados...@korzeniewski.net -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Adding encryption support to an existing bacula installation?
Hello Florian, Could you give more details about what versions of Bacula, Ubuntu and Windows are using?? If you build bacula from source, you will just need to rebuild including the --with-openssl option and then make the necessary configurations in your director and file daemon files. All your configurations files will be kept. This should cause no impact in your actual configuration. Best regards, Ana Em sex, 14 de ago de 2015 às 05:47, Florian Splett escreveu: > Hello. > > I have a working installation of bacula that takes care of the backups > in a small network. > When I first started with bacula and learned how to set it up, I had a > lot of trouble with including openssl, so I decided to build bacula > without it. > > Now we want to prepare for storing backups off-site, meaning encryption > becomes highly important. > > Here a short overview of the situation: > Ubuntu Server with Director, SD, catalog on postgresql and FD > 3 Windows machines with FD > 1 Synology NAS as SD target (accessed via mount) > > new: 1 Synology NAS off-site planned as additional SD target (maybe for > a second SD, not sure yet.) > > How can I add encryption support to my existing bacula installation? > Is a rebuild needed? If yes, does it have an impact on the existing > configurations? > > Regards, > > Florian S. > > > -- > ___ > 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] Adding encryption support to an existing bacula installation?
Hello. I have a working installation of bacula that takes care of the backups in a small network. When I first started with bacula and learned how to set it up, I had a lot of trouble with including openssl, so I decided to build bacula without it. Now we want to prepare for storing backups off-site, meaning encryption becomes highly important. Here a short overview of the situation: Ubuntu Server with Director, SD, catalog on postgresql and FD 3 Windows machines with FD 1 Synology NAS as SD target (accessed via mount) new: 1 Synology NAS off-site planned as additional SD target (maybe for a second SD, not sure yet.) How can I add encryption support to my existing bacula installation? Is a rebuild needed? If yes, does it have an impact on the existing configurations? Regards, Florian S. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users