> I do not follow this thread from the beginning, so I could be wrong about 
> some tips. 

> You have a 11M files in single backup job. If your job name is not misleading 
> all your files are located on NFS share. Right? 
> If yes, this is your main bottleneck. NFS is not the best protocol for this 
> job. If your NFS is a some kind of NAS array then you can speed up your 
> backup with NDMP. 

Hi, i don't use NFS share, i put bacula client on this server, I'll look at how 
to implement NDMP

> Next, you should implement Bacula VirtualFull backup, which avoid any next 
> Full backup on the client. After that all your jobs will be all Incremental > 
> and your problem with full will gone. 

I do not know VirtualFull backup, I will document about this

> Data spool is required for tape drive only. You need to manually tune the 
> best job spool size for best performance. From my experience on one of my 
> systems I have 8GB/Job which is better then 32GB/Job spool which was before. 
> The most important, your job spool size can be 8GB too, because you limit 
> overall spool size to 24GB. It will work.

I'll try it, I can do the test quickly
I'll let you know

+----------------------------------------------------------------------
|This was sent by supervision AT numalliance DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users