Re: [Bacula-users] Bacula in the cloud

2016-10-19 Thread Roberts, Ben 
The documentation is outdated and this limit was removed (or perhaps vastly 
increased?) somewhere around the 7 mark. I’ve had jobs running a lot longer 
since upgrading.

In branch-5.2: 
http://www.bacula.org/git/cgit.cgi/bacula/tree/bacula/src/lib/bnet.c#n784
bsock->timeout = 60 * 60 * 6 * 24;   /* 6 days timeout */

In branch-7.0 this line is removed.

(Unfortunately I can’t see a way to get a direct link from cgit directly to a 
line at a particular commit.)

Regards,
Ben Roberts

From: Clark, Patti [mailto:clar...@ornl.gov]
Sent: 18 October 2016 22:29
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula in the cloud

From Bacula’s main.pdf documentation:

Max Run Time =  The time specifies the maximum allowed time that a job 
may run, counted from when the job starts, (not necessarily the same as when 
the job was scheduled).
By default, the the watchdog thread will kill any Job that has run more than 6 
days. The maximum watchdog timeout is independent of MaxRunTime and cannot be 
changed.


Patti Clark
Linux System Administrator
R&D Systems Support Oak Ridge National Laboratory

From: Josip Deanovic 
mailto:djosip+n...@linuxpages.net>>
Date: Tuesday, October 18, 2016 at 4:06 PM
To: 
"bacula-users@lists.sourceforge.net" 
mailto:bacula-users@lists.sourceforge.net>>
Subject: Re: [Bacula-users] Bacula in the cloud

On Tuesday 2016-10-18 12:34:08 Jason Voorhees wrote:
Thank you all for your responses.
I'll take a look at Bacula systems' whitepaper to see what they're
talking about. Meanwhile I'll explore some of the alternatives
discussed on this thread like copying files with scripts and making a
replica on SpiderOak or anything similar.
I hope we can have an interesting solution for this "problem" in the
near future.


Hi Jason!

You have said that "Bacula can't run jobs for so long without modifying
source code and recompiling".

What did you mean by that and can you give an example of the problem
you have experienced?

I am asking because I am not aware of the bacula's job duration related
limitations.

--
Josip Deanovic

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! 
http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

This email and any files transmitted with it contain confidential and 
proprietary information and is solely for the use of the intended recipient.
If you are not the intended recipient please return the email to the sender and 
delete it from your computer and you must not use, disclose, distribute, copy, 
print or rely on this email or its contents.
This communication is for informational purposes only.
It is not intended as an offer or solicitation for the purchase or sale of any 
financial instrument or as an official confirmation of any transaction.
Any comments or statements made herein do not necessarily reflect those of GSA 
Capital.
GSA Capital Partners LLP is authorised and regulated by the Financial Conduct 
Authority and is registered in England and Wales at Stratton House, 5 Stratton 
Street, London W1J 8LA, number OC309261.
GSA Capital Services Limited is registered in England and Wales at the same 
address, number 5320529.
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula in the cloud

2016-10-19 Thread Josip Deanovic 
On Wednesday 2016-10-19 06:41:53 Roberts, Ben wrote:
> The documentation is outdated and this limit was removed (or perhaps
> vastly increased?) somewhere around the 7 mark. I’ve had jobs running a
> lot longer since upgrading.
> 
> In branch-5.2:
> http://www.bacula.org/git/cgit.cgi/bacula/tree/bacula/src/lib/bnet.c#n7
> 84 bsock->timeout = 60 * 60 * 6 * 24;   /* 6 days timeout */
> 
> In branch-7.0 this line is removed.
> 
> (Unfortunately I can’t see a way to get a direct link from cgit directly
> to a line at a particular commit.)
> 
> Regards,
> Ben Roberts


Great.
Thanks for the info.

-- 
Josip Deanovic

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Re: [Bacula-users] Bacula in the cloud

2016-10-19 Thread Kern Sibbald 

  
  
On 10/19/2016 08:41 AM, Roberts, Ben
  wrote:


  
  
  
  
The
documentation is outdated and this limit was removed (or
perhaps vastly increased?) somewhere around the 7 mark. I’ve
had jobs running a lot longer since upgrading.
 
In
branch-5.2:
http://www.bacula.org/git/cgit.cgi/bacula/tree/bacula/src/lib/bnet.c#n784
bsock->timeout = 60 * 60 * 6 *
24;   /* 6 days timeout */
 
In
branch-7.0 this line is removed.
  


Well, I am not really sure that it was removed, since I would say
that it was replaced.  The current bsock timeout is 200 days.

Best regards,
Kern



  

 
(Unfortunately
I can’t see a way to get a direct link from cgit directly to
a line at a particular commit.)
 

  Regards,
  Ben
  Roberts

 

  
From: Clark, Patti [mailto:clar...@ornl.gov]

Sent: 18 October 2016 22:29
To: bacula-users@lists.sourceforge.net
Subject: Re: [Bacula-users] Bacula in the cloud
  

 
From Bacula’s main.pdf documentation:
 
Max Run Time =

Re: [Bacula-users] Multiple autochanger devices

2016-10-19 Thread Josh Fisher 

On 10/18/2016 11:31 AM, Eddie Appel wrote:
>
> Hi all,
>
> Looking for a bit of suggestion or direction here. Keep in mind, RTFM 
> is a valid response so long as you provide some hints as to which M to 
> R where. 😀
>
> I have a pretty straight forward setup using bacula 7 on centos 6 and 
> two tape libraries attached via FC to the host. Using a single client 
> to backup several nfs/cifs mounts to lto5 tape.
>
> This setup has given me some three years of mostly headache free 
> backups. What i have been unable to accomplish is having both changers 
> available for all jobs coming from this single client.
>
> Couple of questions,
>
> Should I be using multiple clients or storage daemons?
>
> I already have the single sd configured to use both devices, how can i 
> tell dir or client to pick a free tape device from ANY changer when 
> client starts job?
>

The problem is that once a job is assigned one of the autochanger 
devices, all tapes it might use must be available in that autochangers 
library. Bacula will not reassign the device of a running job. For 
example, if a job is writing to a volume from pool A on device 0 and 
that volume becomes full, then it will seek another volume to write on. 
If the next selected volume from pool A happens to be in device 0's 
library, then all is well. However, if the next selected volume from 
pool A resides in the other autochanger's library, then it becomes a 
huge problem and Bacula will be forced to ask the operator to move the 
tape manually from one library to the other.

One possibility is to use a different pool for each job, then keep all 
tapes from a particular pool in the same library. For example, place 
tapes for pools A, C, E in device 0's library and tapes for pools B, D, 
F in device 1's library.

> Thanks all for your time and consideration!
>
> --eddie
>

--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users