Hi All<br><br>I've been looking for something like Gluster for a while and stumbled on it today via the wikipedia pages on Filesystems etc.<br><br>I have a few very very simple questions that might even be too simple to be on the FAQ, but if you think any of them are decent please add them there.<br>
<br>I think it might help if I start with what I want to achieve, then ask the questions. We want to build a high uptime, storage solution that can scale easily, but we want to do it on the cheap, with normal SATA disks and "consumer" motherboards etc. We'll use GigE to connect the nodes. Performance is not such a big criteria since the required throughput is nothing spectacular. <br>
<br>Based on what I've read I think we should use:<br><br>1. Unify translator (to present one big FS to my systems master server)<br>2. AFR (to make my data redundant ... I'd like to try and avoid using RAID on the nodes.)<br>
<br>So my questions are:<br><br>1. Is there anything blindingly wrong with what I'm suggesting?<br>2. Should I use AFR to achieve redundancy?<br>2. What is the minimum number of machines/bricks in the cluster that will support data redundancy with AFR?<br>
3. The AFR docs seem to indicate that it keeps a copy of the file on *every* node... isn't that wasting a lot of space? I really just need 2 copies or three copies so that one node or 2 nodes can go down at a time.<br>
<br>I'm sure I'll have lots more questions but for now that should point me in the right direction.<br><br>Regards<br>J.<br>