Zitat von Radosław Korzeniewski <rados...@korzeniewski.net>: > Hello, > > 2012/10/17 <lst_ho...@kwsoft.de> > (...) > >> 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.
With the exception of Windows Clients at least when using data encryption or VSS :-( But ok, the "thread per client" is incorrect of course. > >> running and of course your OS >> must be able to handle some thousand TCP connections. > > > Yes it's true. > > >> That said you >> could also split the load to a number of Storage Daemons and only use >> a central Director. With this the next "hot-spot" will be the Director >> Database managing the file metadata. >> > > 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? >> In any way you should consider to get professional help from >> Baculasystems (www.baculasystems.com) with this target scale. >> > > Sure, or any Bacula Systems certified partner in your location. :) > > You can check a great success story deploying a large scale Bacula at: > http://myunix.dk/2010/12/01/large-scale-disk-to-disk-backups-using-bacula/ > Interesting reading, thanks. Regards Andreas ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
