Hello Radoslaw, Perhaps you should consider a total FD revamp that allows:
- Parallel Client disk reading streams, for faster backups even for a single SD device writing; - FD multi-SD writing capability, with redundant streams or even just fail-over between SDs. Regards, -- MSc Heitor Faria CEO Bacula LatAm mobile1: + 1 909 655-8971 mobile2: + 55 61 98268-4220 América Latina [ http://bacula.lat/] -------- Original Message -------- From: Radosław Korzeniewski <rados...@korzeniewski.net> Sent: Monday, February 10, 2020 07:19 AM To: dmaziuk <dmaz...@bmrb.wisc.edu> Subject: Re: [Bacula-users] [EXTERNAL] Re: bacula cloud backup CC: bacula-users <bacula-users@lists.sourceforge.net> >Hello, > >pt., 31 sty 2020 o 16:27 dmaziuk via Bacula-users < >bacula-users@lists.sourceforge.net> napisał(a): > >> On 1/31/2020 3:33 AM, Radosław Korzeniewski wrote: >> > >> >> Amanda had "RAIT" since forever. >> >> >> > >> > If you would be so kind and have an idea how it could be implemented in >> > bacula and so kind to describe it on this list it would be implemented by >> > developers. >> >> I don't have any idea how it could be implemented *in bacula* since I >> never looked at any bacula code. >> > >I do not want you to know anything about Bacula source code when I asked >about functionality description. It is a pure architecture description >which developers could implement. > > >> In general sending the same stream of bytes to two different places >> instead of one is not exactly rocket science. > > >Well, I do not want to dive deeper into discussion how rocket science or >not it is... > > >> I guess it and can be >> implemented in several places, e.g. special storage inside SD, or two >> different SDs. >> > >This is the exact discussion I could make. >What is better - two distinct SD which do not know anything about each >other and FD just sends two concurrent data streams to both (or any >multiple number of SD when we implement chunking or erasure code) or >special kind of SD which handles redundancy internally syncing data to >other SD synchronously. > > >> >> I would probably send to two SDs at once because it allows for more >> flexible setups: > > >And by default lower the backup speed twice. > > >> the 2nd SD can write to "the cloud", it can be on the >> off-site box, etc. Whereas amanda-style RAIT device only protects >> against single disk/tape failure. >> > >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? > >This is a kind of help I want to get from community as you always complain >about decisions which developers take himself. > >best regards >-- >Radosław Korzeniewski >rados...@korzeniewski.net > > >_______________________________________________ >Bacula-users mailing list >Bacula-users@lists.sourceforge.net >https://lists.sourceforge.net/lists/listinfo/bacula-users
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
