I scoped the problem as two major projects: 

1) implementation of "copy pools" -- where files written to a pool were
automatically also written to up to 3 additional pools using the same volume
selection criteria as exist now (essentially getting the SD to act as a FD
to more than one FDs to ensure synchronous updates, or creating a SD-mux
function to split the FD data stream to N SDs).

2) implementation of pool to pool migration as discussed on the list
previously. 

I think there is approximately 1-2 solid months of coding involved in each
project -- neither are trivial to do. To get that coded is going to take a
few contributions. 




-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to