[bareos-users]
Hi, I found a misbehaviour (I don't want to say a bug): I used erroneously the following fileset parameter: file = "D:\\Directory" bareos services start without error, estimate works like expected, backup runs without error, but restore isn't possible: If I try to restore with the web gui bareos-dir hangs often (not every time), if it doesn't crash I get an empty file list (see attachment). bconsole shows files like: D:\Directory/Dir1/Dir2/File.txt and I can't change the directory. I think the problem is file option parsing. Bareos shouldn't accept the backslash. Stefan -- *CaC, Computer and Communication* Inhaber Stefan Klatt End-2-End Senior Network Consultant Triftstrasse 9 60528 Frankfurt Germany USt-IdNr.: DE260461592 Tel.: +49-(0)172-6807809 Tel.: +49-(0)69-67808-900 Fax: +49-(0)69-67808-837 Email: stefan.kl...@cac-netzwerk.de Profil: http://www.cac-netzwerk.de/profil -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
[bareos-users] [Bareos-users] NDMP Cluster Aware aggregates & volumes effective home
Hi All, Now I use Bareos for 9 months to backup NetApp Cluster DOT via NDMP, I am still hoping some kind of enhancement for Bareos around "clustered filers". Via bconsole "status client myfiler" we can have the list of aggregates and volumes currently available on a node, even if I am not sure Bareos knows how to make the difference between aggregates and volumes. Could it be possible to build a pre-run script to enable or disable a job when schedule times arises? Could it be possible that all fileset would be declared once on tis default home node with chained "paired client" (for more than 2 nodes clusters) where it could be found as alternate when it is not default homed ? Regards, Denis -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] NDMP with more than 8 incrementals causes director to crash
Hello, I recently went into an "issue" I solved just by learning more on NDMP protocol and limits. I use FreeBSD 10.2 with Bareos 15.2.2 with NDMP enabled. I later ran the Director with debug, found my error and corrected it. I adjusted the configuration to run "Full" each first saturday of month, "Differential" the other saturday of th month and "Incremental" all other days. I think crashing the director is not well suited to mis-configuration/understanding of NDMP. Here is the log I received after enabling debug mode BAREOS interrupted by signal 11: Segmentation violation Kaboom! bareos-dir, bkbad01-dir got signal 11 - Segmentation violation. Attempting traceback. Kaboom! exepath=/usr/local/sbin/ Calling: /usr/local/sbin/btraceback /usr/local/sbin/bareos-dir 59232 /var/db/bareos It looks like the traceback worked... Dumping: /var/db/bareos/bkbad01-dir.59232.bactrace Fatal error: NDMP dump format doesn't support more than 8 incrementals, please run a Differential or a Full Backup Backtrace is Attempt to dump locks threadid=0x805c50400 max=0 current=-1 threadid=0x80587c400 max=1 current=-1 threadid=0x80504c400 max=1 current=-1 threadid=0x804007c00 max=1 current=-1 threadid=0x804007400 max=0 current=-1 threadid=0x804007800 max=2 current=-1 threadid=0x804007000 max=0 current=-1 threadid=0x804006400 max=1 current=-1 Attempt to dump current JCRs. njcrs=4 threadid=0x804006400 JobId=0 JobStatus=R jcr=0x8041b9c28 name=*JobMonitor*.2016-08-25_10.18.10_01 threadid=0x804006400 killable=0 JobId=0 JobStatus=R jcr=0x8041b9c28 name=*JobMonitor*.2016-08-25_10.18.10_01 use_count=1 JobType=I JobLevel= sched_time=25-Aug-2016 10:18 start_time=25-Aug-2016 10:18 end_time=01-Jan-1970 01:00 wait_time=01-Jan-1970 01:00 db=0x0 db_batch=0x0 batch_started=0 threadid=0x804007c00 JobId=0 JobStatus=R jcr=0x805434c28 name=*StatisticsCollector*.2016-08-25_10.18.10_02 threadid=0x804007c00 killable=0 JobId=0 JobStatus=R jcr=0x805434c28 name=*StatisticsCollector*.2016-08-25_10.18.10_02 use_count=1 JobType=I JobLevel= sched_time=25-Aug-2016 10:18 start_time=25-Aug-2016 10:18 end_time=01-Jan-1970 01:00 wait_time=01-Jan-1970 01:00 db=0x8054601a8 db_batch=0x0 batch_started=0 B_DB=0x8054601a8 db_name=bareos db_user=bareos connected=true cmd="SELECT DumpLevel FROM NDMPLevelMap WHERE ClientId='3' AND FileSetId='37' AND FileSystem='/cifs01/cifs01_vol1'" changes=0 RWLOCK=0x8054601b0 w_active=0 w_wait=0 threadid=0x80504c400 JobId=0 JobStatus=R jcr=0x805830c28 name=-Console-.2016-08-25_10.26.29_03 threadid=0x80504c400 killable=0 JobId=0 JobStatus=R jcr=0x805830c28 name=-Console-.2016-08-25_10.26.29_03 use_count=1 JobType=U JobLevel= sched_time=25-Aug-2016 10:26 start_time=25-Aug-2016 10:26 end_time=01-Jan-1970 01:00 wait_time=01-Jan-1970 01:00 db=0x805851c28 db_batch=0x0 batch_started=0 B_DB=0x805851c28 db_name=bareos db_user=bareos connected=true cmd="db_init_database first time " changes=0 RWLOCK=0x805851c30 w_active=0 w_wait=0 threadid=0x80587c400 JobId=1590 JobStatus=f jcr=0x805831828 name=JOB-NDMP-FULL-IC1-CIFS01-VOL1.2016-08-25_10.37.42_04 threadid=0x80587c400 killable=1 JobId=1590 JobStatus=f jcr=0x805831828 name=JOB-NDMP-FULL-IC1-CIFS01-VOL1.2016-08-25_10.37.42_04 use_count=2 JobType=B JobLevel=I sched_time=25-Aug-2016 10:37 start_time=25-Aug-2016 10:37 end_time=01-Jan-1970 01:00 wait_time=01-Jan-1970 01:00 db=0x8054601a8 db_batch=0x0 batch_started=0 B_DB=0x8054601a8 db_name=bareos db_user=bareos connected=true cmd="SELECT DumpLevel FROM NDMPLevelMap WHERE ClientId='3' AND FileSetId='37' AND FileSystem='/cifs01/cifs01_vol1'" changes=0 RWLOCK=0x8054601b0 w_active=0 w_wait Regards, Denis -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [bareos-users] Client offline - possibility to skip backup instead of getting an error?
On lundi, 5 septembre 2016 00.30:20 h CEST Daniel wrote: > Hi, > > i use bareos to backup some webservers, but also some computers. The pcs > aren't 24/7 online, so sometimes bareos tries to backup them und throws an > error. (Warning: bsock_tcp.c:128 Could not connect to Client: titan-fd on > name:9102. ERR=Keine Route zum Zielrechner Retrying ... > Fatal error: bsock_tcp.c:134 Unable to connect to Client: titan-fd on > name:9102. ERR=Unterbrechung wÀhrend des Betriebssystemaufrufs). I want to > change the behaviour, so that I won't get an error. Instead of that bareos > should check, if the client is available. If he is, the backup can be done > and if not, bareos should try it x hours later again, without throwing an > error. Only if during y days no backup could be done, bareos should throw > an error. Is there any posssibility to do that? > Which solution choose other users with similar problems? I use Runscript with before and have script that ping the target host. if not present I'm using the retry on error instruction to retry during 4 times in the next 4 hours. Have a look at http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirJobRun Have fun -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.7.2-1-default x86_64 GNU/Linux, nvidia: 370.23 Qt: 5.6.1, KDE Frameworks: 5.25.0, Plasma: 5.7.4, kmail2 5.3.0 (QtWebEngine) -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[bareos-users] Client offline - possibility to skip backup instead of getting an error?
Hi, i use bareos to backup some webservers, but also some computers. The pcs aren't 24/7 online, so sometimes bareos tries to backup them und throws an error. (Warning: bsock_tcp.c:128 Could not connect to Client: titan-fd on name:9102. ERR=Keine Route zum Zielrechner Retrying ... Fatal error: bsock_tcp.c:134 Unable to connect to Client: titan-fd on name:9102. ERR=Unterbrechung wÀhrend des Betriebssystemaufrufs). I want to change the behaviour, so that I won't get an error. Instead of that bareos should check, if the client is available. If he is, the backup can be done and if not, bareos should try it x hours later again, without throwing an error. Only if during y days no backup could be done, bareos should throw an error. Is there any posssibility to do that? Which solution choose other users with similar problems? -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to bareos-users+unsubscr...@googlegroups.com. To post to this group, send email to bareos-users@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
