ThanksRadoslaw
--- On Fri, 19/10/12, Radosław Korzeniewski wrote:
From: Radosław Korzeniewski
Subject: Re: [Bacula-users] Query regarding bacula
To: "krishna pawankar"
Cc: bacula-users@lists.sourceforge.net
Date: Friday, 19 October, 2012, 5:06 PM
Hello,
2012/10/
Hello,
2012/10/19 krishna pawankar
> Hello,
>
> I have one query on bacula. I am not able to figure that when bacula
> deletes the physical data actually from VTL, since what i know is purge and
> prune only work on catalog inormation. They don't touch the actual data on
> volumes. So can i conc
Hello,
2012/10/19
>
>
Ok, so for the OP case with 1000 concurrent jobs this would be 2000
> threads at director side and 1000 connections to the Database... wow!
>
>
Right. You have to keep in mind that those threads are very idle almost all
the time, especially when you use an attributes spooli
Hello,
I have one query on bacula. I am not able to figure that when bacula deletes
the physical data actually from VTL, since what i know is purge and prune only
work on catalog inormation. They don't touch the actual data on volumes. So can
i conclude that it will not delete the physical dat
Thanks Simone for your suggestion...
--- On Wed, 17/10/12, Simone Caronni wrote:
From: Simone Caronni
Subject: Re: [Bacula-users] Query regarding Bacula
To: "krishna pawankar"
Cc: bacula-users@lists.sourceforge.net
Date: Wednesday, 17 October, 2012, 6:15 PM
Hello,
I persona
Zitat von Radosław Korzeniewski :
> Hello,
>
> 2012/10/19
>>
>> > The same for Director. It uses one thread per JOB so managing a 1000
>> > concurrent jobs leads to at least 1000 threads to manage by OS.
>>
>> What about SD -> Director? Does this also mean we have 1000
>> connections to the data
Hello,
2012/10/19
>
> > The same for Director. It uses one thread per JOB so managing a 1000
> > concurrent jobs leads to at least 1000 threads to manage by OS.
>
> What about SD -> Director? Does this also mean we have 1000
> connections to the database?
To be precise. Every job on Director si
Zitat von Radosław Korzeniewski :
> Hello,
>
> 2012/10/17
> (...)
>
>> As far as i know the Storage Daemon will be the "hot-spot" because it
>> will use one thread per client backup
>
>
> No, SD is using one thread per JOB not per Client. You can have a number
> of concurrent jobs running from o
Hello,
2012/10/17
(...)
> As far as i know the Storage Daemon will be the "hot-spot" because it
> will use one thread per client backup
No, SD is using one thread per JOB not per Client. You can have a number
of concurrent jobs running from one client without a problem.
> running and of cour
Zitat von krishna pawankar :
> Hi,
> I am using bacula 5.2.6 which will replace other network backup
> software if it is proven to be more featured compared to other
> nework backup software.
>
> Statistically i want to show the compression ratio bacula can
> support while backing up the
Hello,
I personally run it on hundreds of systems; windows (most of these are also
road warriors), linux, freebsd, openbsd - even a SCOUnix box - on a variety
of storage daemons with tapes, disks, etc. all on a single mysql director
without a hitch.
Compression is good in itself, it depends on th
Hi,
I am using bacula 5.2.6 which will replace other network backup software if it
is proven to be more featured compared to other nework backup software.
Statistically i want to show the compression ratio bacula can support while
backing up the data over the other vendor softwares also what am
12 matches
Mail list logo
