I have been designing a system that does something a lot like this, to function as a multimedia asset management system.
I would love to compare notes with you if you like. Do you want this to work on the block level? It sounds like you do. Things like this do exist, but you have to be very specific about what you are trying to get out of it? From your description it sounds like you simply want to do replication between two nodes. But then I thought about it more and realized that, in this case, you could simply set your file service as "active" and the remote one as "redundant". Or are you trying to implement a cache for your working files that are a subset of the complete file service that has too much data to store locally? I am trying to minimize noise in the local sub-NAS of the complete file server. The sub-NAS will have SSD's and the remote upstream NAS will have many arrays of high-capacity spinning HDD's. In your case there are companies that, I think, do what you need, such as Dell/EMC. But they are expensive and proprietary. Can you please specify in detail what you want to do? I would like to see if there is any common overlap. If you like, we could share our findings. Andrew On 22 June 2019 14:13:21 BST, tlaro...@polynum.com wrote: >Hello, > >I don't know if the idea is stupid, but I wonder if there is a way >to combine existing programs in order to associate in a RAID1 a local >disk and a "remote" disk, i.e. a way to give the RAID1 software a >pseudo-device as the secondary disk, write data being sent also to this >remote disk while read data being only done via the network if the >local disk fails to answer after some laps of time (in order not to >crowd the network with the redundant reads, if a "shared" network >pipe is the mean of the remote link, or simply to not waste energy). > >This would allow both remote backup and fallback. > >Is there something like that existing? the idea being to combine >as much as possible existing facilities and just to insert a simple >client/server encapsulating "disk" data at the right place (the >pseudo-device) to make it work. > >Hoping this does not sound totally weird, >-- > Thierry Laronde <tlaronde +AT+ polynum +dot+ com> > http://www.kergis.com/ > http://www.sbfa.fr/ >Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
