That's maybe a stupid question, but I really wonder...

Using Disk Spooling prior to write data to tape, heads in a sequential 
write order:
a) write data from backup client to disk spool directory
b) write data from spool directory to tape

Why are those tasks done sequentially?

Let's say if the spool is reaching a waterlevel mark, the storage daemon 
will start to write the spool data to tape _and_ at the same time the 
backup client still sends data to the spool directory. Isn't that possible?

Cheerz,
  - Dan

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users