On 2/10/20 4:12 AM, Radosław Korzeniewski wrote: > So, why not to design a special kind of SD which will get data from FD and > then save it on different backend SD synchronously defining full and > flexible RAIT or EC solution?
How should I know why you need a "specail" SD instead of a "regular" one? > This is a kind of help I want to get from community as you always complain > about decisions which developers take himself. I personally only care about failure of my HDD "magazine" being written to. SD writing to two file descriptors instead of one is all *I* want. I don't even care for having the 2nd copy in the catalog: I just want the same exact volume file on two physical drives. Once full, I'll put one of them on the shelf and wipe out the other, to be reused w/ the next magazine. Somebody else may want the copy to go to "the cloud" instead, that may or may not require a different approach. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
