[Bacula-users] copy jobs
Hello, is it possible to setup copy job for a single client so that all the jobs data is stored on two different volumes? But without specifying an extra pool for such a client. If I specify an extra pool, I can specify PoolUncopiedJobs. That works but not for a single client only. If I specify e.g. Client as a selection rule, I'm lost in a recursion because all copy jobs are selected for copy next time as they match a client name. So any change here? -- Lukáš Hejtmánek -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Deadlock error
Hi Ana, Did you monitor resource usage during the backups? The list of files generated for accurate backups are kept in memory (by both director and client), so this should cause resource use (CPU, memory, etc.) to increase in both hosts. I did monitor these items earlier, but did not notice a huge drop in usage in these items. However, I was using Zabbix to monitor which takes a reading every so many minutes. It's possible it didn't take a reading when the problem occurred. I should've used something like top instead or VMware's performance tools. I'll take a look at the graphs again...I may have missed it. However, as usual your suggestions helped! I increased the amount of memory on Director and added more CPUs. I also reduced the number of concurrent jobs from 50 to 25. So far, two days of incremental backups have not produced any deadlock errors. All my backups finished successfully. Thank you so much for the help! (again) :-) Your advice is always, always so helpful. -craig On Sat, Aug 8, 2015 at 4:11 PM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hi Craig, On Fri, Aug 7, 2015 at 3:49 PM, Craig Shiroma shiroma.crai...@gmail.com wrote: Hi Ana, Thank you for the suggestion! You're welcome! I'll look into adding more CPU and memory to director, although I didn't see much of an impact on either between a non-accurate run and an accurate run. For example, there was large depletion of available memory, no swapping, or high load. Did you monitor resource usage during the backups? The list of files generated for accurate backups are kept in memory (by both director and client), so this should cause resource use (CPU, memory, etc.) to increase in both hosts. I did add more memory to the catalog server and turned Accurate back on for the same hosts. I had no deadlocks. Last night was mostly Fulls, though. Not sure if that makes a difference. Would you know if Bacula would uses less resources when fulls are run because it is going to back up everything anyway and no comparison of files needs to be made (I'm guessing)? When a full is done, does Bacula still need to keep a list of the files in memory for hosts using Accurate backups? My first thought is no. Mine too. When using accurate backups, the amount of resources used should be noticed when running incremental, differential and full+basejobs backups. Thanks again for the help! Your posts are always so helpful. Thank you too! Best regards, Ana -craig On Thu, Aug 6, 2015 at 3:37 PM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hello Craig, In one of your posts you mentioned Segmentation violation in the director host. Accurate backups requires more resources than normal ones. Have you checked if CPU and memory resources are enough in director and the clients that are configured for using accurate mode? Best regards, Ana On Thu, Aug 6, 2015 at 5:36 PM, Craig Shiroma shiroma.crai...@gmail.com wrote: Thanks Kern! I'll bring in a DBA on our side to have a look. Would you have any thoughts on this question posed earlier? 3. Why is Bacula spinning off a new job right away after it detects the deadlock for each affected job instead of waiting until the rescheduled job runs? I verified that there were no duplicate jobs in the queue before the backups started running, no jobs were running before the start of the backups, and I did not start any of these backups manually to cause a second job to appear. This happened on both nights I ran with Accurate turned On on the hosts that had failed backups because of the deadlock. Regards, -craig On Thu, Aug 6, 2015 at 9:48 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 21:44, Craig Shiroma wrote: Hi Kern, Thank you for the info! We're using MySQL 5.6 Percona Server, Release 68.0, Revision 656. Would this setting cause the problem? innodb_lock_wait_timeout = 100 Is it too high or too low or has no bearing on the problem? Sorry, I am a Bacula programmer, and I do not know much about databases -- especially MySQL since I use PostgreSQL. PostgreSQL is harder to install and a bit harder to configure than MySQL, but it performs much better. Thanks again, -craig On Thu, Aug 6, 2015 at 9:26 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 18:46, Bryn Hughes wrote: I think what Kern is getting at is that your database is what threw the error, not Bacula. Whatever DB you are using is what is having the issue. Yes. That is exactly what I was implying. The rest of this is directed to Craig: If you are using MariaDB (I have no indication that you are), please be aware that it may be a very good database, maybe even better than MySQL, but Bacula is built and tested against MySQL, and if you use binaries that were built for MySQL, you could run into problems by using MariaDB. Even if your binaries were explicitly built with MariaDB, it
Re: [Bacula-users] Deadlock error
Hi Kelvin, Thank you for the info and help! Good information to keep in mind. I think I found the root of the problem thanks to everyone. See my reply to Ana. Thanks again for the post. It's much appreciated. -craig On Fri, Aug 7, 2015 at 10:46 AM, Kelvin Minter kb.min...@gmail.com wrote: MyISAM is terrible for transactions. If the deadlock is happening because of table locking then switching the engine to InnoDB might help your problem. MyISAM locks the entire table while InnoDB only locks the rows it is updating. Check out the link below. http://stackoverflow.com/questions/20148/myisam-versus-innodb On Thu, Aug 6, 2015 at 8:37 PM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hello Craig, In one of your posts you mentioned Segmentation violation in the director host. Accurate backups requires more resources than normal ones. Have you checked if CPU and memory resources are enough in director and the clients that are configured for using accurate mode? Best regards, Ana On Thu, Aug 6, 2015 at 5:36 PM, Craig Shiroma shiroma.crai...@gmail.com wrote: Thanks Kern! I'll bring in a DBA on our side to have a look. Would you have any thoughts on this question posed earlier? 3. Why is Bacula spinning off a new job right away after it detects the deadlock for each affected job instead of waiting until the rescheduled job runs? I verified that there were no duplicate jobs in the queue before the backups started running, no jobs were running before the start of the backups, and I did not start any of these backups manually to cause a second job to appear. This happened on both nights I ran with Accurate turned On on the hosts that had failed backups because of the deadlock. Regards, -craig On Thu, Aug 6, 2015 at 9:48 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 21:44, Craig Shiroma wrote: Hi Kern, Thank you for the info! We're using MySQL 5.6 Percona Server, Release 68.0, Revision 656. Would this setting cause the problem? innodb_lock_wait_timeout = 100 Is it too high or too low or has no bearing on the problem? Sorry, I am a Bacula programmer, and I do not know much about databases -- especially MySQL since I use PostgreSQL. PostgreSQL is harder to install and a bit harder to configure than MySQL, but it performs much better. Thanks again, -craig On Thu, Aug 6, 2015 at 9:26 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 18:46, Bryn Hughes wrote: I think what Kern is getting at is that your database is what threw the error, not Bacula. Whatever DB you are using is what is having the issue. Yes. That is exactly what I was implying. The rest of this is directed to Craig: If you are using MariaDB (I have no indication that you are), please be aware that it may be a very good database, maybe even better than MySQL, but Bacula is built and tested against MySQL, and if you use binaries that were built for MySQL, you could run into problems by using MariaDB. Even if your binaries were explicitly built with MariaDB, it may not be compatible with the way Bacula works. Bacula has a tendency to push databases to the extreme, and it works well with MySQL and PostgreSQL, but possibly not with other databases. I bring up MariaDB because it has been mentioned in another posting to this list. I would be very surprised if your problem has anything to do with Accurate -- the database routines know nothing about accurate and none of the data is different. It is more likely due to the VM environment or to some build or version problem with MySQL (or MariaDB). Best regards, Kern Bryn On 2015-08-06 09:11 AM, Craig Shiroma wrote: Hi Kern, Thank you very much for the reply! Would you have any suggestions on what may be causing this problem or how I can debug it? Obviously, I'm encountering deadlocks when accurate backup runs on some of our hosts and we want to use accurate backup on all of our hosts if possible. Warmest regards, -craig On Thu, Aug 6, 2015 at 12:11 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 10:15, Craig Shiroma wrote: Hello again, I just thought I'd update this post with more information in hopes of getting some explanation for the deadlocks. I ran with Accurate backup on our test VMs (RHEL) for a couple of days and got the same errors on some VMs that were running accurate and some that were not. These hosts were running concurrently. I would say 90% of the hosts that were configured to use Accurate finished successfully. However, there were a few that failed with the deadlock error -- some that were configured to use accurate and some that were not configured to use accurate. Also, on all of these, a second job started for each of the affected hosts right after Bacula detected the deadlock even though it said a reschedule would happen 3600 seconds later (the 3600 seconds is correct). Tonight, I disabled accurate on all
Re: [Bacula-users] Deadlock error
Hi Josip, Thank you for the advice and for looking that up in the mysql docs. That was pretty much the error I was getting. See my reply to Ana. Again, thank you for the help. I really appreciate it. -craig On Thu, Aug 6, 2015 at 9:26 PM, Josip Deanovic djosip+n...@linuxpages.net wrote: On Thursday 2015-08-06 09:44:06 Craig Shiroma wrote: Hi Kern, Thank you for the info! We're using MySQL 5.6 Percona Server, Release 68.0, Revision 656. Would this setting cause the problem? innodb_lock_wait_timeout = 100 Is it too high or too low or has no bearing on the problem? Hi! http://dev.mysql.com/doc/refman/5.0/en/innodb-parameters.html#sysvar_innodb_lock_wait_timeout Documentation says: -BEGIN- The timeout in seconds an InnoDB transaction may wait for a row lock before giving up. The default value is 50 seconds. A transaction that tries to access a row that is locked by another InnoDB transaction will hang for at most this many seconds before issuing the following error: ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction When a lock wait timeout occurs, the current statement is not executed. The current transaction is not rolled back. -END- So I wouldn't say that decreasing this value would change anything in your case. -- 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] copy jobs
Hello Lukas, I was wondering if this could be solved using cloned copy jobs :) Best regards, Ana On Mon, Aug 10, 2015 at 11:36 AM, Lukas Hejtmanek xhejt...@ics.muni.cz wrote: Hello, is it possible to setup copy job for a single client so that all the jobs data is stored on two different volumes? But without specifying an extra pool for such a client. If I specify an extra pool, I can specify PoolUncopiedJobs. That works but not for a single client only. If I specify e.g. Client as a selection rule, I'm lost in a recursion because all copy jobs are selected for copy next time as they match a client name. So any change here? -- Lukáš Hejtmánek -- ___ 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 daemon message- where did it come from?
Hello Michael, It seems not to be an issue with Bacula. Instead, maybe this mail had been queued in your system and relayed at a later time. Best regards, Ana On Mon, Aug 10, 2015 at 11:01 AM, Michael Schwager mschwa...@mochotrading.com wrote: Hello, Yesterday (Sunday) I received an email from bacula-dir but I don't know why. It contains old authentication error messages from a week ago (see below) that I'd rectified on the 03 August later in the day. I don't know why I received this message now, and I'd like to prevent it from recurring. ...It makes my boss anxious. :-) The mail was sent at 11:00 UTC. There is no other job scheduled in bacula-dir or in cron that would take place at the time this email was sent. My maillog is consistent with that. I have verified that the mail came from bacula-dir I wonder if a start of the bacula director would send an email, but I just tried it and it did not send the email again (see the cron operations that are performed, below). Does bacula-dir send error messages that are = 1 week old, upon startup? At 11:00 UTC my system performs the following from cron, in order to perform a binary backup: systemctl stop bacula-dir systemctl stop bacula-sd systemctl stop bacula-fd systemctl stop mysqld (copy database dir) systemctl start mysqld systemctl start bacula-fd systemctl stop bacula-sd systemctl stop bacula-dir Thanks for any help. *- Mike Schwager* * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 312-646-4783 Phone312-637-0011 312-637-0011 Cell312-957-9804 312-957-9804 Fax* -- Forwarded message -- From: Bacula backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.com 02-Aug 22:24 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director unable to authenticate with Storage daemon at -backup-01.example.com:9103 http://backup-01.example.com:9103. Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the SD or SD networking messed up (restart daemon). Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 03-Aug 02:38 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director unable to authenticate with Storage daemon at http://backup-01.example.com:9103;. Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the SD or SD networking messed up (restart daemon). Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 03-Aug 02:49 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director unable to authenticate with Storage daemon at http://backup-01.example.com:9103;. Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the SD or SD networking messed up (restart daemon). Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. This message is for the named person(s) use only. It may contain confidential proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Mocho Trading LLC reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. -- ___ 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] Deadlock error
Hi Craig, Good news! You're welcome (again) :). And thank you for your feedback. They are always useful. Best regards, Ana On Mon, Aug 10, 2015 at 3:35 PM, Craig Shiroma shiroma.crai...@gmail.com wrote: Hi Ana, Did you monitor resource usage during the backups? The list of files generated for accurate backups are kept in memory (by both director and client), so this should cause resource use (CPU, memory, etc.) to increase in both hosts. I did monitor these items earlier, but did not notice a huge drop in usage in these items. However, I was using Zabbix to monitor which takes a reading every so many minutes. It's possible it didn't take a reading when the problem occurred. I should've used something like top instead or VMware's performance tools. I'll take a look at the graphs again...I may have missed it. However, as usual your suggestions helped! I increased the amount of memory on Director and added more CPUs. I also reduced the number of concurrent jobs from 50 to 25. So far, two days of incremental backups have not produced any deadlock errors. All my backups finished successfully. Thank you so much for the help! (again) :-) Your advice is always, always so helpful. -craig On Sat, Aug 8, 2015 at 4:11 PM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hi Craig, On Fri, Aug 7, 2015 at 3:49 PM, Craig Shiroma shiroma.crai...@gmail.com wrote: Hi Ana, Thank you for the suggestion! You're welcome! I'll look into adding more CPU and memory to director, although I didn't see much of an impact on either between a non-accurate run and an accurate run. For example, there was large depletion of available memory, no swapping, or high load. Did you monitor resource usage during the backups? The list of files generated for accurate backups are kept in memory (by both director and client), so this should cause resource use (CPU, memory, etc.) to increase in both hosts. I did add more memory to the catalog server and turned Accurate back on for the same hosts. I had no deadlocks. Last night was mostly Fulls, though. Not sure if that makes a difference. Would you know if Bacula would uses less resources when fulls are run because it is going to back up everything anyway and no comparison of files needs to be made (I'm guessing)? When a full is done, does Bacula still need to keep a list of the files in memory for hosts using Accurate backups? My first thought is no. Mine too. When using accurate backups, the amount of resources used should be noticed when running incremental, differential and full+basejobs backups. Thanks again for the help! Your posts are always so helpful. Thank you too! Best regards, Ana -craig On Thu, Aug 6, 2015 at 3:37 PM, Ana Emília M. Arruda emiliaarr...@gmail.com wrote: Hello Craig, In one of your posts you mentioned Segmentation violation in the director host. Accurate backups requires more resources than normal ones. Have you checked if CPU and memory resources are enough in director and the clients that are configured for using accurate mode? Best regards, Ana On Thu, Aug 6, 2015 at 5:36 PM, Craig Shiroma shiroma.crai...@gmail.com wrote: Thanks Kern! I'll bring in a DBA on our side to have a look. Would you have any thoughts on this question posed earlier? 3. Why is Bacula spinning off a new job right away after it detects the deadlock for each affected job instead of waiting until the rescheduled job runs? I verified that there were no duplicate jobs in the queue before the backups started running, no jobs were running before the start of the backups, and I did not start any of these backups manually to cause a second job to appear. This happened on both nights I ran with Accurate turned On on the hosts that had failed backups because of the deadlock. Regards, -craig On Thu, Aug 6, 2015 at 9:48 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 21:44, Craig Shiroma wrote: Hi Kern, Thank you for the info! We're using MySQL 5.6 Percona Server, Release 68.0, Revision 656. Would this setting cause the problem? innodb_lock_wait_timeout = 100 Is it too high or too low or has no bearing on the problem? Sorry, I am a Bacula programmer, and I do not know much about databases -- especially MySQL since I use PostgreSQL. PostgreSQL is harder to install and a bit harder to configure than MySQL, but it performs much better. Thanks again, -craig On Thu, Aug 6, 2015 at 9:26 AM, Kern Sibbald k...@sibbald.com wrote: On 06.08.2015 18:46, Bryn Hughes wrote: I think what Kern is getting at is that your database is what threw the error, not Bacula. Whatever DB you are using is what is having the issue. Yes. That is exactly what I was implying. The rest of this is directed to Craig: If you are using MariaDB (I have no indication that you are), please be aware that it may be a very good database, maybe
Re: [Bacula-users] Backup finished, but Fatal error: Network error with FD/Connection reset by peer
- Original Message - From: Josh Fisher jfis...@pvct.com To: bacula-users@lists.sourceforge.net Sent: Friday, August 7, 2015 2:47:21 PM Subject: Re: [Bacula-users] Backup finished, but Fatal error: Network error with FD/Connection reset by peer Fyi, version 7.x of the client daemon added progress data. The FD sends progress data to the Dir every 30 seconds. In version 5.x the Dir - FD connection sat idle during a backup. If your Windows FDs are 5.x then that could explain why they fail on the same network where the other FDs do not. Hello Josh, thank you very much for your very insightful input. I'l try to implement the keepalive's this week and we will upgrade our FD's on windows to the latest 7.x. I'l report back on how it goes, but it'l take some time. Thanks, Best Ray -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] bsmtp failing to connect to mail server
On 8/7/2015 6:15 PM, Jerry Lowry wrote: All, I have recently setup two separate bacula servers on two subnets. They were using one server and going through the firewall for one of the subnets. The previous configuration worked well but for security reasons and speed I separated them. Along with this change the company decided to move from an inhouse email server to gmail. Since the move to gmail I have not been able to get the bsmtp configuration to work. I have tried to use gmail but it requires tls. Jul 20 10:26:59 distress bacula-dir: 20-Jul 10:26 Message delivery ERROR: Mail prog: bsmtp: bsmtp.c:145 Fatal malformed reply from smtp.googlemail.com http://smtp.googlemail.com: 530 5.7 .0 Must issue a STARTTLS command first. b9sm14093516ioj.6 - gsmtp So, I have configured postfix/cyrus on the backup server just to send email. The problem I get from bsmtp now is that it can not connect to the mail server. [root@kilchis bin]# /usr/bacula/bin/bsmtp -d 25 -h kilchis.server.com http://kilchis.server.com -f \\(Bacula\) \no-re...@edt.com mailto:no-re...@edt.com\\ -s \Bacula daemon message\ r...@server.com mailto:r...@server.com test message bsmtp: bsmtp.c:338-0 Debug level = 25 bsmtp: bsmtp.c:346-0 host=kilchis.server.com http://kilchis.server.com bsmtp: bsmtp.c:356-0 subject=Bacula bsmtp: bsmtp.c:432-0 My hostname is: kilchis bsmtp: bsmtp.c:456-0 From addr=(Bacula) bsmtp: bsmtp.c:514-0 Failed to connect to mailhost kilchis.server.com http://kilchis.server.com What does postfix log to maillog when bsmtp fails? I can send mail from the command prompt and it works just fine. What am I missing? thanks -- ___ 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 daemon message- where did it come from?
Hello, Yesterday (Sunday) I received an email from bacula-dir but I don't know why. It contains old authentication error messages from a week ago (see below) that I'd rectified on the 03 August later in the day. I don't know why I received this message now, and I'd like to prevent it from recurring. ...It makes my boss anxious. :-) The mail was sent at 11:00 UTC. There is no other job scheduled in bacula-dir or in cron that would take place at the time this email was sent. My maillog is consistent with that. I have verified that the mail came from bacula-dir I wonder if a start of the bacula director would send an email, but I just tried it and it did not send the email again (see the cron operations that are performed, below). Does bacula-dir send error messages that are = 1 week old, upon startup? At 11:00 UTC my system performs the following from cron, in order to perform a binary backup: systemctl stop bacula-dir systemctl stop bacula-sd systemctl stop bacula-fd systemctl stop mysqld (copy database dir) systemctl start mysqld systemctl start bacula-fd systemctl stop bacula-sd systemctl stop bacula-dir Thanks for any help. *- Mike Schwager* * Linux Network Engineer, Mocho Trading LLC* * 312-646-4783 Phone312-637-0011 Cell312-957-9804 Fax* -- Forwarded message -- From: Bacula backup@ example .com Date: Sun, Aug 9, 2015 at 6:00 AM Subject: Bacula daemon message To: it@ example.com 02-Aug 22:24 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director unable to authenticate with Storage daemon at -backup-01.example.com:9103 http://backup-01.example.com:9103. Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the SD or SD networking messed up (restart daemon). Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 03-Aug 02:38 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director unable to authenticate with Storage daemon at http://backup-01.example.com:9103;. Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the SD or SD networking messed up (restart daemon). Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. 03-Aug 02:49 bacula-dir JobId 0: Fatal error: authenticate.c:114 Director unable to authenticate with Storage daemon at http://backup-01.example.com:9103;. Possible causes: Passwords or names not the same or Maximum Concurrent Jobs exceeded on the SD or SD networking messed up (restart daemon). Please see http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION0026 for help. -- This message is for the named person(s) use only. It may contain confidential proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Mocho Trading LLC reserves the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. -- ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
