Re: [Bacula-users] how to debug a job

Hello Kern, 2015-01-25 11:56 GMT+01:00 Kern Sibbald : > On 23.01.2015 19:22, Radosław Korzeniewski wrote: > > Hello, > > 2015-01-22 3:42 GMT+01:00 Dimitri Maziuk : > >> On 01/21/2015 06:41 PM, Bill Arlofski wrote: >> >> > Bacula has a hard-coded 6 day limit on a job's run time. 518401 >> secon

Re: [Bacula-users] how to debug a job

> Original Message > Subject: Re: [Bacula-users] how to debug a job > From: Roberts, Ben > To: Kern Sibbald > Cc: bacula-users > Date: Mon Jan 26 2015 02:51:10 GMT-0500 (EST) > > > Hi Kern, > > >> Hard-coded, huh? Nobody's tried backing up that b

Re: [Bacula-users] how to debug a job

sibbald.com] Sent: 25 January 2015 10:56 To: Radosław Korzeniewski; Dimitri Maziuk Cc: bacula-users Subject: Re: [Bacula-users] how to debug a job On 23.01.2015 19:22, Radosław Korzeniewski wrote: Hello, 2015-01-22 3:42 GMT+01:00 Dimitri Maziuk mailto:dmaz...@bmrb.wisc.edu>>: On 01/21/2015 06:4

Re: [Bacula-users] how to debug a job

On 1/24/2015 1:12 PM, Dmitri Maziuk wrote: > On 1/24/2015 9:00 AM, Kern Sibbald wrote: > >> Bottom line: contrary to what I previously thought there *might* be some >> benefits to turning on spooling for disk Volumes, but only if you have >> really fast spooling disks (or SSD). This is an interes

Re: [Bacula-users] how to debug a job

On 23.01.2015 19:22, Radosław Korzeniewski wrote: Hello, 2015-01-22 3:42 GMT+01:00 Dimitri Maziuk : On 01/21/2015 06:41 PM, Bill Arlofski wrote: > Bacula has a hard-co

Re: [Bacula-users] how to debug a job

On 1/24/2015 9:00 AM, Kern Sibbald wrote: > Bottom line: contrary to what I previously thought there *might* be some > benefits to turning on spooling for disk Volumes, but only if you have > really fast spooling disks (or SSD). This is an interesting topic, and > it would be nice to see some rea

Re: [Bacula-users] how to debug a job

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, This is not directed to any particular individual person -- I just chose the last email on this topic to keep the thread. I have alway thought it would not be useful to use spooling when writ

Re: [Bacula-users] how to debug a job

Hello, 2015-01-23 21:36 GMT+01:00 Josh Fisher : > > On 1/23/2015 2:33 PM, Heitor Faria wrote: > >> On 01/23/2015 12:22 PM, Radosław Korzeniewski wrote: > >> > >>> If you are using a vchanger then I guess it is a disk only backup, so > why > >>> do you spool data? It is not required but making you

Re: [Bacula-users] how to debug a job

Hello, 2015-01-23 21:42 GMT+01:00 Dimitri Maziuk : > On 01/23/2015 02:33 PM, Radosław Korzeniewski wrote: > > > No, it is not working as you described. > > Data spooling will read stream from the client, then write it to the > > temporary disk file, then during despool it is stopping a stream fro

Re: [Bacula-users] how to debug a job

Hello, 2015-01-23 20:57 GMT+01:00 Dimitri Maziuk : > On 01/23/2015 01:33 PM, Heitor Faria wrote: > > > Even though, IMHO, spooling disks backup is just "muda" (Japanese Term): > http://en.wikipedia.org/wiki/Muda_(Japanese_term) > > so are proxies and caching: spool disk is just a variation on >

Re: [Bacula-users] how to debug a job

On 01/23/2015 02:33 PM, Radosław Korzeniewski wrote: > No, it is not working as you described. > Data spooling will read stream from the client, then write it to the > temporary disk file, then during despool it is stopping a stream from the > client, reads a temporary file and write to destinatio

Re: [Bacula-users] how to debug a job

On 1/23/2015 2:33 PM, Heitor Faria wrote: >> On 01/23/2015 12:22 PM, Radosław Korzeniewski wrote: >> >>> If you are using a vchanger then I guess it is a disk only backup, so why >>> do you spool data? It is not required but making you backup slow down at >>> least 2 times then standard job. >> It

Re: [Bacula-users] how to debug a job

Hello, 2015-01-23 20:04 GMT+01:00 Dimitri Maziuk : > On 01/23/2015 12:22 PM, Radosław Korzeniewski wrote: > > > If you are using a vchanger then I guess it is a disk only backup, so why > > do you spool data? It is not required but making you backup slow down at > > least 2 times then standard jo

Re: [Bacula-users] how to debug a job

> Even though, IMHO, spooling disks backup is just "muda" (Japanese > Term): http://en.wikipedia.org/wiki/Muda_(Japanese_term) Not necessarily - if you have a number of backups that tend to flake out halfway through for whatever reasons (network, client issues, user issues, etc) e.g. then by spoo

Re: [Bacula-users] how to debug a job

On 01/23/2015 01:33 PM, Heitor Faria wrote: > Even though, IMHO, spooling disks backup is just "muda" (Japanese Term): > http://en.wikipedia.org/wiki/Muda_(Japanese_term) so are proxies and caching: spool disk is just a variation on that theme. -- Dimitri Maziuk Programmer/sysadmin BioMagResB

Re: [Bacula-users] how to debug a job

> On 01/23/2015 12:22 PM, Radosław Korzeniewski wrote: > > > If you are using a vchanger then I guess it is a disk only backup, so why > > do you spool data? It is not required but making you backup slow down at > > least 2 times then standard job. > > It's 2 times slower if your spool/despool is

Re: [Bacula-users] how to debug a job

On 01/23/2015 12:22 PM, Radosław Korzeniewski wrote: > If you are using a vchanger then I guess it is a disk only backup, so why > do you spool data? It is not required but making you backup slow down at > least 2 times then standard job. It's 2 times slower if your spool/despool is strictly sequ

Re: [Bacula-users] how to debug a job

Hello, 2015-01-22 3:42 GMT+01:00 Dimitri Maziuk : > On 01/21/2015 06:41 PM, Bill Arlofski wrote: > > > Bacula has a hard-coded 6 day limit on a job's run time. 518401 > seconds = > > 6.1157 days, so it appears that is the cause for the watchdog > killing the job. > > Hard-coded, huh? Nobody

Re: [Bacula-users] how to debug a job

On 01/23/2015 09:57 AM, Josh Fisher wrote: > ... Have you been able to determine what > exactly is slow? I wonder if when the data spool file gets full it > triggers a de-spool of both data and attributes, rather than just data? Look like there's something wrong with the spool disk: I replaced it

Re: [Bacula-users] how to debug a job

On 1/23/2015 10:36 AM, Dmitri Maziuk wrote: On 1/23/2015 9:03 AM, Josh Fisher wrote: I use another approach. I define the vchanger to have multiple virtual drives... So for 10 concurrent jobs there would be 10 virtual drives and so 10 opened volume files. My way also keeps the config simple s

Re: [Bacula-users] how to debug a job

On 1/23/2015 9:03 AM, Josh Fisher wrote: > I use another approach. I define the vchanger to have multiple virtual > drives... So for 10 concurrent jobs there would be 10 virtual > drives and so 10 opened volume files. My way also keeps the config simple stupid: as long as the backups complete on

Re: [Bacula-users] how to debug a job

On 1/22/2015 12:47 PM, Dimitri Maziuk wrote: On 01/22/2015 10:07 AM, Josh Fisher wrote: There is likely no reason to have SpoolData=yes for disk volumes, and it could actually slow things down. On 01/22/2015 07:32 AM, Clark, Patricia A. wrote: Spooling is for the benefit of tape drives and

Re: [Bacula-users] how to debug a job

On 01/22/2015 10:07 AM, Josh Fisher wrote: > There is likely no reason to have SpoolData=yes for disk volumes, and it > could actually slow things down. On 01/22/2015 07:32 AM, Clark, Patricia A. wrote: > Spooling is for the benefit of tape drives and databases. What is the > benefit of spoolin

Re: [Bacula-users] how to debug a job

On 1/21/2015 6:37 PM, Dimitri Maziuk wrote: On 01/21/2015 05:12 PM, Heitor Faria wrote: Hey Mr. Dimitri: do you have Attribute Spooling on for this job (Job resource, Spool Attributes=yes)? It usually improves the performance if backing up lots of files, witch maybe causing this bottleneck.

Re: [Bacula-users] how to debug a job

I back up over 300T each month. For that reason I also stay as current as is reasonably possible on versions of Bacula. Having upgraded to version 7, I've found that the 6-day hard coded failure appears to have been removed which has allowed several of my long-running jobs to complete successfull

Re: [Bacula-users] how to debug a job

@lists.sourceforge.net Subject: [Bacula-users] how to debug a job (Take 2) I've a client with ~316GB to back up. Currently the backup's been running for 5 days and wrote 33GB to the spool file. Previous runs failed with > User specified Job spool size reached: JobSpoolSize=49,807,365,050

Re: [Bacula-users] how to debug a job

On 01/21/2015 06:41 PM, Bill Arlofski wrote: > Bacula has a hard-coded 6 day limit on a job's run time. 518401 seconds = > 6.1157 days, so it appears that is the cause for the watchdog killing the > job. Hard-coded, huh? Nobody's tried backing up that big data I keep hearing about? > Does

Re: [Bacula-users] how to debug a job

On 01/21/2015 05:13 PM, Dimitri Maziuk wrote: > (Take 2) > > I've a client with ~316GB to back up. Currently the backup's been > running for 5 days and wrote 33GB to the spool file. Previous runs > failed with > >> User specified Job spool size reached: JobSpoolSize=49,807,365,050 >> MaxJobSpool

Re: [Bacula-users] how to debug a job

On 01/21/2015 05:12 PM, Heitor Faria wrote: > Hey Mr. Dimitri: do you have Attribute Spooling on for this job (Job resource, Spool Attributes=yes)? It usually improves the performance if backing up lots of files, witch maybe causing this bottleneck. Yes: SpoolData = yes SpoolAttributes =

Re: [Bacula-users] how to debug a job

> I've a client with ~316GB to back up. Currently the backup's been > running for 5 days and wrote 33GB to the spool file. Previous runs > failed with > > > User specified Job spool size reached: JobSpoolSize=49,807,365,050 > > MaxJobSpoolSize=49,807,360,000 > > Writing spooled data to Volume. Des

[Bacula-users] how to debug a job

(Take 2) I've a client with ~316GB to back up. Currently the backup's been running for 5 days and wrote 33GB to the spool file. Previous runs failed with > User specified Job spool size reached: JobSpoolSize=49,807,365,050 > MaxJobSpoolSize=49,807,360,000 > Writing spooled data to Volume. Despoo